On %M 0, Kris wrote > At 03:36 17/05/1999 +0000, you wrote: > >A quick kludge that might fix your problem (it fixed it on my machine under > >hamm, and after I get done upgrading to slink, I'm going to try it there) is > >to kill inetd. I think the problem revolves around the netbase script in > >the /etc/init.d folder trying to use ifwadm(or something like that) instead > >of ifchains(or something like that). I still don't understand why this > >works or why the problem has never happened to me before now with the 2.2 > >kernels under both hamm and slink, but thought this info might be of use to > >you. > > Nope. inetd has been well and truly slaughtered, and nothing changes (even > renamed it to make sure it didn't get restarted... call me strange). > > Output of 'ps ax' while connected (after I've killed gpm, portmap & inetd): > > init > [kflushd] > [kpiod] > [kswapd] > update > /sbin/syslogd > /sbin/klogd > /usr/sbin/atd > /usr/sbin/cron > -bash > -bash > /sbin/getty 38400 tty3 > /sbin/getty 38400 tty4 > /sbin/getty 38400 tty5 > /sbin/getty 38400 tty6 > tail -f /var/log/debug > /usr/sbin/pppd call provider > sh /etc/ppp/ip-up ppp0 /dev/ttyS2 115200 195.147.135. ^^^^^^^^^^^^^^^^^^^^^^ > run-parts /etc/ppp/ip-up.d ^^^^^^^^^^^^^^^^^^^^^^ > sh /etc/ppp/ip-up.d/exim ^^^^^^^^^^^^^^^^^^^^^^ > /usr/sbin/exim -qf ^^^^^^^^^^^^^^^^^^^^^^ > ps ax >
These should run briefly when you start your session, and then be gone. If they are still running it may be that there is a problem with exim's setup that is preventing it from quitting in a timely manner, or it may just be a further symptom of the fact that your PPP connection isn't working. What happens if you kill /usr/sbin/exim-qf? John P. -- [EMAIL PROTECTED] [EMAIL PROTECTED] "Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark