> > The first question that comes to mind: do you really need logs from a
> > year back?
>
> Nope. Should I need to tweak the default config files to ensure
> that I dont get them?
Since that's the element that brings three possible mis-features
together in the unfortunate
On Mon, Apr 18, 2005 at 10:54:20AM +0900, Joel wrote:
> The first question that comes to mind: do you really need logs from a
> year back?
Nope. Should I need to tweak the default config files to ensure
that I dont get them?
> Maybe it's because I'm such a newb, but I'm wondering which program
Joel wrote:
[ ... ]
Maybe it's because I'm such a newb, but I'm wondering which program has
what bug? Is it that the default configuration files for the login logs
doesn't put on age limit on the rotation? Is it that the log lines don't
conain a full 4-digit year in the timestamp?
This last one is
I'm just a newb, but
> > > I had an interesting experience, this morning. The nightly
> > > security message from a CVS server machine that runs a version
> > > of FreeBSD-4 had arrived, and it claimed that someone who hadn't
> > > done any work for us for some considerable time ha
On Sun, Apr 17, 2005 at 06:55:27AM -0700, Joshua Tinnin wrote:
> On Wed 13 Apr 05 19:59, Andrew Reilly
> > This could be avoided, perhaps, with a NetBSD-style backup/diff
> > mechanism, or (incompatibly) with daemontools/multilog-style
> > 64-bit time stamps in the log files. It can be worked-aro
On Wed 13 Apr 05 19:59, Andrew Reilly
<[EMAIL PROTECTED]> wrote:
> I had an interesting experience, this morning. The nightly
> security message from a CVS server machine that runs a version
> of FreeBSD-4 had arrived, and it claimed that someone who hadn't
> done any work for us for some conside
On Thu, 2005-Apr-14 13:04:36 +1000, Andrew Reilly wrote:
[Unexpected failed login reports in security messages]
>
>After much hunting around, and checking perimeter logs, it
>turned out that nothing of the sort had happened. The security
>log script had been fooled by the age of the messages.0.gz
I had an interesting experience, this morning. The nightly
security message from a CVS server machine that runs a version
of FreeBSD-4 had arrived, and it claimed that someone who hadn't
done any work for us for some considerable time had had three
failed login attempts, late that night. Curious.
