O/S Fedora Core 2: Kernel 2.6.10-1.12_FC2
Boinc version 4.19_i686
Einstein version 4.76
When running the boinc executable from the command line and using Ctrl-C to end the app, the lockfile is not removed. Trying to restart boinc gives a message that another instance of boinc is running. The lockfile must be manually deleted to start boinc. The Ctrl-C key sequence is used as directed by the UNIX install instructions.
Copyright © 2024 Einstein@Home. All rights reserved.
Linux: Lockfile Problem
)
# killall boinc
works for me. :)
Happy crunching
Neil
Be lucky,
Neil
> O/S Fedora Core 2: Kernel
)
> O/S Fedora Core 2: Kernel 2.6.10-1.12_FC2
> Boinc version 4.19_i686
> Einstein version 4.76
>
> When running the boinc executable from the command line and using Ctrl-C to
> end the app, the lockfile is not removed. Trying to restart boinc gives a
> message that another instance of boinc is running. The lockfile must be
> manually deleted to start boinc. The Ctrl-C key sequence is used as directed
> by the UNIX install instructions.
>
I have this problem to with FC3, I think. When I deleted the lock file I can run boinc with the various commands but trying to do normal work cause a lot of error messages about Seti being outside something, can't recall details. So I ran boinc while logged is as root and it created new project and slots directories plus the xml files in the /root directory. It runs just fine but now there is work "abandoned" in the /home/user directory and of course lots of logging in/out and cd'ing which is a pain. Any advice on how to get back to a normal arrangement and combine the two sources of wu's would be gratefully received.
Get BOINC WIKIed