Overclock.net › Forums › Overclockers Care › Overclock.net BOINC Team › stop Boinc from running at startup (linux)
New Posts  All Forums:Forum Nav:

stop Boinc from running at startup (linux)

post #1 of 11
8/8/11 at 11:44pm
Thread Starter 
I can't seem to find any option within Boinc Manager to stop Boinc from running at startup on ubuntu Natty x64. It isn't in my list of startup applications so is this anything anyone is familiar with?
My System
(13 items)
  		  
CPUMotherboardGraphicsRAM
Athlon II X4 645 Asus M4A785-M Radeon HD 6770 4GB Samsung/Kingston PC2-6400 800MHz 6-6-6-18 
Hard DriveOSPowerCase
WD 1TB Windows 7 x64 Antec Earthwatts 650w Cooler Master Elite 310 
View all
  hide details  
Reply
My System
(13 items)
  		  
CPUMotherboardGraphicsRAM
Athlon II X4 645 Asus M4A785-M Radeon HD 6770 4GB Samsung/Kingston PC2-6400 800MHz 6-6-6-18 
Hard DriveOSPowerCase
WD 1TB Windows 7 x64 Antec Earthwatts 650w Cooler Master Elite 310 
View all
  hide details  
Reply
post #2 of 11
8/9/11 at 3:19am
Not really, you can stop the boinc-deamon (startup script) via this:
Code:
sudo gedit /etc/init.d/boinc-client
Type password and press enter, change the top ENABLE from ''0'' to ''1''
Problem is, when starting the boinc manager it will not be able to connect to the boinc client because it's not running. In Windows the client will start with the manager, in Linux not. I don't know how to start the boinc-client manually.

Code:
sudo /etc/init.d/boinc-client start
does not seem to work for me, only the restart function works.
Reply
Reply
post #3 of 11
8/9/11 at 2:06pm
To stop it from starting automatically, type

sudo update-rc.d -f boinc-client remove

This will remove it from the startup scripts. If you want to re-add it later, type

sudo update-rc.d boinc-client defaults 99

I believe Stef is right, though, that later on you will have to manually start the service or the manager will not connect to anything. The following three commands may be useful:

sudo /etc/init.d/boinc-client stop
sudo /etc/init.d/boinc-client start
sudo /etc/init.d/boinc-client restart

This is presuming you installed it through the repository, NOT through the Berkeley website. Let me know if this works for you.

edit:
Just removed from startup scripts, rebooted. Did not autostart. Manager connected to nothing. Manually started using the /etc/init.d/boinc-client start, and the manager then connected. Then readded to the startup using the second command in this post.

All seems to work fine for me. I'm running Natty. Also, starting in this manner can help resolve some issues with GPU detection. Are you trying to use GPU?
Edited by avesdude - 8/9/11 at 2:15pm
950
(16 items)
  		  
CPUMotherboardGraphicsRAM
i7 950 Asus X58 Sabertooth MSI R6970 Lightning Corsair XMS3 6GB 1600Mhz 
RAMHard DriveOptical DriveOS
Corsair Vengeance 12GB 2x ST Barracuda Raid 0 Asus, LG Win 7 Pro 
MonitorMonitorKeyboardPower
ViewSonic 19" HP w2207 NEC APC-H412 Corsair AX-850 
CaseMouseAudio
Antec 900 MS Laser 5000 Soundblaster X-Fi Titanium HD 
View all
  hide details  
Reply
950
(16 items)
  		  
CPUMotherboardGraphicsRAM
i7 950 Asus X58 Sabertooth MSI R6970 Lightning Corsair XMS3 6GB 1600Mhz 
RAMHard DriveOptical DriveOS
Corsair Vengeance 12GB 2x ST Barracuda Raid 0 Asus, LG Win 7 Pro 
MonitorMonitorKeyboardPower
ViewSonic 19" HP w2207 NEC APC-H412 Corsair AX-850 
CaseMouseAudio
Antec 900 MS Laser 5000 Soundblaster X-Fi Titanium HD 
View all
  hide details  
