On 01.06.2012 05:27, Samuel Hym wrote: > Package: systemd > Version: 44-1 > Severity: grave > Justification: causes non-serious data loss > > Dear Maintainer, > > Launching systemd instead of sysvinit uses its default tmp files policy of > removing files older than a month from /var/tmp. > Since this behaviour is different from the older init, a warning at the > installation than that would happen would have been most helpful.
If you want to store data persistently, /var/tmp is not the right place. The only real guarantee that /var/tmp provides is that data survives a reboot. The FHS is pretty clear imho about this [1] "Files and directories located in /var/tmp must not be deleted when the system is booted. Although data stored in /var/tmp is typically deleted in a site-specific manner, it is recommended that deletions occur at a less frequent interval than /tmp." Systemd by default cleans up unmodified/unaccessed files from /tmp after 10 days, and 30 days for /var/tmp. sysvinit on Debian indeed does not clean up stale files from /var/tmp by default. That said I'm not convinced that showing a (debconf) message during installation is a good idea. Maybe something for README.Debian? I'm also not convinced that the severity is warranted, given the clear definition of /var/tmp. That said, I'll leave that up to Tollef to decide. Michael [1] http://www.pathname.com/fhs/pub/fhs-2.3.html#VARTMPTEMPORARYFILESPRESERVEDBETWEE -- 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
