anacron killed immediately after resume from suspend state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sysvinit (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: anacron
If I resume my system from hibernate, anacron is started, but killed immediately afterwards. This bug is reproducible.
/var/log/syslog has this:
Dec 17 16:14:47 auster kernel: [135486.210318] PM: resume devices took 7.220 seconds
Dec 17 16:14:47 auster kernel: [135486.210341] PM: Finishing wakeup.
Dec 17 16:14:47 auster kernel: [135486.210342] Restarting tasks ... done.
Dec 17 16:14:47 auster acpid: client 1618[0:0] has disconnected
Dec 17 16:14:47 auster acpid: client 1618[0:0] has disconnected
Dec 17 16:14:47 auster acpid: client connected from 1618[0:0]
Dec 17 16:14:47 auster acpid: client connected from 1618[0:0]
Dec 17 16:14:47 auster anacron[31175]: Anacron 2.3 started on 2009-12-17
Dec 17 16:14:47 auster anacron[31175]: Will run job `cron.daily' in 5 min.
Dec 17 16:14:47 auster anacron[31175]: Jobs will be executed sequentially
Dec 17 16:14:47 auster init: anacron main process (31175) killed by TERM signal
>uname -a
Linux auster.zuhause 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:02:15 UTC 2009 x86_64 GNU/Linux
>cat /etc/issue.net
Ubuntu 9.10
Changed in sysvinit (Ubuntu): | |
assignee: | nobody → Ubuntu Core Development Team (ubuntu-core-dev) |
Changed in sysvinit (Ubuntu): | |
assignee: | Ubuntu Core Development Team (ubuntu-core-dev) → nobody |
Changed in sysvinit (Ubuntu): | |
status: | New → Confirmed |
This bug was already discussed in some forums
http:// forum.ubuntuuse rs.de/topic/ init-anacron- killed- by-term- signal/ #post-2257598
http:// ubuntuforums. org/showthread. php?p=8482125
The "solution" in the second thread is a real hack and far form a bug fix.