On Tue, 2001-11-27 at 03:31, Roger Keays wrote:
> Hi all,
>
> Has anybody seen this message in their /var/log/syslog?
> Nov 27 19:10:59 bilby inetd[31178]: /usr/sbin/tcpd: exit status 0x1
> Nov 27 19:10:59 bilby nmbd[3012]: connect from 192.168.0.6
> Nov 27 19:10:59 bilby inetd[31178]: /usr/sbin/t
Hi all,
Has anybody seen this message in their /var/log/syslog?
..
..
Nov 27 19:10:59 bilby inetd[31178]: /usr/sbin/tcpd: exit status 0x1
Nov 27 19:10:59 bilby nmbd[3012]: connect from 192.168.0.6
Nov 27 19:10:59 bilby inetd[31178]: /usr/sbin/tcpd: exit status 0x1
Nov 27 19:10:59 bilby nmbd[3013
* Moritz Schulte in "Re: strange log messages" dated 2000/07/18 01:33
* wrote:
> On Mon, Jul 17, 2000 at 05:35:28PM -0500, Ashley Clark wrote:
>
> > Jul 17 16:04:31 ghoti kernel: VM: do_try_to_free_pages failed for
> > squid...
>
> which kernel? 2.2.16 or earl
On Mon, Jul 17, 2000 at 05:35:28PM -0500, Ashley Clark wrote:
> Jul 17 16:04:31 ghoti kernel: VM: do_try_to_free_pages failed for
> squid...
which kernel? 2.2.16 or early 2.2.17pre's? it's a known bug in
them. upgrading to the last 2.2.17pre should solve the problem.
moritz
--
/* Moritz S
When I'm running vmware I get these strange log messages, should I
worry about them, are they deadly? My machine has 160 meg and vmware is
setup to allocate 64M for vmware clients.
Jul 17 16:04:31 ghoti kernel: VM: do_try_to_free_pages failed for
squid...
Jul 17 16:04:31 ghoti kerne
On Sun, 14 Mar, 1999 à 06:12:57PM -0600, Chris R. Martin wrote:
> Has anyone ever seen these messages before? Does anyone know what they mean?
>
> Mar 14 17:27:19 server init: Id "1" respawning too fast: disabled for 5
> minutes
> Mar 14 17:28:50 server init: Id "2" respawning too fast: disabled f
"Chris R. Martin" wrote:
>
> Has anyone ever seen these messages before? Does anyone know what they mean?
>
> Mar 14 17:27:19 server init: Id "1" respawning too fast: disabled for 5
> minutes
> Mar 14 17:28:50 server init: Id "2" respawning too fast: disabled for 5
> minutes
> Mar 14 17:29:39 ser
On Mon, 15 Mar 1999, Kris Van Heghe wrote:
> * Sometimes, after playing around for a while on the machine, if some
> command gives me an error, subsequent commands (whatever it is) produce
> only one output: 'Segmentation fault'. From that moment, there is only one
> solution: restarting the
here is only one
solution: restarting the machine, the 'dirty way'.
I hope some Linux-guru can give a little advice to solve these
'destabilizing' phenomena.
TIA
-Original Message-
From: Chris R. Martin [SMTP:[EMAIL PROTECTED]
Sent: maandag 15 maart 1999 1:1
At 06:12 PM 3/14/99 -0600, Chris R. Martin wrote:
>Has anyone ever seen these messages before? Does anyone know what they mean?
IIRC the answer to both questions is "YES".
Unfortunately, I don't have the answers :)
There was some discussion on this issue just recently. It may pay to check
the M
Has anyone ever seen these messages before? Does anyone know what they mean?
Mar 14 17:27:19 server init: Id "1" respawning too fast: disabled for 5
minutes
Mar 14 17:28:50 server init: Id "2" respawning too fast: disabled for 5
minutes
Mar 14 17:29:39 server init: Id "3" respawning too fast: disa
11 matches
Mail list logo