Date: Thu, 30 Apr 2015 19:50:05 +0000 From: John Howie <john@thehowies.com> To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: minor syslog issue Message-ID: <D001AAE5-2823-4139-913E-979C7FB802BC@thehowies.com> In-Reply-To: <55424715.3080607@infracaninophile.co.uk> References: <55422366.8060000@hiwaay.net> <554229CE.30009@infracaninophile.co.uk> <55422E43.8090206@hiwaay.net> <5542348D.8000109@infracaninophile.co.uk> <5542398B.4000405@hiwaay.net>,<55424715.3080607@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
A little OT but do you really want the RPI to be your time server? It has n= o hardware clock. The time keeping will be (relatively) terrible. Sent from my iPhone > On Apr 30, 2015, at 11:16, Matthew Seaman <m.seaman@infracaninophile.co.u= k> wrote: >=20 >> On 2015/04/30 15:17, William A. Mahaffey III wrote: >> I missed that (high port #, thought it might be a process #, *new* to >> tcpdump et al :-/ ) .... Could that be a mal/mis-configuration in the >> (rather beta) NetBSD ARM port ? I will try the updated syslogd flag & >> see how that goes. Thanks :-). >=20 > Dunno. FreeBSD syslogd sends /from/ port 514 as well as to port 514 -- > which is the traditional behaviour from way back when... of a lot of UDP > based services. NTP still does this, DNS used to do that until > Kaminsky, and now it most definitely *doesn't* do that. More recent > code tends to just use arbitrary ports on the sending side -- I believe > rsyslog (which is the Linux standard) works like that. No idea how > NetBSD behaves. >=20 > Cheers, >=20 > Matthew >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D001AAE5-2823-4139-913E-979C7FB802BC>