Shaleh wrote:
>
> I am running 2.0.34 w/ no problems. Could it be a permission on the tty
> and not the executable??
No. Remember, the login process has already started, the user ('ed')
has
already gotten a tty, the system has printed to it (for example to tell him
he has no mail), only when it tries to exec the default shell does the error
occur. I can't see how tty access could cause this.
--
Ed
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]