|
|
Posted by Ross Becker on 03/12/05 11:33
Ah. Well, then my bug report is probably of no matter. Even looking
further into SSH's options, there's something for controlling the TTY
allocated for SSH, but it only controls what TTY SSH allocates, there is
no means for turning tty allocation off completely. I was still holding
out some hope that this was my system configuration, and not something
fundamental in how PHP or worse- SSH acted.
Ross
Rasmus Lerdorf wrote:
> Ross Becker wrote:
>
>> I think you're probably right. My gut is telling me that this has to
>> do with tty funkiness. I tried the batchmode option, but it didn't
>> affect the problem. My bet is that ssh is mucking around with ttys,
>> and PHP is loosing it's connection through apache. The php processing
>> may actually be completing, it's just no longer sending it's output
>> through apache, and apache hasn't figured that out, so apache is
>> standing around waiting for PHP to complete. I'm hoping that the PHP
>> devs may get around to this as a bug and decide it can be fixed-
>> maybe by resetting the tty after returning from a system or whatever.
>
>
> I am actually a PHP dev, believe it or not. Exactly which tty is it you
> are suggesting we reset? There is no tty here. You can't run
> interactive things that require a controlling tty from something which
> doesn't have one without some really nasty tricks.
>
> -Rasmus
Navigation:
[Reply to this message]
|