da Silva, Joe wrote:
> Hi Michael.
>
> The problem I was referring to, with PPP.LOG remaining open,
> was not really a problem _within_ Arachne, but rather with
> DOS redirection. That is, the redirection of LSPPP's output
> to PPP.LOG (called directly or indirectly, by ARACHNE.BAT).
>
I understand. But as we cannot change DOs behaviour,
we can only find some workaround...
> I suppose the same thing would happen with redirection of
> EPPPD's output to PPP.LOG, unless this does it's own
Yes, its happening...
> redirection (instead of letting COMMAND.COM (?) do it)?
> I suspect however, that the problem _does_ exist when using
> EPPPD too, because this would explain the strange connect
> behaviour I would sometimes get, if my first dial attempt failed
> (IIRC). Perhaps Bernie can tell us if EPPPD does it's own
> redirection, or whether it let's DOS do it ...
Definitely DOS redirection, because it is done on
command line: EPPPD.EXE>>PPP.LOG ;-)
> I noticed this effect because I normally run SHARE - however
> there are more subtle effects of this problem for those that
> don't run SHARE.
Hmm, I think we should get rid of it.
> It's good that you will be supporting LSPPP directly in Arachne
> and also that you will favour the BOOTP method in future,
> rather than the PPP.LOG method. Much better, IMHO. :-)
Probably yes. I am planning this too..
