>> The third party scripts use "sudox", which ... internally uses sudo. >> ... in scripts with long operations such as this one, the password >> timeouts may cause some permission problems
The idea behind "sudox" (= sudo eXtended ;-) is the following (this is the also the behavior when compiling via command line, for example with do-all): - if you are root, just execute the command (no questions asked) - if you are a normal user: - if SUDOPWD environment variable is defined, use this for sudo password (no questions asked) - else use normal sudo behavior (i.e. when sudo is executed later during the session, ask for password and remember it for the predefined time, usually 5 minutes) When compiling via menu3p, the script asks for sudo password at the beginning and - if the given password is not correct, it notifies the user and aborts - else remembers the password in SUDOPWD for all future sudo commands within the session (no more questions asked) Therefore, if using menu3p, you cannot get the normal sudo behavior - it either works without questions or it aborts immediately. >> Do you need sudo for third party tool install normally? Yes, because tools are installed to /usr/local or /opt/local directories. In short - compile as root and no questions will be asked or compile as normal user and no or max. 1 question will be asked. >> I did do a clean all (ca) before recompiling. Perhaps a file >> permission is messed up, but it's running via sudo. In this case the switch for overwriting the existing file when uncompressing was missing, which has now been added. Everything else (sudo, permissions, ...) was and should be OK. Please update to the latest revision and try again. Matjaz _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
