Regarding the recently uploaded cron-3.0pl1-37, which should be showing
up on the mirror sites RSN, Joey Hess found the following problem during
an upgrade from -36.1:
On Jan 16, [EMAIL PROTECTED] (Joey Hess) wrote:
(In Bug#6634: cron: can't upgrade cron while cron job is running)
> Package: cron
> Version: 3.0pl1-37
>
> Setting up cron (3.0pl1-37) ...
> Installing new version of config file /etc/cron.daily/standard ...
> /usr/sbin/cron: can't lock /var/run/crond.pid, otherpid may be 443: Try
> again
> dpkg: error processing cron (--install):
> subprocess post-installation script returned error exit status 1
>
Cause:
It's because the prerm in -36 and -36.1 was hosed -- it never stops
the cron daemon, so when the -37 postinst tries to (re-) start the
daemon, it can't , because the old crond is still running. Sigh.
Temporary Workaround:
Before upgrading cron, issue
/etc/init.d/cron stop
and then do the install. If you've already tried once, and gotten
the 'already locked' message, you'll probably need to kill it by
hand, it looks like pid file gets screwed, and start-stop-daemon
can no longer find the right process.
I'll poke around tonight and see if I can figure the right
place to deal with it in the new scripts.
Steve Greenland
--
The Mole - I think, therefore I scream
"He was sweet and sincere and giving and good...
AND A CHERISHED NEIGHBOR UNDESERVING OF SUCH A
FATE!!
"Nevertheless, better him than me. Amen."
[Eulogy given by Banana PC Jr to Opus in Bloom County]
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
