Good morning, Martin-Éric Racine [Fri, Aug 07, 2009 at 05:14:21PM +0300]: > O0o.oops(): [daemon/check_kill.c(42)]: Problem reading from /var/run/gpm.pid > > [...] > ***** > > As the above shows, even though GPM's init script correctly calls > invoke-rc.d, > the source code itself insists upon seeing a real usable pid number in the > file, > even though this is not something that's gonna appear when unpacking packages > in > a chroot, such as when preparing a filesystem image for copying to JFFS2.
Sure it does. How should gpm be able to see whether it's running or not else? I guess alot other daemons also do this, so I'm a bit wondering why this problem with Debian comes up now. I'm a bit tired, but way more confused about this bug in general: Why should a any software care about that problem? And why is gpm started in this environment at el? Maybe I'm missing some Debian magic, but for an installation there's no requirement to start it. Greetings from the airport, Nico -- Currently moving *.schottelius.org to http://www.nico.schottelius.org/ ... PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C
signature.asc
Description: Digital signature
