Sorry for the delay. Only two people replied. Rob Vahsen said that it
works fine for him on
2.4 and sent me a list of installed patches. He had not installed the ksh
jumbo patch (which
I had). So probably it is the patch (102048) but I have not tested it by
removing the patch.
The original post is included at the end.
Thanks to :
Veronica Paul (veronica@uac.edu.au)
Rob Vahsen (vahsenr@ce.philips.nl)
- vasu
> Here is an interesting ksh problem/bug (on solaris 2.4 or 2.5)
>
> 'joe' is a user with ksh as the login shell. /tmp/x, /tmp/y and /tmp/z
> are shell scripts.
>
> % cat /tmp/x
> #!/bin/ksh
> echo yes
>
> %cat /tmp/y
> #!/bin/ksh
> su - joe -c /tmp/x
> su - joe -c /tmp/x
>
>
> %cat /tmp/z
> #!/bin/ksh
> su - joe -c /tmp/x
>
>
> To make things simple, 'joe' does not have any dot files (.profile,
.kshrc
> etc.) in his home. Though the following observations hold even if
> .profile, .kshrc etc are present. /etc/profile has not been modified at
> all.
>
> Now, here are some observations when these scripts are run by root
> (ineractively or non-interactively)
>
> * /tmp/z runs fine
> * /tmp/y runs the first "su" and then hangs. truss shows that the
> process
> is getting SIGTTIN's (and sometimes SIGTTOU's) continuously.
> * if "su -" is replaced with "su" in /tmp/y, it runs fine
> * if the shell in /tmp/z is changed to /bin/sh, it hangs
> * all the above hold for 2.4 (+ ksh jumbo patch) or 2.5
> * it is not the nfs-HISTFILE-locking problem
> * if joe's login shell is changed to /bin/csh all the scripts
> run fine.
>
> I fail to see why SIGTTIN's are being generated.
> Any ideas/solutions ? Thanks.
>
> - vasu
>
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:59 CDT