On Tue, Dec 03, 2002 at 10:51:20PM -0800, Todd Lyons wrote: > Ryan T. Sammartino wrote on Mon, Dec 02, 2002 at 05:43:05PM -0800 : > > Did not help. > > Any other info I can provide that might narrow this down? > > What I would do is bring it down to runlevel 1. This should stop all > services and you should have basically nothing when you do a netstat. > Verify that. > > Then start one service at a time and see if you can narrow down any > particular service that seems to trigger it. Also, try tell it not to > resolve hostnames (netstat -pn). Maybe an overly large dns response is > creating some kind of havoc (we're reduced to the SWAG method now :)
Don't need to... the strace stop trying to do something with /dev/log, and netstat -x lists /dev/log first: # netstat -x Active UNIX domain sockets (w/o servers) Proto RefCnt Flags Type State I-Node Path unix 12 [ ] DGRAM -979118814 /dev/log and then # netstat -xp Active UNIX domain sockets (w/o servers) Proto RefCnt Flags Type State I-Node PID/Program name Path Segmentation fault So something to do with /dev/log... what daemon is responsible for that? # rpm -q -f /dev/log file /dev/log is not owned by any package Anyways... according to urpmi, I do have the latest devfsd: # rpm -q devfsd devfsd-1.3.25-22mdk Maybe sysklogd? # rpm -q sysklogd sysklogd-1.4.1-4mdk ps -aux doesn't reveal any obvious processes that might be touching /dev/log, besides devfsd. Anything else? -- Ryan T. Sammartino http://members.shaw.ca/ryants/ "What time is it?" "I don't know, it keeps changing."
