The wchan command, thus the mention that it wasn't on my system. I suppose it is also not on yours: http://ou800doc.caldera.com/SM_dump/wchan.html
Not to pick nits, but that's not a command, it's a preprocessor macro from the kernel sources. Not really anything that could be used on a command line. Or maybe that's what you were getting at.
Who said anything about a linux dev? I would be a linux adm.
In my experience, the line between the two tends to blur quite frequently. *grin*
I use debian, but now I see my problem. I looked for select(2) and wait4(2) on a mail server in between doing other things on it. I don't have the developers manual pages there, but I do on another system.
Ahh. Since you were inquiring into the fiddly bits of the OS, I assumed that you were working on something with the source, and would be looking about on a machine with all the normal development tools and documentation pertinent to what you were looking for. My appologies.
One user had written a perl script through cron that made a connection to a sql server that was hanging. The process showed a wchan of select and I wanted to see if I could determine more information about it through this method. I now know the answer is no, this process was simply waiting on an i/o handle. The problem turns out to be in DBD::Sybase.
Good to know!
-Brad
_______________________________________________ EuG-LUG mailing list [EMAIL PROTECTED] http://mailman.efn.org/cgi-bin/listinfo/eug-lug
