I have a job that runs a script; the script does an sudo and it appears to be waiting for a password. Cancelling the job doesn't kill it.
How can I kill the job? Is it safe to kill the job with the invoked shell script? I tested the sudo on the command line and it did not ask for a password; that was in a terminal in which I did an su. In contrast, the job is configured with Run Before Job = "super cyrus-prep" So I think it runs as bacula, does a "super" to root, and the offending line in the script is trying to sudo to cyrus. I guess the environment created by su is sufficiently "root" that sudo doesn't ask for a password, but the one created by super is not "root" enough. I used super because I had problems with su and sudo asking for passwords; I notice a lot of advice on this list to use sudo. Can anyone recommend how I can make this work properly in the future? The big picture is that before the job runs I need to run as root, mostly, but one of the items needs to be done as user cyrus. Thanks. Ross Boylan ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
