On Wednesday 29 August 2007 23:19, Joey Hess wrote:
> Nigel Henry wrote:
> > It obviously didn't work, and appears that
> > if a script is in /etc/init.d, and there are no links to it in the
> > runlevel directories, the script is run anyway.
>
> I think that avahi may be started by /etc/network/if
On Wednesday 29 August 2007 22:52, Sven Joachim wrote:
> Nigel Henry <[EMAIL PROTECTED]> writes:
> > Before closing this post, and I've still got tail -f /var/log/messages
> > running. I keep getting every 20 mins "debian -- MARK --" . What's that
> > all about?
>
> It's only the syslogd who tells
Nigel Henry wrote:
> It obviously didn't work, and appears that
> if a script is in /etc/init.d, and there are no links to it in the runlevel
> directories, the script is run anyway.
I think that avahi may be started by /etc/network/if-up.d/avahi-daemon,
when a network interface is brought up. I
Nigel Henry <[EMAIL PROTECTED]> writes:
> Before closing this post, and I've still got tail -f /var/log/messages
> running. I keep getting every 20 mins "debian -- MARK --" . What's that all
> about?
It's only the syslogd who tells you that it is alive and kickin', see
syslogd(8).
Sven
--
On Wednesday 29 August 2007 03:27, Douglas A. Tutty wrote:
> On Tue, Aug 28, 2007 at 11:50:14PM +0200, Nigel Henry wrote:
> > Any comments, suggestions, and including "go and get a life", welcome.
> >
> > This is no big deal, but would be nice to resolve this problem.
>
> So its a script in /etc/ne
On Tue, Aug 28, 2007 at 11:50:14PM +0200, Nigel Henry wrote:
> Any comments, suggestions, and including "go and get a life", welcome.
>
> This is no big deal, but would be nice to resolve this problem.
So its a script in /etc/network/ip-up.d? That would be run by the
networking stuff and you d
On 8/28/07, Nelson Castillo <[EMAIL PROTECTED]> wrote:
(cut)
> > Any comments, suggestions, and including "go and get a life", welcome.
>
> Well, it seems like a multicast address. I've used that range to do
> multicast in a LAN (with videolan).
Rendezvous, mDNS, zeroconf?
That is what I read som
On 8/28/07, Nigel Henry <[EMAIL PROTECTED]> wrote:
(cut)
> TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=52
> DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=72 TOS=0x00 PREC=0x00
> TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=52
> d
>
> Any comments, suggestions, and including "go an
On Tuesday 28 August 2007 03:53, Douglas A. Tutty wrote:
> On Mon, Aug 27, 2007 at 04:28:48PM +0200, Nigel Henry wrote:
> > On Monday 27 August 2007 03:52, Douglas A. Tutty wrote:
> > > Since this is all happening in /etc/rcS.d, I'd suggest booting with
> > > init=/bin/sh and running the /etc/rcS.d
On Mon, Aug 27, 2007 at 04:28:48PM +0200, Nigel Henry wrote:
> On Monday 27 August 2007 03:52, Douglas A. Tutty wrote:
> > Since this is all happening in /etc/rcS.d, I'd suggest booting with
> > init=/bin/sh and running the /etc/rcS.d scripts manually one at a time
> > to try to track it down. If
On Monday 27 August 2007 10:53, Avi Rozen wrote:
> Looks like zeroconf traffic (avahi/mdns), maybe try:
>
> /etc/init.d/avahi-daemon stop
>
> and see what happens.
>
>
> HTH,
>
> Avi.
Thanks for that Avi. As soon as your first line mentioned zeroconf, bells
started to ring in my head. Zeroconf ha
On Monday 27 August 2007 03:52, Douglas A. Tutty wrote:
> On Sun, Aug 26, 2007 at 10:42:51PM +0200, Nigel Henry wrote:
> > I've had this problem for a while. When booting Debian Lenny, and perhaps
> > Etch as well. When booting up I've had the following output trying to
> > access 224.0.0.251.
> >
Looks like zeroconf traffic (avahi/mdns), maybe try:
/etc/init.d/avahi-daemon stop
and see what happens.
HTH,
Avi.
Nigel Henry wrote:
> I've had this problem for a while. When booting Debian Lenny, and perhaps
> Etch
> as well. When booting up I've had the following output trying to acces
On Sun, Aug 26, 2007 at 10:42:51PM +0200, Nigel Henry wrote:
> I've had this problem for a while. When booting Debian Lenny, and perhaps
> Etch
> as well. When booting up I've had the following output trying to access
> 224.0.0.251.
>
> eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> NET: Reg
I've had this problem for a while. When booting Debian Lenny, and perhaps Etch
as well. When booting up I've had the following output trying to access
224.0.0.251.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
lp0: using parpor
15 matches
Mail list logo
