Re: locks and shutdown policy; was Re: stale lockfile on fetchmail.
Andrew, Ron, Tzafrir and others, Thanks for the clarifications. At Mon, 11 Feb 2008 19:14:58 -0800 as-w> ... fetchmail being killed in a nasty way ... We're still not exactly certain how the stale lock comes to exist but ... At Tue, 12 Feb 2008 09:11:39 + tc> fetchmail is a daemon, ... tc> fetchmail cleans that stale lock on (its) startup. System startup or my login invoking a fork of fetchmail? The user can remove the stale lock but a daemon should be able to run without intervention. Seems that the maintainer should be examining design of the locking mechanism. Reimplementation may be necessary. Unless we've overlooked something, this justifies a bug report. Thanks,... Peter E. http://carnot.yi.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: locks and shutdown policy; was Re: stale lockfile on fetchmail.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/12/08 03:11, Tzafrir Cohen wrote: > On Mon, Feb 11, 2008 at 04:58:57PM -0700, [EMAIL PROTECTED] wrote: >> Andrew, Ron & others, >> >> a> probably because fetchmail died (or ... >> >> Which can happen if a power failure occurs >> or I happen to reboot while fetchmail is >> retrieving. >> >> This strikes me as a bug. An obvious strategy >> would be to remove an old lock at startup. > > fetchmail cleans that stale lock on (its) startup. That lock may be in > the user's home directory. > >> I know nothing about shutdown policy. Does >> shutdown allow an application any leeway? >> Can a second or two of delay be invoked >> _via_ the xfsm-shutdown-helper? > > fetchmail is a daemon, and thus not part of a desktop. I don't suppose > that this could be handled in the SIGKILL signal handler either. fetchmail *can* be run as a daemon. (For some reason, I decided to run it from cron every X minutes. It runs a different divisor of 60 for myself, wife & two children.) - -- Ron Johnson, Jr. Jefferson LA USA PETA - People Eating Tasty Animals -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHseDnS9HxQb37XmcRAmjMAJ4k2BUvdne4BnHQxMiCKNyQZ5NaggCfSrRs GHB4f/mtGEMQ6hQ1D6bHb8Q= =vyGK -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: locks and shutdown policy; was Re: stale lockfile on fetchmail.
On Mon, Feb 11, 2008 at 04:58:57PM -0700, [EMAIL PROTECTED] wrote: > Andrew, Ron & others, > > a> probably because fetchmail died (or ... > > Which can happen if a power failure occurs > or I happen to reboot while fetchmail is > retrieving. > > This strikes me as a bug. An obvious strategy > would be to remove an old lock at startup. fetchmail cleans that stale lock on (its) startup. That lock may be in the user's home directory. > > I know nothing about shutdown policy. Does > shutdown allow an application any leeway? > Can a second or two of delay be invoked > _via_ the xfsm-shutdown-helper? fetchmail is a daemon, and thus not part of a desktop. I don't suppose that this could be handled in the SIGKILL signal handler either. -- Tzafrir Cohen | [EMAIL PROTECTED] | VIM is http://tzafrir.org.il || a Mutt's [EMAIL PROTECTED] || best ICQ# 16849754 || friend -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: locks and shutdown policy; was Re: stale lockfile on fetchmail.
On Mon, Feb 11, 2008 at 07:26:59PM -0600, Ron Johnson wrote: > On 02/11/08 17:58, [EMAIL PROTECTED] wrote: > > Andrew, Ron & others, > > > > a> probably because fetchmail died (or ... > > > > Which can happen if a power failure occurs > > or I happen to reboot while fetchmail is > > retrieving. > > > > This strikes me as a bug. An obvious strategy > > would be to remove an old lock at startup. > > /tmp is cleaned out at boot. Maybe the fetchmail lockfile is > somewhere else? > Yeah. I think this is more likely an issue of fetchmail being killed in a nasty way (kill -9 p signature.asc Description: Digital signature
Re: locks and shutdown policy; was Re: stale lockfile on fetchmail.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/11/08 17:58, [EMAIL PROTECTED] wrote: > Andrew, Ron & others, > > a> probably because fetchmail died (or ... > > Which can happen if a power failure occurs > or I happen to reboot while fetchmail is > retrieving. > > This strikes me as a bug. An obvious strategy > would be to remove an old lock at startup. /tmp is cleaned out at boot. Maybe the fetchmail lockfile is somewhere else? > I know nothing about shutdown policy. Does > shutdown allow an application any leeway? > Can a second or two of delay be invoked > _via_ the xfsm-shutdown-helper? - -- Ron Johnson, Jr. Jefferson LA USA PETA - People Eating Tasty Animals -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHsPXjS9HxQb37XmcRAuBoAKCeSrM4La/3tT1bH29I4SQfJefohwCeIvnd BDlT0srMYzk+ZYSQUfm6gq0= =f83V -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
locks and shutdown policy; was Re: stale lockfile on fetchmail.
Andrew, Ron & others, a> probably because fetchmail died (or ... Which can happen if a power failure occurs or I happen to reboot while fetchmail is retrieving. This strikes me as a bug. An obvious strategy would be to remove an old lock at startup. I know nothing about shutdown policy. Does shutdown allow an application any leeway? Can a second or two of delay be invoked _via_ the xfsm-shutdown-helper? Thanks,... Peter E. Desktops.OpenDoc http://carnot.yi.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
