On Thu, 20 May 1999, The Tech-Admin Dude wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I could add another one, top(1) frequently does that on this machine..
so whatever answers you get, be sure to forward them to me :).
Blast from the past, but since no one gave you an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I could add another one, top(1) frequently does that on this machine..
so whatever answers you get, be sure to forward them to me :).
On Wed, 19 May 1999, Luigi Rizzo wrote:
These programs are mostly tin and lynx and such interactive programs.
On Wed, 19 May 1999, Andre Rikkert de Koe wrote:
We are an ISP and we recently installed FreeBSD 3.1 on our main
logonserver. Since than almost every day we find timeconsuming processes
running while the user isn't even logged in (anymore). These programs are
I believe the easiest solution
I sent this question to newsgroup comp.unix.bsd.freebsd.misc but I found
the two answers I got not sufficient. The answers were like it's inherent
to Unix and Just kill those processes.
So now I'm trying the mailing list.
Hello FreeBSD users,
We are an ISP and we recently
In the last episode (May 19), Andre Rikkert de Koe said:
We are an ISP and we recently installed FreeBSD 3.1 on our main
logonserver. Since than almost every day we find timeconsuming
processes running while the user isn't even logged in (anymore).
These programs are mostly tin and lynx and
On Wed, 19 May 1999 18:01:57 +0200 (MET DST), Andre Rikkert de Koe
arikk...@surf.iae.nl said:
logonserver. Since than almost every day we find timeconsuming processes
running while the user isn't even logged in (anymore). These programs are
mostly tin and lynx and such interactive programs.
These programs are mostly tin and lynx and such interactive programs.
...
ee and pico are two more. ee is particularly annoying since it
is one of the supported editors...
luigi
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the
On Wed, 19 May 1999, Andre Rikkert de Koe wrote:
I sent this question to newsgroup comp.unix.bsd.freebsd.misc but I found
the two answers I got not sufficient. The answers were like it's inherent
to Unix and Just kill those processes.
So now I'm trying the mailing list.
Sir, you may want
On Wed, 19 May 1999, Andre Rikkert de Koe wrote:
I sent this question to newsgroup comp.unix.bsd.freebsd.misc but I found
the two answers I got not sufficient. The answers were like it's inherent
to Unix and Just kill those processes.
So now I'm trying the mailing list.
As pointed out by
It's usually due to a bug in the application. When a user exits, the
stdin/stdout filedescriptors on any backgrounded processes go away.
That makes any read() calls return with an error. If the application
doesn't check the return value of its read(), it can go into a tight
loop it'll
10 matches
Mail list logo
