-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 16 Oct 2009 05:23:01 +0200
Tom H wrote:
> > I noticed this today - my syslog is filling up with repeated
> > calls to my internet provider...even though I am obviously connected.
> > Is this caused by some mis-configuration ?
> >
> > This is
> I noticed this today - my syslog is filling up with repeated
> calls to my internet provider...even though I am obviously connected.
> Is this caused by some mis-configuration ?
>
> This is the sort of thing I mean:
> Oct 14 19:02:21 squeeze dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 15 Oct 2009 12:29:12 +0800
Jerome BENOIT wrote:
> >>>
> >>> I noticed this today - my syslog is filling up with repeated
> >>> calls to my internet provider...even though I am obviously connected.
> >>> Is this caused by some mis-configuratio
Hello,
Frank McCormick wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 15 Oct 2009 08:39:43 +0800
Jerome BENOIT wrote:
I noticed this today - my syslog is filling up with repeated
calls to my internet provider...even though I am obviously connected.
Is this caused by some mis-c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 15 Oct 2009 08:39:43 +0800
Jerome BENOIT wrote:
> >
> >
> > I noticed this today - my syslog is filling up with repeated
> > calls to my internet provider...even though I am obviously connected.
> > Is this caused by some mis-configuration
Hello Franck,
Frank McCormick wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I noticed this today - my syslog is filling up with repeated
calls to my internet provider...even though I am obviously connected.
Is this caused by some mis-configuration ?
This is the sort of thing I mean:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I noticed this today - my syslog is filling up with repeated
calls to my internet provider...even though I am obviously connected.
Is this caused by some mis-configuration ?
This is the sort of thing I mean:
Oct 14 19:02:21 squeeze dhclient: DHCPR
I've installed pmount, dbus and hal and they seem to work fine,
although I noticed last night that my syslog file was over 2MB!
As long as my camera memory card reader is plugged in -- but with no
card in it -- /dev/sda is present (as I think it should be) but every
two or three seconds the follow
Paul Johnson <[EMAIL PROTECTED]> writes:
> When running gtk-gnutella, every few minutes I see this appear in the
> syslog again...what does this mean?
>
> Mar 16 11:02:22 ursine kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV)
> failed at tcp.c(2229)
> Mar 16 11:02:22 ursine kernel: KERNE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When running gtk-gnutella, every few minutes I see this appear in the
syslog again...what does this mean?
Mar 16 11:02:22 ursine kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed
at tcp.c(2229)
Mar 16 11:02:22 ursine kernel: KERNEL: ass
Matthew Thompson wrote:
> Hello,
>
> I'm getting TONS of this:
>
> Jun 12 06:30:03 doma kernel: Packet log: input REJECT eth0 PROTO=17
> 216.39.146.44:513 216.39.146.255:513 L=88 S=0x00 I=56637 F=0x T=64
> (#5)
> Jun 12 06:33:03 doma kernel: Packet log: input REJECT eth0 PROTO=17
> 216.39.146.
On Mon, Jun 12, 2000 at 11:57:32AM -0700, Matthew Thompson wrote:
> Hello,
>
> I'm getting TONS of this:
>
> Jun 12 06:36:03 doma kernel: Packet log: input REJECT eth0 PROTO=17
> 216.39.146.44:513 216.39.146.255:513 L=88 S=0x00 I=56673 F=0x T=64
> (#5)
> Jun 12 06:39:03 doma kernel: Packet lo
Hello,
I'm getting TONS of this:
Jun 12 06:30:03 doma kernel: Packet log: input REJECT eth0 PROTO=17
216.39.146.44:513 216.39.146.255:513 L=88 S=0x00 I=56637 F=0x T=64
(#5)
Jun 12 06:33:03 doma kernel: Packet log: input REJECT eth0 PROTO=17
216.39.146.44:513 216.39.146.255:513 L=88 S=0x00 I=5
13 matches
Mail list logo
