FS#29855 - [initscripts] removing leftover files
Attached to Project:
Arch Linux
Opened by Csaba Cs (dash) - Saturday, 12 May 2012, 12:53 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 08 September 2012, 22:52 GMT
Opened by Csaba Cs (dash) - Saturday, 12 May 2012, 12:53 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 08 September 2012, 22:52 GMT
|
Details
Description:
Cleaning /tmp at boot time also removes the lost+found folder on an ext3/ext4 filesystem. When fsck runs, it generates the lost+found not found. CREATED message. I have a separate logical volume for /tmp mount. At least for cosmetic reasons it should be fixed. |
This task depends upon
Closed by Dave Reisner (falconindy)
Saturday, 08 September 2012, 22:52 GMT
Reason for closing: Fixed
Additional comments about closing: systemd-tmpfiles is more clever about ignoring things like lost+found and is now used by everyone, systemd or not.
Saturday, 08 September 2012, 22:52 GMT
Reason for closing: Fixed
Additional comments about closing: systemd-tmpfiles is more clever about ignoring things like lost+found and is now used by everyone, systemd or not.
Comment by
Dave Reisner (falconindy) -
Saturday, 12 May 2012, 13:04 GMT
Any particular reason you've chosen not to use tmpfs for /tmp?
Comment by Dan McGee (toofishes) -
Saturday, 12 May 2012, 16:59 GMT
Because sometimes people need more than available RAM for /tmp? I
know you and Tom like to advocate using tmpfs, but there are times
when it is not appropriate as well.
Comment by Tom Gundersen (tomegun) -
Saturday, 12 May 2012, 17:09 GMT
@Dan: then add the space as swap. I always ask this question: I
would be very interested in a usecase (including numbers if
performance is relevant) where using tmpfs is not the best thing
to do.
Comment by
Alexander F. Rødseth (xyproto) -
Saturday, 08 September 2012, 22:48 GMT
@dash, if you have elected to not use tmpfs, does it solve your
problem to edit /etc/rc.sysinit and silence fsc? Is this still an
issue?
Comment by
Dave Reisner (falconindy) -
Saturday, 08 September 2012, 22:50 GMT
This should have been fixed a while ago, when systemd-tmpfiles
replaced arch-tmpfiles.