On Fri, 22 Jan 1999, Tommy Wareing wrote:
> Adding diagnostics to modem.c...
>
> mon_syslog(LOG_INFO, "child trace point 8");
> setenv("MODEM", current_dev, 1);
> mon_syslog(LOG_INFO, "child trace point 9");
>
> trace point 8 is reached. 9 is not: the process simply exits.
>
> Removing the calls to setenv seems to make everything work.
I can understand why the setnev of DIALD_LINK might fail
if you haven't got a "linkname xxx" in your config but the
MODEM one happens first and that one has always been there.
Current_dev shouldn't be null or bogus or you would have died
earlier - unless it has been trashed somewhere. The only
other thing would be your environment getting trashed.
Unfortunately it all seems to work for me :-(.
Mike
--
.----------------------------------------------------------------------.
| Mike Jagdis | Internet: [EMAIL PROTECTED] |
| 280, Silverdale Road, Earley, | Voice: +44 118 926 6996 |
| Reading RG6 7NU ENGLAND | Work: +44 118 989 0403 |
`----------------------------------------------------------------------'
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
