[gccsdk] Syslog: DoggySoft vs. Unix

Adam lists at snowstone.org.uk
Thu May 24 14:02:11 PDT 2007

In message <4ee82cc548gdshaw at sagitta.demon.co.uk>, Graham Shaw wrote:

> In article <84dfa9e74e.ajw498 at caramel.cp15.org>,
>    Alex Waugh <alex at alexwaugh.com> wrote:
> > Adam <lists at snowstone.org.uk> wrote:
> > > Hi All,
> > > 
> > > Having been reading Graham Shaw's new book on UnixLib, I've been
> > > fiddling with the GCC implimentation of syslog (in the past I've used
> > > the RISC OS syslog SWIs). How are the different priority schemes
> > > rationalised? For instance, the DoggySoft help file says:
> > > 
> > > Is there some way of rationalising the two which I've missed, or am I
> > > just going about things the wrong way?
> > The syslog code in UnixLib is derived from the BSD code, and so uses the
> > same priorities as BSD. This limits the number of priorities available.
> OTOH, I would not be totally surprised if the majority of SysLog-using
> programs are ports that work through UnixLib, in which case it could be
> argued that we would merely be formalising a change that to a large extent
> has already happened.

In fact, it's exactly the opposite here. The logs I've got are for:

 MultiError (mine)
 POPStop (mine)

Only Nettle uses the unix scheme (CryptRand hasn't logged anything here
so I don't know what that does).

1. or 3. get my vote :)


Adam Richardson          Carpe Diem

More information about the gcc mailing list