[Mono-devel-list] problems with Syscall.syslog fot mono-126.96.36.199
MVorobiev at croc.ru
Thu Jul 28 05:37:53 EDT 2005
Today I've upgraded mono version to 188.8.131.52 and found, that it has no
fixes for syslog support. Not in sources, not in binaries. That version
will contain these changes?
The oiginal discussion of problem listed below.
From: mono-devel-list-bounces at lists.ximian.com
[mailto:mono-devel-list-bounces at lists.ximian.com] On Behalf Of Jonathan
Sent: Tuesday, June 28, 2005 3:32 PM
To: Vorobiev Maksim
Cc: Mono-devel-list at lists.ximian.com
Subject: Re: [Mono-devel-list] problems with Syscall.syslog
On Mon, 2005-06-27 at 18:35 +0400, Vorobiev Maksim wrote:
> I've started using Syscall.syslog method and encounted several
> problems. It may be errors in mono, or I just missed some details.
> Please note, that I use Suse 9.2 linux distribute.
It's nice to know someone is testing it. :-)
> 1. In Syscall.cs enumeration SyslogFacility declared with members:
> LOG_UUCP = 8 << 3,
> LOG_CRON = 8 << 3
> But under Suse the same constants declared in
> /usr/include/sys/syslog.h as LOG_UUCP = 8 << 3, LOG_CRON = 9 << 3
Oops, my bad. Fixed in svn-trunk (r46637,r46638).
> 2. There is no constant LOG_USRE in syslog.h under Suse, but it's
> LOG_USER. So, in support/map.c there is a bug (?) - no such definition
> found and error returned then code execution steps in this branch. The
> question is the same: is it mono problem, or Suse-platform specific
> header file?
This was fixed on June 15 in svn-trunk.
> 3. It seems very strange that SyslogFacility enumeration declared with
> [Flag] attribute. Members of this enumeration are not "powers of 2",
> so their combination via OR-mask is something incorrect. And these
> constants should be used independantly, not in combination. Is it true
> or I missed something?
No, it's my mistake. Fixed in svn-trunk.
Thank you for the help.
Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list