[2142] in athena10

home help back first fref pref prev next nref lref last post

Re: [Debathena] #186: debathena-afs-config should `fs newcell` in

daemon@ATHENA.MIT.EDU (Debathena Trac)
Thu Apr 9 11:49:22 2009

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@mit.edu
To: broder@mit.edu
Date: Thu, 09 Apr 2009 15:49:04 -0000
Reply-To: 
Message-ID: <052.1b2858bce844c2e0cd69a0b898e03d0b@mit.edu>
In-Reply-To: <043.4dbec676040fb38dc3b2967a68dd25f9@mit.edu>
Content-Transfer-Encoding: 8bit

#186: debathena-afs-config should `fs newcell` in postinst--------------------------+-------------------------------------------------
  Reporter:  broder       |       Owner:     
      Type:  enhancement  |      Status:  new
  Priority:  major        |   Component:  -- 
Resolution:               |    Keywords:     
--------------------------+-------------------------------------------------
Comment(by broder):
 I wonder if afs-config's postinst should also schedule a reboot if
 restarting openafs-client fails?

 It looks like you're supposed to do that by running `/usr/share/update-
 notifier/notify-reboot-required`, although that doesn't seem to generally
 exist on non-ubuntu-desktop systems. That script just touches `/var/run
 /reboot-required`, which is what debathena-auto-update keys off of to
 trigger a reboot.

 So maybe something like

 {{{
 if ! invoke-rc.d openafs-client restart; then
     if [ -x /usr/share/update-notifier/notify-reboot-required]; then
         /usr/share/update-notifier/notify-reboot-required
     else
         touch /var/run/reboot-required
     fi
 fi
 }}}

 The `fs newcell` loop should be sufficient for most cases, since usually
 updates to afs-config just change the CSDB. Maybe have an easy way to
 trigger a reboot on specific upgrades?
-- Ticket URL: <http://debathena.mit.edu/trac/ticket/186#comment:1>Debathena <http://debathena.mit.edu/>MIT Debian-Athena Project

home help back first fref pref prev next nref lref last post