cleanup scripts confused about cleaning /var/run and /var/lock

Bug #77954 reported by James Troup
2
Affects Status Importance Assigned to Milestone
sysvinit (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: sysvinit

There are several scripts in init.d that talk about cleaning up /var/lock and /var/run, but in fact these directories are now cleaned by virtue of being tmpfs mounts. It'd be nice to cleanup the comments to match this new reality, as it's otherwise kind of confusing.

mountall-bootclean.sh: # Clean /tmp, /var/lock, /var/run
mountnfs-bootclean.sh: # Clean /tmp, /var/lock, /var/run
mountnfs.sh: # Clean /tmp, /var/lock, /var/run
umountnfs.sh: rm -f /tmp/.clean /var/lock/.clean /var/run/.clean

Also mountnfs.sh seems to source '/etc/init.d/bootclean.sh' (sic) which doesn't exist, so I'm not sure how it's meant to even work ATM...

Related branches

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

sysvinit (2.86.ds1-14.1ubuntu30) gutsy; urgency=low

  * Drop saving of udev.log seeing as one of udev's own init scripts
    handle this now.
  * Make missing directories on the root filesystem before unmounting it.
  * Remove confusing mentions of cleaning /var/run and /var/lock. LP: #77954.

 -- Scott James Remnant <email address hidden> Wed, 03 Oct 2007 16:34:42 +0100

Changed in sysvinit:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.