Tyler Opatrny wrote:
> [posted to rush.general]
>
> we had the same problem on a linux box. This is what we did.
>
> stopped the rush service
> uninstalled rush
> We coppied over the install files, and ran a chmod 777 of the rush
> folder before installing installed it.
> gave it the latest host list
> started the rush service
> it worked after that.
Hmm, no, I would not ever recommend chmod 777 of the
rush directory. That's just an invitation for someone to
root the machine.
With perms like that, an ordinary user could rename out the
/usr/local/rush/etc or /usr/local/rush/bin directories,
and install their own programs that would run their commands
as root when the machine reboots to start the daemons.
No, you want the /usr/local/rush directory, and its subdirs
to be 755, and the rush and rushd binaries to be 4755 root/root.
The 'install.sh' script tries to enforce the rush and rushd
binary perms to prevent such problems. The only way they could
be changed is by someone manually changing the perms after the
install.sh script is run, which shouldn't happen.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|