snapshot doesn't resync due to bad symlinks

[phl]

Binary package hint: casper

At halt/reboot time there is no automatic snapshot, b/c the symlink is S89casper and /etc/init.d/casper start does nothing, it is /etc/init.d/casper stop that does the resync.

In /etc/rc{0,6}.d, renaming S89casper to K89casper fixes the issue.

[Colin Watson (cjwatson)]

Fixed, thanks.

[Colin Watson (cjwatson)]

Actually, this isn't right; if you move it to K89 then the order in which the scripts in /etc/rc6.d are run ends up being wrong, since the casper init script needs to be the last thing run before rebooting. It needs to be S89, but the script needs to handle 'start'.

[Colin Watson (cjwatson)]

(Done.)

[Launchpad Janitor (janitor)]

This bug was fixed in the package casper - 1.178

---------------
casper (1.178) karmic; urgency=low

  * Ensure that unionfs-fuse isn't killed by /etc/init.d/sendsigs on
    shutdown (LP: #386010).
  * Patches from "phl" (https://launchpad.net/~ubuntu-leledy), adjusted by
    me, to fix snapshot resync:
    - Avoid using cpio -u -d options if klibc cpio is in use (LP: #384059).
    - Copy /etc/casper.conf into /root, otherwise we forget snapshot resync
      settings (LP: #384061).
    - Adjust the first field of *SNAP entries in casper.conf to be relative
      to /cow, not /root (LP: #384066).
    - Prefix $DEST with $MOUNTP in casper-snapshot (LP: #384068).
    - /etc/init.d/casper is usually called with 'start', so handle that as
      well as 'stop' to do snapshot resyncing and CD ejecting (LP: #384076).
  * Fix casper-snapshot(1) syntax to avoid missing spaces between options
    and their values.
  * Fix showmounts when used in conjunction with unionfs-fuse; read-only
    filesystems need to be bind-mounted rather than move-mounted.

 -- Colin Watson <email address hidden> Fri, 12 Jun 2009 13:24:28 +0100