Very Computer

Okay, not too sure if I missed an update somewhere or something, but
I'm having a problem with previously made shell scripts that ran fine
in 6.2, but don't in 7.1 or 7.2.

The command that's giving me greif is the 'exec' command. I have a
shell that has a line that looks like:
exec /usr/local/uddp/udenv.sh
This is all fine and dandy in 6.2. The main shell will then execute
'udenv.sh' (which loads environment vars). Another example is:
exec /usr/local/voxcd/voxcd.sh
This works fine as well (the voxcd.sh shell calls a program after
setting up environmentals.) in 6.2..

In 7.1/7.2, what is SEEMING to happen is the exec command is executing
the shells with not tty attached to them. So when I run the calling
shell, I see nothing. In fact, I can't even abort it, interrupt it,
suspend it from that tty. The only way to kill it is to kill-9 the
process id (from another tty.)

Have I been using the 'exec' command incorrectly, or was something
changed that I should be aware of?

Thanks!
Mike.

The purpose of the 'exec' command is to transfer the current process to
the command listed as its argument.

That is: you can run the same command with or without the 'exec"
command.

If you do it without the 'exec' then the shell you execute the command
in will remain and control will be returned to it after the command is
finished.

If you do it with the 'exec' command, another process is not created and
control passes to the command -- it doesn't come back.

You probably want to use: 'source' which will run the command script as
though it was part of the script you call it from.

JRT