Nicholas Marriott <nicholas.marri...@gmail.com>: > Yes, it is probably because it is setuid. fdm calls kill(pid, 0) to see if the > process has actually started. This isn't actually needed, it is a debugging > aid. In any case, if it gets EPERM it is probably safe to assume the process > does exist. Please try this diff:
Ian, since I didn't hear from you again I suppose you require assistance in trying the diff Nicholas provided. See <http://ft.bewatermyfriend.org/tmp/fdm_deb.html>. There's a link to an extended debian patch against fdm_1.5.orig.tar.gz, which is also available from there. Which those you can build a debian package that includes said patch. Since (from your initial report) you seem to be on a i386 machine, you can also use the .deb provided there, here is a quick link: <http://ft.bewatermyfriend.org/tmp/fdm_1.5-patched_i386.deb> Note, that this a not a properly updated package yet. It currently only includes the new patch in addition to the old package. No updated documentation, no nothing. We need to make sure it fixes the problem and doesn't break anything before attempting to touch 'stable'. Please try it and report back. Regards, Frank -- In protocol design, perfection has been reached not when there is nothing left to add, but when there is nothing left to take away. -- RFC 1925 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
