Re: [sipX-dev] Input on XCF-651 implementation (Restore page from sipXconfig UI)
Andy Spitzer wrote:
Woof!
On Tue, 03 Apr 2007 15:49:44 -0400, Damian Krzeminski <damian@xxxxxxxxxxx>
wrote:
The different is that by using '/etc/init.d/sipxpbx' you'd be stopping/starting
watchdog and httpd
(possible some other services). Process manager would restart services without
restarting itself.
Just using process manager to restart the services doesn't cause the
configuration scripts to be run. Dunno if you need to or not, just pointing
out that that step is done by the init.d script.
Process manager will run the process starting script (sipxconfig.sh etc.), and starting script would
parse configuration files if necessary. (At least this is what sipXconfig relies on now when
restarting services.)
However restarting entire sipxpbx service is probably safer after restore
anyway.
I am with woof! on setuid, but quite frankly I am not crazy about sudo idea
either. That would
require that sipXpbx configures passwordless sudo access for 'sipx' user during
installation. I am
not sure if this is what admins would like - at least not by default.
I usually add the sipx user to the "wheel" group, and uncomment the '%wheel'
line in /etc/sudoers (if it doesn't come that way by default...I don't recall)
But does it have to be passwordless? Prompt the user for the sipx user
password (not roots).
--Woof!
I did not think about it: does 'sipx' user even have password?
If we do end up using sudo, let's not use wheel group; let's add a special line for 'sipx' in
'sudoers' instead. Or am I complicating this too much?
