On 6/9/06, Gavin Maltby <[EMAIL PROTECTED]> wrote:
On 06/09/06 11:31, Darren Reed wrote:
> To bring the syslogd shipped with Solaris up to a level that is
> more in line with what is found in other systems today, I'd like
> to propose a project to upgrade it.
>
> Tasks currently scoped out for this project include:
> - introduce some of the more modern aspects of syslog.conf such as the
> use of '*' and '!'
> - filling out the list of facilities defined where there is common usage
> of undefined ones in the opensource community
> - implement the IETF TLS transport mapping for syslog
> - supporting explicit IPv6 destinations
> - adding support for specifying extra log devices
I'd like to see the syslog files be structured (binary) files. For
backwards compatability they'd have different pathnames and the
current pathnames would either be the existing random ascii
expansion of those records (duplicating storage) or some
cunning overlay filesystem which rewrites the contents of
the binary log in random ascii (along the lines of mntfs).
YUCK!!! no binary, there are enough special apps, to deal with binary
files, give me plain ascii files, when the system is down and you want
to fix things, tail messages etc... have saved my rear more than a
few times, I don't want to have to remember what program decodes yet
another binary file. Next thing you know they will want to write the
log decoder in java, and we will have another 100MB app doing someting
that a 16kB basic UNIX command to do.
James Dickens
uadmin.blogspot.com
Gavin
_______________________________________________
networking-discuss mailing list
networking-discuss@opensolaris.org
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
