Maintain su'd user during script?

[Jeff Crump]

I am attempting to su to a user (su - prandall) within a script but when I look at the output (> /home/prandall/log.txt) the next command (whoami) after the su does not appear to be executed by prandall. The system shows a logout.

How do I maintain the su'd user during the entire script?

Thanks,

Jeff

[Patrick Wallek · Accepted solution]

You don't.

The better thing to do would be to write a separate script with the commands you want to run as the prandall user. Then execute that script like this:

su - prandall -c scriptname

[Pete Randall]

The answer is obvious: because I didn't execute it!!

;^)


prandall

[Jeff Crump]

Patrick:

Thanks, I had seen that kind of reference before ... this helped a lot. However, I do have a follow-up question:

The script I am calling contains the following:

#!/bin/sh

# Look at what kind of file is being transferred and execute the appropriate compile command

case "$vcsfile_suffix" in
".qks") qd $vcsfile;;
".cob") sc_cobcomp $vcsfile;;
esac

fi

exit 0

Aside from the fact that I don't see a new object file being created (I'm transferring a .qks file and the qd command is supposed to do a compile and write an object) how can I get a copy of what is happening within the script to see WHY my new object isn't being created.

The qd command works from the command line if you enter the file name after it and I know the system I calling the script from is passing the $vcsfile variable.

Thanks,

Jeff

[Patrick Wallek]

Try something like this:

su - prandall -c command > logfile 2>&1