The 03.10.17 at 12:26, Kastus wrote:
/etc/ppp/ip-up.local.doit &
I would advise to look into your ip-up.local.doit script, there might be something wrong inside it.
I did, I did... I had a line: /etc/ppp/ip-up.local.doit & Just that, nothing strange. No wait command. And till the child exited, the pppd daemon did not say that ip-up had finished. Strange, yes... but unless it thought ip-up had finished, it refused to call ip-down. Maybe it has something to do with not having a terminal asociated, or that it is started from a daemon?
Parent process DOES exit. Please try yourself the following example:
I tried, and I agree, your sample works. But the same idea in ip-up.local, did not. I might try again, but I'm reluctant to do so, as it is working in my twisted ways ;-) Ok, I try - offline. 14769 pts/13 S 0:00 /bin/bash /etc/ppp/ip-up.local.doit now 14773 pts/13 S 0:00 \_ /bin/bash /etc/ppp/ip-up.local.doit now 14779 pts/13 S 0:00 \_ /usr/bin/fetchmail -v -L /var/log/fm.log You seem to be right, not ip-up nor ip-up.local show as processes there. However... I'm sure that if I try on line via the ppp daemon, "he" will insist the script has not finished (a wait command, perhaps?). I'm curious, I'll try in some minutes. -- Cheers, Carlos Robinson