Bug#636339: Missing directory structure in /var/run
retitle 636339 Please provide mechanism to create directory structure in /var/run tmpfs severity 636339 wishlist thanks Hello, > I don't use init scripts, and even if i did, the runit FastCGI > services might still get started before my init script. I don't know how runit services work, but if this is supported, the best in your case might be to modify your FastCGI service to let it create its socket directory right when it's going to be needed. Otherwise, I surmise you can create another service doing just that with proper dependencies to ensure they're run in the right order. > So I need a simple way to have a persistent directory tree under > /var/run (I guess we can agree that writing new rcS.d scripts isn't an > option). Nothing prevents you from creating your own new rcS.d script or editing an existing one, like /etc/init.d/mountkernfs.sh, to create your directory structure right after it mounts /run. I agree that a general-purpose tmpfiles.d or equivalent could be a good thing to have. However, initscripts can already be edited to add in such small setups, any external tool providing such a configurable feature can already plug itself into the boot sequence, and tmpfs /run and /var/run are long standard now, so I'm downgrading this to wishlist. Michael, how hard does systemd-tmpfiles depend on systemd, and what would you think of splitting it into a separate binary package? -- Pierre Ynard
Bug#636339: Missing directory structure in /var/run
Hi Stefan, a mechanism like tmpfiles.d [2] as provided by systemd would be the solution for this and we should consider making that generally usable (i.e. without a dependency on systemd). This way your package can drop a simple file in /usr/lib/tmpfiles.d or you as administrator can create a file in /etc/tmpfiles.d In your case this file would be as simple as ,--- |d /var/run/lighttpd 0750 www-data root - `--- Cheers, Michael [1] http://0pointer.de/public/systemd-man/tmpfiles.d.html -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#636339: Missing directory structure in /var/run
Hi Michael, On 09/28/2011 10:22 PM, Michael Biebl wrote: Hi Stefan, a mechanism like tmpfiles.d [2] as provided by systemd would be the solution for this and we should consider making that generally usable (i.e. without a dependency on systemd). This way your package can drop a simple file in /usr/lib/tmpfiles.d or you as administrator can create a file in /etc/tmpfiles.d In your case this file would be as simple as ,--- |d /var/run/lighttpd 0750 www-data root - `--- yes, this sounds like the right solution to me if it would be provided outside from systemd, perhaps in a base package. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636339: Missing directory structure in /var/run
Package: initscripts Version: 2.88dsf-13.11 User: rle...@debian.org Usertags: run-transition Hi! Let me put this first: I think using a tmpfs for /var/run is a good idea. But I think you have to be a little bit more careful. The FHS states, that Files under this directory must be cleared (removed or truncated as appropriate) at the beginning of the boot process. And debian has always interpreted Files to mean not a directory: (from /lib/init/bootclean.sh) find . ! -xtype d ! -name utmp ! -name innd.pid -delete And so I have been using custom sub directories like /var/run/lighttpd where I put FastCGI socket files. I use 0750 www-data:root on it, so only www-data processes can see the sockets, and I would like to keep it that way. I do *not* want to put those sockets directly in /var/run, as there is no reason for others to even *see* those sockets (file permissions on the socket would still prevent unauthorized connections). I don't use init scripts, and even if i did, the runit FastCGI services might still get started before my init script. So I need a simple way to have a persistent directory tree under /var/run (I guess we can agree that writing new rcS.d scripts isn't an option). A second note: You really should think about backporting. Especially server packages are a valid target for backporting, and those often use /var/run. So i really suggest not to use /run in any source package for debian until all supported debian dists (including ubuntu) support /run, so we can still backport them. (core packages like udev can use /run ofc, backporting them is probably hell anyway :D) Btw: https://build.opensuse.org/ provides backport overlays with current debhelper releases for ubuntu, so backporting is really not that hard. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
