[cod] Spamming our logs again

[Geoff Goas]

an strace shows otherwise:

connect(34, {sa_family=AF_FILE, path="/dev/log"}, 110) = 0
send(34, "<134>Mar 11 16:37:23 bdLog[13737]:
../DemonWare/bdNet/bdUPnP/bdUPnP.cpp(334):\nWARNING: Cannot shutdown class
as it is already uninitialised!\n", 1
41, MSG_NOSIGNAL) = 141
close(34)

# lsof | grep '/dev/log'
syslogd    1727      root    0u     unix 0xffff81007a7e6580
3754 /dev/log

On Wed, Mar 11, 2009 at 4:21 PM, Ryan C. Gordon <icculus at icculus.org> wrote:

>
>  It writes to /var/log/messages directly? odd....
>>
>
> No, it writes to its own logfile; I don't think we use a syslog facility at
> all.
>
> It's possible that other programs, like Ubuntu's logger, might be catching
> stdout and redirecting to syslog.
>
> (I'd have to check, though, maybe I'll be surprised to find some leftover
> from quake 3 where it DOES write to syslog...)
>
>
> --ryan.
>
>
> ---
> To unsubscribe, send a blank email to cod-unsubscribe at icculus.org
> Mailing list archives: http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?38
>
>
>


-- 
Geoff Goas
Network Engineer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/cod/attachments/20090311/6f33e32f/attachment.htm>