I am not sure if this is the right forum since this may very well
be a problem with Netscape Communicator (4.03) and not with kerneld.
However, at this point, I am not sure, which one is causing my
problem.
I have a dialup connection (SLIP) to my ISP, and normally this is
down. Under such circumstances, when I invoke netscape, the first
click I do usually triggers the netscape routine to load the home
page. When the link is down, this results in a number of popup
messages telling me that DNS was not available, the URL was not found,
etc, etc. While this happens, the 'Stop' icon on the 'Navigation
Toolbar' lights up as red. But once the determination has been made
that the network is is not available, the light goes out.
I made the interesting discovery today that if, while doing 'make
config', I set CONFIG_KERNELD to 'y', I run into problems with this
scenario. I have been testing with kernels 2.0.30 thru 2.0.35 and
pre36 patch 21, and for all of these, the load homepage routine of
Communicator creates a zombie 'request-route' and hangs the program.
Communicator cannot be closed and must be killed. Normally, on
loading, two processes with the name of 'netscape' are spawned. Under
the scenario I have described, 4 or five such processes are spawned
and they are all left running when I kill netscape.
This is at present an annoyance - nothing more. But I would like
to know why CONFIG_KERNELD is causing such behaviour. Any idea?
Thanks in advance,
Kenneth Stephen
-- There is no such thing as luck. 'Luck' is nothing but an absence of bad luck.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/