Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#44615 - [open-vm-tools] using config file in /etc/tmpfiles.d to create /run/vmblock-fuse directory
Attached to Project:
Community Packages
Opened by Martin Stolpe (BertiBoeller) - Thursday, 16 April 2015, 12:38 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 16 April 2015, 16:36 GMT
Opened by Martin Stolpe (BertiBoeller) - Thursday, 16 April 2015, 12:38 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 16 April 2015, 16:36 GMT
|
DetailsAccording to the systemd documentation: http://www.freedesktop.org/software/systemd/man/tmpfiles.d.html
it seems to be good style to use configuration files in /etc/tmpfiles.d to create directories in the /run folder. So instead of using ExecStartPre=/usr/bin/mkdir -p /run/vmblock-fuse in vmware-vmblock-fuse.service you could create /etc/tmpfiles.d/vmware-vmblock-fuse.conf with the following contents: d /run/vmblock-fuse Regards Martin |
This task depends upon
Closed by Sergej Pupykin (sergej)
Thursday, 16 April 2015, 16:36 GMT
Reason for closing: Fixed
Additional comments about closing: without tmpfiles.d but using RuntimeDirectory.
in svn/trunk only
Thursday, 16 April 2015, 16:36 GMT
Reason for closing: Fixed
Additional comments about closing: without tmpfiles.d but using RuntimeDirectory.
in svn/trunk only
-ExecStartPre=/usr/bin/mkdir -p /run/vmblock-fuse
+RuntimeDirectory=/run/vmblock-fuse
+RuntimeDirectoryMode=755