Reply
post #4 of 11
8/9/11 at 8:38pm
Thread Starter 
Quote:
Originally Posted by avesdude View Post
edit:
Just removed from startup scripts, rebooted. Did not autostart. Manager connected to nothing. Manually started using the /etc/init.d/boinc-client start, and the manager then connected. Then readded to the startup using the second command in this post.
This happened to me also... I ran sudo update-rc.d -f boinc-client remove
restarted, opened Boinc Manager and got the error "unable to connect to core." So i undid my changes and it's working again.
When I open up my task manager in Xubuntu, it's reading "../../projects/milkyway.cs.rpi.edu_milkyway_nbody_0.62_x86_64-pc-linux-gnu_mt -f nbody_parameters.......etc
So with that being said I don't think it's Boinc Manager auto starting but this project.
I'll try it your way you said in your edit.
p.s.
I'm using onboard graphics ... so not going to get any GPU work.
My System
(13 items)
  		  
CPUMotherboardGraphicsRAM
Athlon II X4 645 Asus M4A785-M Radeon HD 6770 4GB Samsung/Kingston PC2-6400 800MHz 6-6-6-18 
Hard DriveOSPowerCase
WD 1TB Windows 7 x64 Antec Earthwatts 650w Cooler Master Elite 310 
View all
  hide details  
Reply
My System
(13 items)
  		  
CPUMotherboardGraphicsRAM
Athlon II X4 645 Asus M4A785-M Radeon HD 6770 4GB Samsung/Kingston PC2-6400 800MHz 6-6-6-18 
Hard DriveOSPowerCase
WD 1TB Windows 7 x64 Antec Earthwatts 650w Cooler Master Elite 310 
View all
  hide details  
