| Summary: | /etc/init.d/boinc attach fails with sched_setscheduler error | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Nick Gotsinas <darf> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | djsmiley2k |
| Priority: | High | ||
| Version: | 2008.0 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge info
output of /etc/init.d/boinc --debug start boinc.conf |
||
Please attach emerge --info and emerge -pvq boinc. Created attachment 191574 [details]
emerge info
emerge --info
(In reply to comment #2) > Created an attachment (id=191574) [edit] > emerge info > > emerge --info > emerge -pvq boinc % [ebuild R ] sci-misc/boinc-6.4.5-r2 USE="X server -cuda" Please attach the ouptut of /etc/init.d/boinc --debug start to this bug. Created attachment 191871 [details]
output of /etc/init.d/boinc --debug start
Are you using boinc under existing user? Also arent you trying to run boinc as root, are you? (In reply to comment #6) > Are you using boinc under existing user? > Also arent you trying to run boinc as root, are you? > These two you can find by pasting your /etc/conf.d/boinc Please attach your /etc/conf.d/boinc file as Tomáš requested. Reopen this bug when you provide the requested information. Created attachment 206355 [details]
boinc.conf
/etc/conf.d/boinc
(In reply to comment #9) > Created an attachment (id=206355) [details] > boinc.conf > > /etc/conf.d/boinc > I have the exact same issue - Wasn't sure if I should clone the bug? - Attached requested info, hope this helps |
Boinc fails to start when trying to attach, not sure what else I can show I have no idea what the sched_setscheduler error means and google isn't helping either. % /etc/init.d/boinc attach Enter the Project URL: http://setiathome.berkeley.edu Enter your Account Key: mykey * Attaching to project ... [ ok ] sched_setscheduler: Invalid argument failed to set pid 0's policy sched_setscheduler: Invalid argument failed to set pid 0's policy sched_setscheduler: Invalid argument failed to set pid 0's policy sched_setscheduler: Invalid argument failed to set pid 0's policy sched_setscheduler: Invalid argument failed to set pid 0's policy It does however work if I start it manually: % boinc_client --daemon --dir /var/lib/boinc --allow_remote_gui_rpc --attach_project http://setiathome.berkeley.edu/ mykey The above works and does stuff, however the gui fails to connect.