i'm not "sticking up" for linux.. merely accurate experimentation.
think of mysql's crash_me test. how good of a test is it really? and therefore
how good are the results?
--
Aaron J. Seigo
Sys Admin
ut and finds that what you said wasn't exactly
accurate, how does reflect on your OS? answer: not very well.
"the means is the end, not the pathway to the end"
--
Aaron J. Seigo
Sys Admin
nd dealing with
> crash and error recovery issues could make it larger. If I end up writing
> it from scratch, I'll post the source for others to use.
for read only type database, i don't think this is a HUG job and can also
be accomplished with existing UNIX tools (if not specific to pgsql)... a
read/write environment however... well. that's more complicated and infinitely
more useable...
--
Aaron J. Seigo
Sys Admin
id, that's over half our space used already!
will we use those other <50 numbers?
it would be a shame to underallocate a numberspace now when we don't have to
face breaking anything (e.g. log parsers) than later on when we would. numbers
are cheap. at the begining anyhow.
--
Aaron J. Seigo
Sys Admin
ly with thresholds (1..10) and finely
(and optionally) with message filters...
> You could do worse than to borrow BIND's syntax for log control.
much worse. =)
--
Aaron J. Seigo
Sys Admin
ey would
each have a consistent record format...
of course, once we have the logs, the next step would be to write a script
that imports them into a pgsql database @;-)
--
Aaron J. Seigo
Sys Admin
d.. or put right onto removable media... or
stored in someone's home dir if they give the right username/password combo,
etc...
--
Aaron J. Seigo
Sys Admin
