I take it that is your own network? Try and have the dhcp server supply the proper domain to your clients. That may or may not clean this up. I'm not sure about how pump cleans and restores the resolv.conf or why you get a zombie.
--mike On 08 Aug 2001 20:07:47 +0200, Daniel Wagner wrote: > Michael Heldebrant <[EMAIL PROTECTED]> writes: > > > Hmmm. I have a pump.conf to not clobber my resolv.conf on address > > allocation. Just checking if you did. Perhaps this is a sleeping > > process waiting for you to let go of the address so it can restore your > > resolv.conf. I'm not sure otherwise what would do that. What does the > > syslog say about pump lines? Can you run pump -i eth0 --status for me? > > i've no idea what's this process is good for, that's why i asked. > > |[EMAIL PROTECTED]:~# pump -i eth0 --status > |Device eth0 > | IP: 172.16.0.243 > | Netmask: 255.255.0.0 > | Broadcast: 172.16.255.255 > | Network: 172.16.0.0 > | Boot server 172.16.0.1 > | Next server 172.16.0.1 > | Gateway: 172.16.0.1 > | Domain: foo.bar > | Nameservers: 172.16.0.1 > | Renewal time: Thu Aug 9 04:54:29 2001 > | Expiration time: Thu Aug 9 06:24:29 2001 > > and shouldn't the pump process restore the resolv.conf, if pump > changes it? and isn't resolv.conf a glibc thing, cause the kernel > whould be configured via the procfs? > > -- > daniel > > You will be singled out for promotion in your work. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
