topic Using another user to run a script yields error in Operating System - HP-UX

Using another user to run a script yields error

Yeo Khian Wei — Mon, 01 Mar 2004 07:41:48 GMT

Hi
I had created this script owned by root that will execute a script owned by another user. if I execute the script on the command prompt, everyting goes through. But if I use nohup to execute the script at the backend. It returns the error -
Cannot start job control
stty: : I/O error.
My script (owned by root) is as follows -
su - testusr1 -c "/home/testusr1/test_print.sh"
Can someone please advise me? Thanks!

Re: Using another user to run a script yields error

RAC_1 — Mon, 01 Mar 2004 07:53:50 GMT

Do you have any interactive steps in user's script? Also make sure that all required variables are put in user's script. One way to do it is putting env at the start os the user's script.

You can run script as sh -vx ./script and check where it is failing.

Re: Using another user to run a script yields error

Michael Schulte zur Sur — Mon, 01 Mar 2004 08:17:10 GMT

Hi,

would it be a big deal to post the script as attachment?
Is the script trying to change attributes of the tty?

Michael

Re: Using another user to run a script yields error

Yeo Khian Wei — Tue, 02 Mar 2004 00:44:42 GMT

Hi
I had executed the script using the sh -vx command. I do not see any errors coming out from that. The only error that I see is when I used the nohup. My script is very simple, since it's for testing purpose, it is doing a single print statement thats all.

Regards,
Khian Wei

Re: Using another user to run a script yields error

Rory R Hammond — Tue, 02 Mar 2004 11:58:55 GMT

The su - is reading the testusr1 .profile and is causing your problem the stty setting is trying to talt to a terminal

If you are not worried about the environment
su testusr1 -c "/home/testusr1/test_print.sh" should work.
If you need the user env. set the need ones in the test_print.sh.

Rory

Re: Using another user to run a script yields error

Dave La Mar — Tue, 02 Mar 2004 14:29:06 GMT

I had run into same and found what Rory mentioned as part of the problem. The rest was taken care of when I placed the required environment variables in the script being executed.

Best of luck.

Regards,

dl