Da Silva, Joe wrote:
> Some of you may recall, a little while ago, a consensus was reached,
> that the 'lspppcfg' package should redirect the output of 'lsppp' to
> the 'ppp.log' file ...
>
> Alas, as it "turns out", the consensus view was flawed (oh, well!),
> because when the 'lsppp' program "goes resident", the 'ppp.log' file
> then remains "open". Because the 'ppp.log' file is read and written
> by other applications, these operations can either get muddled or be
> blocked (depending on whether 'share' is loaded).
>
Arachne is solving this by using sopen() to open ppp.log...
with some flags to deny_noone...., or something like that..
I can check it.
> Therefore, the 'cfg-ppp' program (in the 'lspppcfg' package) has
> been updated again, so that the 'lsppp' output is redirected to
> 'nul' (as previously). However, to be more informative, a message
> is now added to the 'ppp.log' file to indicate the success/failure
> of 'lsppp' in establishing a PPP link. In addition, the user can
> still redirect the output of 'lsppp' to the 'ppp.log' file, for debugging
> purposes, by issuing the command "SET DEBUG=PPP" at the
> DOS prompt, before invoking Arachne. Ironically, redirecting the
> output of 'lsppp' to 'ppp.log' should not cause any problems when
> the PPP link fails, because then 'lsppp' does not "go resident".
>
> In addition, the 'cfg-ppp' program now has a new option, called
> 'update', which will update an existing 'lspppcfg' installation,
> while preserving any configuration changes that have been made
> since the previous installation. Simply unzip the 'lspppcfg.zip'
> file into your Arachne directory, and type "cfg-ppp update".
I think my solution for lsppp will be anyway complete transfer from
PPP.LOG method to IP_Address bootp; in that case, PPP.LOG will
be closed after MINITERM exits.