Reply
post #5 of 11
8/10/11 at 11:27am
It's something which is a downside on the linux boinc client. BOINC always starts before the wireless network (giving errors it can't connect) and before the X server (causing ´missing GPU' etc.). I haven't found a way to delay the client from starting, always fails.
Reply
Reply
post #6 of 11
8/10/11 at 11:54am
Quote:
Originally Posted by Stef42 View Post
It's something which is a downside on the linux boinc client. BOINC always starts before the wireless network (giving errors it can't connect) and before the X server (causing ´missing GPU' etc.). I haven't found a way to delay the client from starting, always fails.
I have the same problem. Have to stop and start it after boot to get it to recognize the GPU's...

Real pain... if you find a fix, let me know!



This is a related post at the F@H forum...

Quote:
Re: Folding@home SMP and BOINC Don't See GPU

--------------------------------------------------------------------------------

Finally some progress. I ran code that I found here

Code:
sudo /etc/init.d/boinc-client restart --- and now BOINC can now see my GPU

Quote:
Sun 30 Jan 2011 12:31:43 AM EST NVIDIA GPU 0: GeForce 9800 GT (driver version unknown, CUDA version 3020, compute capability 1.1, 511MB, 364 GFLOPS peak)

Apparently has something to do with when the driver and BOINC start in relation to each other.Now if only folding at home was that easy.
So, for now, I will give that a try to see if it works... and if it does, perhaps there is a way to put it into an automatic startup script somewhere to happen after login and X-Windows is started. Perhaps make it part of the BOINC Icon execution script?
Blue Beast
(13 items)
  		  
CPUMotherboardGraphicsRAM
i7-950 4.259GHz (HT On) 1.41v 24/7 Batch #3043A736 Asus P6X58D Premium DUAL EVGA GTX 560 Ti SC 1G in SLI 12G Corsair Dominator GT2000MHz 
Hard DriveOptical DriveOSMonitor
Corsair Force 90G SSD, 2x 1TB Barracuda HD's LG BlueRay/LightScribe Burner Windows 7 Pro 64Bit 3x24", 1x22" LCD 
KeyboardPowerCaseMouse
Wireless Logitech K320 ULTRA X4 1200W Custom Danger Den LDR-29 Wireless Logitech M310 
Mouse Pad
Custom 
View all
  hide details  
Reply
Blue Beast
(13 items)
  		  
CPUMotherboardGraphicsRAM
i7-950 4.259GHz (HT On) 1.41v 24/7 Batch #3043A736 Asus P6X58D Premium DUAL EVGA GTX 560 Ti SC 1G in SLI 12G Corsair Dominator GT2000MHz 
Hard DriveOptical DriveOSMonitor
Corsair Force 90G SSD, 2x 1TB Barracuda HD's LG BlueRay/LightScribe Burner Windows 7 Pro 64Bit 3x24", 1x22" LCD 
KeyboardPowerCaseMouse
Wireless Logitech K320 ULTRA X4 1200W Custom Danger Den LDR-29 Wireless Logitech M310 
Mouse Pad
Custom 
View all
  hide details  
Reply
post #7 of 11
8/10/11 at 12:13pm
This may be the fix... I'll try it later today...

http://boinc.berkeley.edu/dev/forum_thread.php?id=6307




Quote:
FIX #1: My fix was to add a delay into the start-up script so that GDM/X has a chance to have drivers fully loaded. This solution inserts a 6 second delay in the boinc start-up script which allows ample time for the driver to be available on all machines tested to date.
(a)Edit the start-up script file /etc/init.d/boinc-client with sudo gedit /etc/init.d/boinc-client.
(b)Find this function code and add the line “sleep 6” where it's shown here:

start()
{
log_begin_msg "Starting $DESC: $NAME"
if is_running; then
log_progress_msg "already running"
else
sleep 6
start-stop-daemon --start --quiet --background --pidfile $PIDFILE \\
--make-pidfile --user $BOINC_USER --chuid $BOINC_USER \\
--chdir $BOINC_DIR --exec $BOINC_CLIENT -- $BOINC_OPTS
fi
log_end_msg 0

if [ "$SCHEDULE" = "1" ]; then
schedule
fi
}
Blue Beast
(13 items)
  		  
CPUMotherboardGraphicsRAM
i7-950 4.259GHz (HT On) 1.41v 24/7 Batch #3043A736 Asus P6X58D Premium DUAL EVGA GTX 560 Ti SC 1G in SLI 12G Corsair Dominator GT2000MHz 
Hard DriveOptical DriveOSMonitor
Corsair Force 90G SSD, 2x 1TB Barracuda HD's LG BlueRay/LightScribe Burner Windows 7 Pro 64Bit 3x24", 1x22" LCD 
KeyboardPowerCaseMouse
Wireless Logitech K320 ULTRA X4 1200W Custom Danger Den LDR-29 Wireless Logitech M310 
Mouse Pad
Custom 
View all
  hide details  
Reply
Blue Beast
(13 items)
  		  
CPUMotherboardGraphicsRAM
i7-950 4.259GHz (HT On) 1.41v 24/7 Batch #3043A736 Asus P6X58D Premium DUAL EVGA GTX 560 Ti SC 1G in SLI 12G Corsair Dominator GT2000MHz 
Hard DriveOptical DriveOSMonitor
Corsair Force 90G SSD, 2x 1TB Barracuda HD's LG BlueRay/LightScribe Burner Windows 7 Pro 64Bit 3x24", 1x22" LCD 
KeyboardPowerCaseMouse
Wireless Logitech K320 ULTRA X4 1200W Custom Danger Den LDR-29 Wireless Logitech M310 
Mouse Pad
Custom 
View all
  hide details  
Reply
post #8 of 11
8/10/11 at 12:29pm
I have had a lot of trouble getting boinc to work reliably at startup. Adding delay to the startup script, removing it then readding it as per above using the update-rc.d, nothing has really worked.

If I want boinc to use the GPU I have to manually restart it once the computer is running using the /etc/init.d/boinc-client restart

As to the OP's question:
If you remove the startup command with the update-rc.d as you mentioned, you should get a "cannot connect to client" error when you run the manager. Boinc on Linux separates the Boinc Manager and the science. On Windows starting the Boinc Manager automatically starts the science apps. To solve the error without readding boinc to the startup scripts you need to manually run "sudo /etc/init.d/boinc-client start" before you run the Manager.
950
(16 items)
  		  
CPUMotherboardGraphicsRAM
i7 950 Asus X58 Sabertooth MSI R6970 Lightning Corsair XMS3 6GB 1600Mhz 
RAMHard DriveOptical DriveOS
Corsair Vengeance 12GB 2x ST Barracuda Raid 0 Asus, LG Win 7 Pro 
MonitorMonitorKeyboardPower
ViewSonic 19" HP w2207 NEC APC-H412 Corsair AX-850 
CaseMouseAudio
Antec 900 MS Laser 5000 Soundblaster X-Fi Titanium HD 
View all
  hide details  
Reply
950
(16 items)
  		  
CPUMotherboardGraphicsRAM
i7 950 Asus X58 Sabertooth MSI R6970 Lightning Corsair XMS3 6GB 1600Mhz 
RAMHard DriveOptical DriveOS
Corsair Vengeance 12GB 2x ST Barracuda Raid 0 Asus, LG Win 7 Pro 
MonitorMonitorKeyboardPower
ViewSonic 19" HP w2207 NEC APC-H412 Corsair AX-850 
CaseMouseAudio
Antec 900 MS Laser 5000 Soundblaster X-Fi Titanium HD 
View all
  hide details  
Reply
post #9 of 11
8/10/11 at 1:15pm
Why can't we put

sudo /etc/init.d/boinc-client start

Or something in the ICON or startup scipt and not have the client start automatically?

Blue Beast
(13 items)
  		  
CPUMotherboardGraphicsRAM
i7-950 4.259GHz (HT On) 1.41v 24/7 Batch #3043A736 Asus P6X58D Premium DUAL EVGA GTX 560 Ti SC 1G in SLI 12G Corsair Dominator GT2000MHz 
Hard DriveOptical DriveOSMonitor
Corsair Force 90G SSD, 2x 1TB Barracuda HD's LG BlueRay/LightScribe Burner Windows 7 Pro 64Bit 3x24", 1x22" LCD 
KeyboardPowerCaseMouse
Wireless Logitech K320 ULTRA X4 1200W Custom Danger Den LDR-29 Wireless Logitech M310 
Mouse Pad
Custom 
View all
  hide details  
Reply
Blue Beast
(13 items)
  		  
CPUMotherboardGraphicsRAM
i7-950 4.259GHz (HT On) 1.41v 24/7 Batch #3043A736 Asus P6X58D Premium DUAL EVGA GTX 560 Ti SC 1G in SLI 12G Corsair Dominator GT2000MHz 
Hard DriveOptical DriveOSMonitor
Corsair Force 90G SSD, 2x 1TB Barracuda HD's LG BlueRay/LightScribe Burner Windows 7 Pro 64Bit 3x24", 1x22" LCD 
KeyboardPowerCaseMouse
Wireless Logitech K320 ULTRA X4 1200W Custom Danger Den LDR-29 Wireless Logitech M310 
Mouse Pad
Custom 
View all
  hide details  
Reply
post #10 of 11
8/10/11 at 1:33pm
I'm getting an SSD today so I have to reinstall Ubuntu anyway. I'll try to figure out this BOINC issue in the weekend because it's annoying me aswell. I'll see what I can find...
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Overclock.net BOINC Team
Overclock.net › Forums › Overclockers Care › Overclock.net BOINC Team › stop Boinc from running at startup (linux)