Valery V.Bobrov wrote:
> Hello!
>  
> I have read article "How do I get Zenoss to start at boot time?" at the
> FAQ section, however, I've got a question.
> I have installed zenos on FreeBSD version 6.1
> I added line "export ZENHOME=/usr/local/zenoss" into the
> $ZENHOME/bin/zenoss script as recommended.
> But, my question is under which user(root or zenoss) should I run
> "*zenoss start*" script during server startup?
>  
> Can anyone send me an example of zenoss startup script for FreeBSD, please?
> Thank you in advance.
>  
> Also I would like to ask a question about starting *zenping* and
> *zensyslog.*
> Under which user(root or zenoss)?
> I read the INSTALL.txt file.
> There are  phrases:
> "Start zensyslog (it will need to be run as root to open its socket)"
> "Start zenping (it will need to be run as root to open a raw socket):"
>  
> I understand it. In order to open socket, of course, I need root privileges.
> But zenoss script starts and stops all services:
> "expected output:
>  
>     Daemon: zeoctl program running; pid=23589
>     Daemon: zopectl program running; pid=9768
>     Daemon: zenmodeler program running; pid=23603
>     Daemon: zenperfsnmp program running; pid=30202
>     Daemon: zenperfxmlrpc program running; pid=20132
>     Daemon: zenping program running; pid=1806
>     Daemon: zensyslog program running; pid=19222
>     Daemon: zenstatus program running; pid=1967
>     Daemon: zenactions program running; pid=23666"
>  
> Could anybody explain me under what user's rights(root or zenoss) should
> I  start the following scripts:
> zenoss,
> zenping
> zensyslog,
> please?
>  
> Thank you in advance
>  
> Valery.
> 

Valery

As far as I know, and I may be contradicted, but everything in
/zenoss/bin should be run as zenoss user.  The $ZENHOME environmental
variable isn't populated under root and should only be available under
the zenoss user.

John

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to