/run & /var/run being a tmpfs
Hello,
Speaking of a recent change in current, are we sure that having /run and now also /var/run, because it's a bind mount, as tmpfs is fine? I've already found issues with services that do not recreate a folder in /var/run at startup because they expect it to be permanent, and so they don't start. Is it the services that should be fixed or the directory that should be made not a tmpfs? |
Hi,
I talked about that is this post. The idea is to create the folder automatically when using "/etc/rc.d/rc.mydaemon start", so we have to adapt many SB. |
If possible, try to compile with different path.
|
just a suggestion: if you get in touch with the scripts maintainers and ask to adapt them to create the the directory (as-needed) at start they will be current-ready in no-time.
Quote:
|
Quote:
Btw it seems that the "other system" has got a method to deal with this. |
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
When it exists, the named.pid will be inside it, otherwise it's not present. |
Quote:
|
Quote:
Edit: but probably I realized why. I start named with "-u daemon" so probably it doesn't have permission to create the folder on its own. It's an old habit of not running named as root. So nevermind, it doesn't require a fix in the startup script. |
Quote:
|
Quote:
I'm following the old way of starting it with -u daemon.. it's still referred in rc.bind Maybe it's good to add a note that if still using this method, recreating /var/run/named at boot is on the user. |
Quote:
|
All times are GMT -5. The time now is 06:13 PM. |