> But, but, but... why should the facilities be integers in the first place?
> They're just tags. Names. Strings. Why do I need a mapping between strings
> and integers to maintain? Why can't I have something like:
>
> submit_log_entry("mail/MTA", LOG_ALERT, "the log message")
>
> in my program and
>
> mail/MTA.* "/var/adm/syslog/${facility_name}.log"
>
> in my configuration and then have the logger automagically create a named pipe
> at /dev/logdev/mail/MTA and log the data to /var/adm/syslog/mail/MTA.log?
>
> The only reason is that the creators of syslog didn't think of that. That's
> not a good enough reason.
I wasn't worried about syntax of how to add facilities, etc. I just
wanted to make sure that some sort of dyamic mechanism was available
to push logs around.
The current protocol supported a fixed 24 -- actually its no more than a
text stream??. The new protocol should have enough 'bandwidth' to support
a flexible structure.
transmission protocol? is it in the clear text or binary?
1 byte (facility)
1 byte (priority)
Your /etc/syslog.conf better be simmilar on all your machines if a binary
protocol is chosen for tag to integer matchup. Are we sending text over
tcp/udp to specify facility and service?
If you use a unique facility/priority naming convention, those poor
hackers better have a copy of /etc/syslog.conf to figure out which is
which...
Rob
