All too frequently, Netscape will just stop responding
on my system. This is nothing new, it's been happening
to me for years with at least the last five versions of
Netscape and the last several versions of various Debian
and Rhedd Hatte rEDhAT ;-> distributions on various platforms.
So today, after saying some bad words when it happened
again, I ran strace to maybe get a clue as to what was
going on and I saw an endless stream of failed syscalls,
seemingly an attempt to write some HTTP into a socket.
I can see that no Enet traffic is being generated, so
this is a strictly local failure. Can anybody offer any
guesses as to why such might be happening? Behold:
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
write(26, "GET /q?s=someHTTPstring&d=1b "..., 539) = -1 EAGAIN (Resource temporarily
unavailable)
(HTTP string in those examples has been sanitized since it was
associated with some private porn^H^H^H^Hfinancial stuff...)
Note: The !@#$!! thing did eventually recover after about five minutes...
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
