Lorry <fish at slava.net> wrote: > > Well, it's happened again, and the kill isn't working. I've done kill > pid and kill -9 pid and neither work. I still get the "already running" > message. When I ps, it doesn't show up in the list. What else could be > causing this and how can I stop it from happening? Has anyone else had > a similar problem? Thanks! I've never seen this happen with everybuddy, though you can take a look at the ~/.everybuddy/.lock file. Its contents should be the PID of a running everybuddy (don't know why it'd get confused about that). If everybuddy isn't running, try just removing the file. -- _ _ _ _ _ ___ _ _ _ ___ _ _ __ This one goes to eleven. / \/ \(_)| ' // ._\ / - \(_)/ ./| ' /(__ \_||_/|_||_|_\\___/ \_-_/|_|\__\|_|_\ __) [ Mike Hicks | http://umn.edu/~hick0088/ | mailto:hick0088 at tc.umn.edu ] -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available Url : http://shadowknight.real-time.com/pipermail/tclug-list/attachments/20011021/6d97cabd/attachment.pgp