Re: [leafnode-list] Cannot obtain lock file, aborting.

[Matthias Andree <ma@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>]

"Clemens Fischer" <ino-waiting@xxxxxxx> writes:

> if the signal-handler in such processes aren't programmed to release
> resources, they will remain allocated.  the kernel takes care about
> some resources automatically, but it cannot know about all of them.
> bad lockfile programming can't be repaired by the kernel if it cannot
> determine these files aren't to be used by other programs as well.

Regarding leafnode, the kernel should be able to track ALL resources
allocated. Leafnode's programs should also be able to clear out stale
lock files, the only case when this may fail is a) on network volumes
that multiple hosts can run fetchnews on, b) the machine has a different
name after a reboot that occurred while the previously running leafnode
program had not removed the lock file. (hard crash and moving hard drive
to different computer).

-- 
Matthias Andree

http://sourceforge.net/projects/leafnode/   - leafnode-1 tarballs
http://mandree.home.pages.de/leafnode/beta/ - leafnode-2 tarballs

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list