Comment 6 for bug 1058883

I'm not sure why the restart is there. Perhaps it's trying to guarantee the
routing tables are correct. Or perhaps it's intended to start up the aiccu
daemon if the computer is suspended on a network with native IPv6 support,
then resumed on a network without native IPv6 support, where the aiccu
daemon is needed. It also restarts aiccu if ping6 isn't found, not sure why.

Just in case it wasn't clear, the sleep.d script is part of the default
installation as well--I don't have a link, but it can be easily verified by
downloading the aiccu source package and looking for the file `60aiccu` in
the debian/ directory.

On Tue, Oct 2, 2012 at 11:00 PM, Jeroen Massar <email address hidden> wrote:

> > I found the file
> `/etc/pm/sleep.d/60aiccu`. This appears to be the offending line:
> >
> > $P6 -I $INT -c 1 f.root-servers.net >/dev/null 2>&1 || invoke-rc.d
> aiccu
> restart
>
> And the million dollar prize question becomes: why is there a restart
> there?
>
> > If I comment out the offending line and use the package's original
> Upstart
> > script (with the local-filesystem condition intact), the sixxs interface
> is
> > still present on resume.
>
> Always good to know that the unmodified version works fine ;)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1058883
>
> Title:
> start-on conditions in Upstart script prevent aiccu from restarting
> during resume from suspend
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1058883/+subscriptions
>