Bug 9535 - foldingathome-3.14.ebuild (new ebuild)
|
Bug#:
9535
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: x86
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: aliz@gentoo.org
|
Reported By: ryan.shaw@stanfordalumni.org
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: foldingathome-3.14.ebuild (new ebuild)
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2002-10-23 03:03 0000
|
This will install the folding@home client along with a boot script that allows
the user to run the client at boot. It is modelled after the setiathome ebuild.
I'm not sure about the nobody.nogroup stuff here. The setiathome ebuild was
chowning the directory and executable to nobody.nogroup. I believe it was
intending to set the executable +s as well so that it would run as nobody.
But, I don't think the actual executable is being set +s in that ebuild,
perhaps due to a typo (it has "chmod +s ${S}/setiathome" where it should
probably have "chmod +s ${D}/${I}/setiathome"). In any case, I was under
the impression that daemons which create files should NOT be run as "nobody"
because "nobody" should never own any files on the system.
I've submitted another version of the ebuild without the nobody.nogroup stuff.
The reason is that even if foldingathome is set +s and runs as user nobody,
another process called FahCore_c9.exe is started that runs as root.
FahCore_c9.exe is downloaded by foldingathome after it starts running, and if we
later chown the downloaded/created files and FahCore_c9.exe to nobody and set
FahCore_c9.exe +s, foldingathome starts having problems. So, for now I am just
running it as root.
yeah the whole seti@home stuff is weak ... i'm in the process of re-writing it
now ;)
(and i was the one who wrote most of the original seti@home stuff heh)
Commited, thanks for the ebuild!
