| Bug#: 20327 | Product: Gentoo Linux | Version: unspecified | Platform: All |
| OS/Version: Linux | Status: RESOLVED | Severity: normal | Priority: P2 |
| Resolution: FIXED | Assigned To: aliz@gentoo.org | Reported By: r.s.a.vandomburg@student.utwente.nl | |
| Component: Ebuilds | |||
| URL: | |||
| Summary: broken stop() in foldingathome init.d script | |||
| Keywords: | |||
| Status Whiteboard: | |||
| Opened: 2003-05-02 09:05 0000 | |||
| Description: | Opened: 2003-05-02 09:05 0000 |
Currently, stop() in /etc/init.d/foldingathome only tries to kill FahCore_78.exe. However, the exact filename depends on the actual project running. For instance, my Folding@Home 3.24 is currently running FahCore_65.exe. This causes the computation core to be shutdown incorrectly. Although I haven't experienced any grave failures (i.e. lost work or anything of the kind) other than complaints on the console, I have attached a substitute init.d script. This new init.d script basically cycles through all available projects in /opt/foldingathome and tries to shutdown every one of them.
Created an attachment (id=11383) [details]
Fixed /etc/init.d/foldingathome
Fixes stop() by cycling through all available projects.
Created an attachment (id=11485) [details]
Fixed /etc/init.d/foldingathome (revised)
A cosmetic update to the previous version. Now only kills FahCore*.exe,
supressing all output if one of the cores wasn't running.