Systemd can not start rtkit-daemon, ntpd, cups with PrivateTmp=yes.

[Ed Greshko]

On 11/03/14 19:17, Francis SOUYRI wrote:
> Hello,
>
>      I am running a Fedora 3.16.6-203.fc20.x86_64, after some updates
> (do not know what updates) now systemd can not start rtkit-daemon, ntpd,
> cups when PrivateTmp=yes.
>
> I see a same problem when /var/tmp is a symlink of /tmp or when /tmp is
> a tmpfs but this is not my case.
>
> # df -k /tmp /var/tmp
> Filesystem               1K-blocks    Used Available Use% Mounted on
> /dev/mapper/vgroot-lvtmp   4022592  434892   3363652  12% /tmp
> /dev/mapper/vgroot-lvvar   4022592 1862340   1936204  50% /var
>
> # ls -ld /var/tmp /tmp
> drwxrwxrwt. 89 root root 53248 Nov  3 12:01 /tmp
> drwxrwxrwt. 16 root root 12288 Nov  3 12:00 /var/tmp
>
> l have some other systems the a 32 bits FC20 without this problem.
>
> I set PrivateTmp=no systemd work fine, but this is only a bypass.
>
>

Since this seems like a standard F20 system you're running you may want to bring this up on the "users" list?

But, I will say I'm not seeing this on a fully updated F20 system.  I checked this both with /tmp being on "real" disk as well as tmpfs.

[egreshko at f20f ~]$ grep PrivateTmp /lib/systemd/system/cups.service
PrivateTmp=true
[egreshko at f20f ~]$ ps -eaf | grep cupsd
root       603     1  0 20:48 ?        00:00:00 /usr/sbin/cupsd -f

What means "can not start"?  Error messages in log files?  Error messages displayed with "systemctl status"?


-- 
If you can't laugh at yourself, others will gladly oblige.