View previous topic :: View next topic |
Author |
Message |
Ant P. Watchman
Joined: 18 Apr 2009 Posts: 6920
|
Posted: Fri Nov 16, 2012 4:52 pm Post subject: How is /run supposed to be set up correctly? |
|
|
I'm having problems with two different machines that I let the /run auto-migration thing happen on. Several services aren't starting up due to not having permission to write pidfiles. This started after a reboot and going from 3.5.x to 3.6.x.
I've tried giving /run a mode=1777 in fstab (which seems to be completely ignored), and doing the same with chmod, but that only seems to make more things break. I don't have these problems on my desktop, but that's running a different set of services. |
|
Back to top |
|
|
wolfieh n00b
Joined: 17 Nov 2009 Posts: 54
|
Posted: Tue Nov 20, 2012 7:36 pm Post subject: |
|
|
I just noticed the same. I would prefer to have it has /var/run, since on my setup / is an SSD drive, and /var is a regular hard disk. It was silently done, wouldn't have noticed if I didn't read rc.log |
|
Back to top |
|
|
Gusar Advocate
Joined: 09 Apr 2005 Posts: 2665 Location: Slovenia
|
Posted: Tue Nov 20, 2012 7:57 pm Post subject: |
|
|
/run is a tmpfs so it's irrelevant what kind of disk your / is. |
|
Back to top |
|
|
wolfieh n00b
Joined: 17 Nov 2009 Posts: 54
|
Posted: Tue Nov 20, 2012 7:58 pm Post subject: |
|
|
Gusar wrote: | /run is a tmpfs so it's irrelevant what kind of disk your / is. |
yes, just noticed. thanks |
|
Back to top |
|
|
Ant P. Watchman
Joined: 18 Apr 2009 Posts: 6920
|
Posted: Tue Nov 20, 2012 8:38 pm Post subject: |
|
|
This seems to be related to bug 332633. That's been there for 2 years so I'm not sure why things only started breaking in the last month. Do I need to go file bugs for all affected packages? |
|
Back to top |
|
|
Suicidal l33t
Joined: 30 Jul 2003 Posts: 959 Location: /dev/null
|
Posted: Tue Nov 20, 2012 10:28 pm Post subject: |
|
|
My problems have been with stuff like auditd, it is looking for /var/lock/subsys which symlinks to /run/lock/subsys.
Its not a permissions issue the subsys directory just doesn't exist.
I just added the following to the beginning of start() in the init script
fix_broken_auditd_init_script: | if [ ! -d /var/lock/subsys ]; then
mkdir /var/lock/subsys
fi
|
|
|
Back to top |
|
|
Gusar Advocate
Joined: 09 Apr 2005 Posts: 2665 Location: Slovenia
|
Posted: Tue Nov 20, 2012 11:10 pm Post subject: |
|
|
Creating dirs in /run is a job for tmpfiles. Ideally it should be provided by the auditd package, but until that happens create the file yourself:
/usr/lib/tmpfiles.d/auditd.conf
Code: | d /run/lock/subsys 1777 root root - |
Adjust permissions (the third parameter) and user/group if needed. tmpfiles is a systemd thingy, but OpenRC has a shell implementation of it. To learn more about it: http://0pointer.de/public/systemd-man/tmpfiles.d.html - the openrc implementation ignores the "age" parameter. |
|
Back to top |
|
|
Suicidal l33t
Joined: 30 Jul 2003 Posts: 959 Location: /dev/null
|
Posted: Wed Nov 21, 2012 12:33 am Post subject: |
|
|
Gusar wrote: | Creating dirs in /run is a job for tmpfiles. Ideally it should be provided by the auditd package, but until that happens create the file yourself:
/usr/lib/tmpfiles.d/auditd.conf
Code: | d /run/lock/subsys 1777 root root - |
Adjust permissions (the third parameter) and user/group if needed. tmpfiles is a systemd thingy, but OpenRC has a shell implementation of it. To learn more about it: http://0pointer.de/public/systemd-man/tmpfiles.d.html - the openrc implementation ignores the "age" parameter. |
The bad thing is I am running amd64 not ~amd64, simple bugs like this should have been squashed before hitting the stable tree. |
|
Back to top |
|
|
|