[prev in list] [next in list] [prev in thread] [next in thread] 

List:       syslog-ng
Subject:    Re: [syslog-ng] Reg; Syslog-ng does not recognize the audit facility
From:       Scheidler, Balázs <balazs.scheidler () balabit ! com>
Date:       2015-07-29 21:14:14
Message-ID: CANWQT2No+aD9adtND8=OH2s6hr4k0CnxcWZW9yc3fYgoJQgh5Q () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


It doesn't matter, the on wire format is the same. Syslog-ng on the server
prints the facility in debug mode.
On Jul 29, 2015 9:07 PM, "Justin Kala" <justinkala@gmail.com> wrote:

> Bazsi
>
> We do not have syslog-ng agents on the sending server side .Using the
> capabilities of syslog.conf only where I put the line " audit.notice
> @Syslog-NG-server "
>
> On Wed, Jul 29, 2015 at 4:25 AM, Scheidler, Balázs <
> balazs.scheidler@balabit.com> wrote:
>
>> Syslog-ng does have a private facility registry to make the codes more
>> portable accross OS-es.  It is in syslog-names.c in the lib/ directory. Can
>> you check if audit is listed there?
>>
>> If it's not feel free to submit  a patch to add that.
>>
>> Also, on a related note, if syslog-ng doesnt match by facility code, pls
>> confirm that the message was indeed submitted with the facility code you
>> are expecting. You can do that by looking at raw syslog traffic (using a
>> sniffer or merely looking at syslog-ng debug output). There you will see a
>> number in brackets as the first thing in a message.
>>
>> E.g.
>>
>> <55>date host msg
>>
>> There 55 equals to 8 times facility plus the severity level, in this
>> example 6*8+7, eg. Facility 6, severity 7.
>> Hope this helps.
>> Bazsi
>> On Jul 28, 2015 8:36 PM, "Evan Rempel" <erempel@uvic.ca> wrote:
>>
>>>  Then this needs to go back to whomever compiled the release of
>>> syslog-ng that you are using.
>>> Perhaps it was compiled on a different release of Solaris or something.
>>> Only the group that compiled the release can give you more answers.
>>>
>>> Evan.
>>>
>>> On 07/28/2015 11:08 AM, Justin Kala wrote:
>>>
>>>  I see AUDIT facility defined in /usr/include/sys/syslog.h on syslog-ng
>>> server side and the sending server as well.
>>>
>>>  #define LOG_KERN        (0<<3)  /* kernel messages */
>>> #define LOG_USER        (1<<3)  /* random user-level messages */
>>> #define LOG_MAIL        (2<<3)  /* mail system */
>>> #define LOG_DAEMON      (3<<3)  /* system daemons */
>>> #define LOG_AUTH        (4<<3)  /* security/authorization messages */
>>> #define LOG_SYSLOG      (5<<3)  /* messages generated internally by
>>> syslogd */
>>> #define LOG_LPR         (6<<3)  /* line printer subsystem */
>>> #define LOG_NEWS        (7<<3)  /* netnews subsystem */
>>> #define LOG_UUCP        (8<<3)  /* uucp subsystem */
>>> *#define LOG_AUDIT       (13<<3) /* audit subsystem */*
>>> #define LOG_CRON        (15<<3) /* cron/at subsystem */
>>>
>>> On Tue, Jul 28, 2015 at 12:41 PM, Evan Rempel <erempel@uvic.ca> wrote:
>>>
>>>>  Can you look at the syslog facility definitions
>>>>
>>>> /usr/include/sys/syslog.h
>>>>
>>>> or
>>>>
>>>> /usr/include/syslog.h
>>>>
>>>> to see if audit is a defined facility?
>>>>
>>>>
>>>>
>>>> On 07/28/2015 09:32 AM, Justin Kala wrote:
>>>>
>>>> Hi Evan..thanks for the reply but both sending and receiving servers
>>>> are same OS.. Solaris 10
>>>> On Jul 28, 2015 12:18 PM, "Evan Rempel" <erempel@uvic.ca> wrote:
>>>>
>>>>>  Well, that is probably because the host where syslog-ng was compiled
>>>>> is a different OS than that where the "audit" facility log line was created.
>>>>>
>>>>> For instance, on a Linux host, the syslog.h file from the system only
>>>>> has these facilities defined.
>>>>>
>>>>> CODE facilitynames[] =
>>>>>   {
>>>>>     { "auth", LOG_AUTH },
>>>>>     { "authpriv", LOG_AUTHPRIV },
>>>>>     { "cron", LOG_CRON },
>>>>>     { "daemon", LOG_DAEMON },
>>>>>     { "ftp", LOG_FTP },
>>>>>     { "kern", LOG_KERN },
>>>>>     { "lpr", LOG_LPR },
>>>>>     { "mail", LOG_MAIL },
>>>>>     { "mark", INTERNAL_MARK },          /* INTERNAL */
>>>>>     { "news", LOG_NEWS },
>>>>>     { "security", LOG_AUTH },           /* DEPRECATED */
>>>>>     { "syslog", LOG_SYSLOG },
>>>>>     { "user", LOG_USER },
>>>>>     { "uucp", LOG_UUCP },
>>>>>     { "local0", LOG_LOCAL0 },
>>>>>     { "local1", LOG_LOCAL1 },
>>>>>     { "local2", LOG_LOCAL2 },
>>>>>     { "local3", LOG_LOCAL3 },
>>>>>     { "local4", LOG_LOCAL4 },
>>>>>     { "local5", LOG_LOCAL5 },
>>>>>     { "local6", LOG_LOCAL6 },
>>>>>     { "local7", LOG_LOCAL7 },
>>>>>
>>>>>
>>>>> with values of
>>>>>
>>>>> /* facility codes */
>>>>> #define LOG_KERN        (0<<3)  /* kernel messages */
>>>>> #define LOG_USER        (1<<3)  /* random user-level messages */
>>>>> #define LOG_MAIL        (2<<3)  /* mail system */
>>>>> #define LOG_DAEMON      (3<<3)  /* system daemons */
>>>>> #define LOG_AUTH        (4<<3)  /* security/authorization messages */
>>>>> #define LOG_SYSLOG      (5<<3)  /* messages generated internally by
>>>>> syslogd */
>>>>> #define LOG_LPR         (6<<3)  /* line printer subsystem */
>>>>> #define LOG_NEWS        (7<<3)  /* network news subsystem */
>>>>> #define LOG_UUCP        (8<<3)  /* UUCP subsystem */
>>>>> #define LOG_CRON        (9<<3)  /* clock daemon */
>>>>> #define LOG_AUTHPRIV    (10<<3) /* security/authorization messages
>>>>> (private) */
>>>>> #define LOG_FTP         (11<<3) /* ftp daemon */
>>>>>
>>>>>         /* other codes through 15 reserved for system use */
>>>>> #define LOG_LOCAL0      (16<<3) /* reserved for local use */
>>>>> #define LOG_LOCAL1      (17<<3) /* reserved for local use */
>>>>> #define LOG_LOCAL2      (18<<3) /* reserved for local use */
>>>>> #define LOG_LOCAL3      (19<<3) /* reserved for local use */
>>>>> #define LOG_LOCAL4      (20<<3) /* reserved for local use */
>>>>> #define LOG_LOCAL5      (21<<3) /* reserved for local use */
>>>>> #define LOG_LOCAL6      (22<<3) /* reserved for local use */
>>>>> #define LOG_LOCAL7      (23<<3) /* reserved for local use */
>>>>>
>>>>>
>>>>> so there is no audit facility.
>>>>>
>>>>> Hope that explains it.
>>>>>
>>>>>
>>>>> On 07/28/2015 09:08 AM, Justin Kala wrote:
>>>>>
>>>>>
>>>>> Hi
>>>>>
>>>>>  Syslog-ng is unable to recognize the facility audit. When I put
>>>>> filter as audit and restart syslog-ng it errors out. When I put the
>>>>> facility code as 13 ,it does not error on restarting the service but does
>>>>> not capture the syslog message received through this filter code  13 as
>>>>> well.
>>>>>
>>>>>  Please advise.
>>>>> --
>>>>>  Kaladhar
>>>>>
>>>>>
>>>>> ______________________________________________________________________________
>>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>>>>> Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
>>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Evan Rempel                                      erempel@uvic.ca
>>>>> Senior Systems Administrator                        250.721.7691
>>>>> Data Centre Services, University Systems, University of Victoria
>>>>>
>>>>>
>>>>>
>>>>> ______________________________________________________________________________
>>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>>>>> Documentation:
>>>>> http://www.balabit.com/support/documentation/?product=syslog-ng
>>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>>>>
>>>>>
>>>>>
>>>>
>>>> ______________________________________________________________________________
>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>>>> Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>>>
>>>>
>>>>
>>>> --
>>>> Evan Rempel                                      erempel@uvic.ca
>>>> Senior Systems Administrator                        250.721.7691
>>>> Data Centre Services, University Systems, University of Victoria
>>>>
>>>>
>>>>
>>>> ______________________________________________________________________________
>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>>>> Documentation:
>>>> http://www.balabit.com/support/documentation/?product=syslog-ng
>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Kaladhar
>>>
>>>
>>> ______________________________________________________________________________
>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>>> Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>>
>>>
>>>
>>> --
>>> Evan Rempel                                      erempel@uvic.ca
>>> Senior Systems Administrator                        250.721.7691
>>> Data Centre Services, University Systems, University of Victoria
>>>
>>>
>>>
>>> ______________________________________________________________________________
>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>>> Documentation:
>>> http://www.balabit.com/support/documentation/?product=syslog-ng
>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>>
>>>
>>>
>>
>> ______________________________________________________________________________
>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>> Documentation:
>> http://www.balabit.com/support/documentation/?product=syslog-ng
>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>
>>
>>
>
>
> --
> Kaladhar
>
>
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation:
> http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>
>
>

[Attachment #5 (text/html)]

<p dir="ltr">It doesn&#39;t matter, the on wire format is the same. Syslog-ng on the \
server prints the facility in debug mode.</p> <div class="gmail_quote">On Jul 29, \
2015 9:07 PM, &quot;Justin Kala&quot; &lt;<a \
href="mailto:justinkala@gmail.com">justinkala@gmail.com</a>&gt; wrote:<br \
type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div \
dir="ltr"><div>Bazsi</div><div>  </div><div>We do not have syslog-ng agents on the \
sending server side .Using the capabilities of syslog.conf only where I put  the line \
&quot;  audit.notice @Syslog-NG-server &quot;</div></div><div \
class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 29, 2015 at 4:25 AM, \
Scheidler, Balázs <span dir="ltr">&lt;<a href="mailto:balazs.scheidler@balabit.com" \
target="_blank">balazs.scheidler@balabit.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><p dir="ltr">Syslog-ng does have a private facility registry \
to make the codes more portable accross OS-es.   It is in syslog-names.c in the lib/ \
directory. Can you check if audit is listed there?</p> <p dir="ltr">If it&#39;s not \
feel free to submit   a patch to add that.</p> <p dir="ltr">Also, on a related note, \
if syslog-ng doesnt match by facility code, pls confirm that the message was indeed \
submitted with the facility code you are expecting. You can do that by looking at raw \
syslog traffic (using a sniffer or merely looking at syslog-ng debug output). There \
you will see a number in brackets as the first thing in a message.</p> <p \
dir="ltr">E.g. </p> <p dir="ltr">&lt;55&gt;date host msg</p>
<p dir="ltr">There 55 equals to 8 times facility plus the severity level, in this \
example 6*8+7, eg. Facility 6, severity 7.<br> Hope this helps.<br>
Bazsi</p><div><div>
<div class="gmail_quote">On Jul 28, 2015 8:36 PM, &quot;Evan Rempel&quot; &lt;<a \
href="mailto:erempel@uvic.ca" target="_blank">erempel@uvic.ca</a>&gt; wrote:<br \
type="attribution"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <div>Then this needs to go back to whomever
      compiled the release of syslog-ng that you are using.<br>
      Perhaps it was compiled on a different release of Solaris or
      something. Only the group that compiled the release can give you
      more answers.<br>
      <br>
      Evan.<br>
      <br>
      On 07/28/2015 11:08 AM, Justin Kala wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="ltr">
        <div>I see AUDIT facility defined in /usr/include/sys/syslog.h
          on syslog-ng server side and the sending server as well.</div>
        <div><br>
        </div>
        <div>#define LOG_KERN               (0&lt;&lt;3)   /* kernel messages */<br>
          #define LOG_USER               (1&lt;&lt;3)   /* random user-level
          messages */<br>
          #define LOG_MAIL               (2&lt;&lt;3)   /* mail system */<br>
          #define LOG_DAEMON           (3&lt;&lt;3)   /* system daemons */<br>
          #define LOG_AUTH               (4&lt;&lt;3)   /*
          security/authorization messages */<br>
          #define LOG_SYSLOG           (5&lt;&lt;3)   /* messages generated
          internally by syslogd */<br>
          #define LOG_LPR                 (6&lt;&lt;3)   /* line printer
          subsystem */<br>
          #define LOG_NEWS               (7&lt;&lt;3)   /* netnews subsystem */<br>
          #define LOG_UUCP               (8&lt;&lt;3)   /* uucp subsystem */<br>
          <strong>#define LOG_AUDIT             (13&lt;&lt;3) /* audit
            subsystem */</strong><br>
          #define LOG_CRON               (15&lt;&lt;3) /* cron/at subsystem */<br>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Tue, Jul 28, 2015 at 12:41 PM, Evan
          Rempel <span dir="ltr">&lt;<a href="mailto:erempel@uvic.ca" \
target="_blank">erempel@uvic.ca</a>&gt;</span>  wrote:<br>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
  <div text="#000000" bgcolor="#FFFFFF">
              <div>Can you look at the syslog facility definitions<br>
                <br>
                /usr/include/sys/syslog.h<br>
                <br>
                or<br>
                <br>
                /usr/include/syslog.h<br>
                <br>
                to see if audit is a defined facility?
                <div>
                  <div><br>
                    <br>
                    <br>
                    On 07/28/2015 09:32 AM, Justin Kala wrote:<br>
                  </div>
                </div>
              </div>
              <div>
                <div>
                  <blockquote type="cite">
                    <p dir="ltr">Hi Evan..thanks for the reply but both
                      sending and receiving servers are same OS..
                      Solaris 10</p>
                    <div class="gmail_quote">On Jul 28, 2015 12:18 PM,
                      &quot;Evan Rempel&quot; &lt;<a href="mailto:erempel@uvic.ca" \
target="_blank">erempel@uvic.ca</a>&gt;

                      wrote:<br type="attribution">
                      <blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
  <div text="#000000" bgcolor="#FFFFFF">
                          <div>Well, that is probably because the host
                            where syslog-ng was compiled is a different
                            OS than that where the &quot;audit&quot; facility log
                            line was created.<br>
                            <br>
                            For instance, on a Linux host, the syslog.h
                            file from the system only has these
                            facilities defined.<br>
                            <br>
                            CODE facilitynames[] =<br>
                               {<br>
                                   { &quot;auth&quot;, LOG_AUTH },<br>
                                   { &quot;authpriv&quot;, LOG_AUTHPRIV },<br>
                                   { &quot;cron&quot;, LOG_CRON },<br>
                                   { &quot;daemon&quot;, LOG_DAEMON },<br>
                                   { &quot;ftp&quot;, LOG_FTP },<br>
                                   { &quot;kern&quot;, LOG_KERN },<br>
                                   { &quot;lpr&quot;, LOG_LPR },<br>
                                   { &quot;mail&quot;, LOG_MAIL },<br>
                                   { &quot;mark&quot;, INTERNAL_MARK },               \
/*  INTERNAL */<br>
                                   { &quot;news&quot;, LOG_NEWS },<br>
                                   { &quot;security&quot;, LOG_AUTH },                \
/*  DEPRECATED */<br>
                                   { &quot;syslog&quot;, LOG_SYSLOG },<br>
                                   { &quot;user&quot;, LOG_USER },<br>
                                   { &quot;uucp&quot;, LOG_UUCP },<br>
                                   { &quot;local0&quot;, LOG_LOCAL0 },<br>
                                   { &quot;local1&quot;, LOG_LOCAL1 },<br>
                                   { &quot;local2&quot;, LOG_LOCAL2 },<br>
                                   { &quot;local3&quot;, LOG_LOCAL3 },<br>
                                   { &quot;local4&quot;, LOG_LOCAL4 },<br>
                                   { &quot;local5&quot;, LOG_LOCAL5 },<br>
                                   { &quot;local6&quot;, LOG_LOCAL6 },<br>
                                   { &quot;local7&quot;, LOG_LOCAL7 },<br>
                            <br>
                            <br>
                            with values of<br>
                            <br>
                            /* facility codes */<br>
                            #define LOG_KERN               (0&lt;&lt;3)   /*
                            kernel messages */<br>
                            #define LOG_USER               (1&lt;&lt;3)   /*
                            random user-level messages */<br>
                            #define LOG_MAIL               (2&lt;&lt;3)   /*
                            mail system */<br>
                            #define LOG_DAEMON           (3&lt;&lt;3)   /*
                            system daemons */<br>
                            #define LOG_AUTH               (4&lt;&lt;3)   /*
                            security/authorization messages */<br>
                            #define LOG_SYSLOG           (5&lt;&lt;3)   /*
                            messages generated internally by syslogd */<br>
                            #define LOG_LPR                 (6&lt;&lt;3)   /*
                            line printer subsystem */<br>
                            #define LOG_NEWS               (7&lt;&lt;3)   /*
                            network news subsystem */<br>
                            #define LOG_UUCP               (8&lt;&lt;3)   /*
                            UUCP subsystem */<br>
                            #define LOG_CRON               (9&lt;&lt;3)   /*
                            clock daemon */<br>
                            #define LOG_AUTHPRIV       (10&lt;&lt;3) /*
                            security/authorization messages (private) */<br>
                            #define LOG_FTP                 (11&lt;&lt;3) /* ftp
                            daemon */<br>
                            <br>
                                           /* other codes through 15 reserved
                            for system use */<br>
                            #define LOG_LOCAL0           (16&lt;&lt;3) /*
                            reserved for local use */<br>
                            #define LOG_LOCAL1           (17&lt;&lt;3) /*
                            reserved for local use */<br>
                            #define LOG_LOCAL2           (18&lt;&lt;3) /*
                            reserved for local use */<br>
                            #define LOG_LOCAL3           (19&lt;&lt;3) /*
                            reserved for local use */<br>
                            #define LOG_LOCAL4           (20&lt;&lt;3) /*
                            reserved for local use */<br>
                            #define LOG_LOCAL5           (21&lt;&lt;3) /*
                            reserved for local use */<br>
                            #define LOG_LOCAL6           (22&lt;&lt;3) /*
                            reserved for local use */<br>
                            #define LOG_LOCAL7           (23&lt;&lt;3) /*
                            reserved for local use */<br>
                            <br>
                            <br>
                            so there is no audit facility.<br>
                            <br>
                            Hope that explains it.<br>
                            <br>
                            <br>
                            On 07/28/2015 09:08 AM, Justin Kala wrote:<br>
                          </div>
                          <blockquote type="cite">
                            <div dir="ltr">
                              <div><br clear="all">
                                Hi</div>
                              <div><br>
                              </div>
                              <div>Syslog-ng is unable to recognize the
                                facility audit. When I put filter as
                                audit and restart syslog-ng it errors
                                out. When I put the facility code as 13
                                ,it does not error on restarting the
                                service but does not capture the syslog
                                message received through this filter
                                code   13 as well.</div>
                              <div><br>
                              </div>
                              <div>Please advise.<br>
                                -- <br>
                              </div>
                              <div>Kaladhar</div>
                            </div>
                            <br>
                            <fieldset></fieldset>
                            <br>
                            \
<pre>______________________________________________________________________________ \
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" \
                target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a>
                
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" \
                target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a>
                
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" \
target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a>

</pre>
                          </blockquote>
                          <br>
                          <br>
                          <pre cols="500">-- 
Evan Rempel                                      <a href="mailto:erempel@uvic.ca" \
target="_blank">erempel@uvic.ca</a> Senior Systems Administrator                      \
<a href="tel:250.721.7691" value="+12507217691" target="_blank">250.721.7691</a> Data \
Centre Services, University Systems, University of Victoria  </pre>
                        </div>
                        <br>
______________________________________________________________________________<br>
                        Member info: <a \
href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" rel="noreferrer" \
target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>  \
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" \
rel="noreferrer" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
                
                        FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" \
rel="noreferrer" target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br>  \
<br>  <br>
                      </blockquote>
                    </div>
                    <br>
                    <fieldset></fieldset>
                    <br>
                    <pre>______________________________________________________________________________
 Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" \
                target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a>
                
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" \
                target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a>
                
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" \
target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a>

</pre>
                  </blockquote>
                  <br>
                  <br>
                  <pre cols="500">-- 
Evan Rempel                                      <a href="mailto:erempel@uvic.ca" \
target="_blank">erempel@uvic.ca</a> Senior Systems Administrator                      \
<a href="tel:250.721.7691" value="+12507217691" target="_blank">250.721.7691</a> Data \
Centre Services, University Systems, University of Victoria  </pre>
                </div>
              </div>
            </div>
            <br>
______________________________________________________________________________<br>
            Member info: <a \
href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" rel="noreferrer" \
target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>  \
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" \
rel="noreferrer" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
                
            FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" rel="noreferrer" \
target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br>  <br>
            <br>
          </blockquote>
        </div>
        <br>
        <br clear="all">
        <br>
        -- <br>
        <div>Kaladhar</div>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>______________________________________________________________________________
 Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" \
                target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a>
                
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" \
                target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a>
                
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" \
target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a>

</pre>
    </blockquote>
    <br>
    <br>
    <pre cols="500">-- 
Evan Rempel                                      <a href="mailto:erempel@uvic.ca" \
target="_blank">erempel@uvic.ca</a> Senior Systems Administrator                      \
<a href="tel:250.721.7691" value="+12507217691" target="_blank">250.721.7691</a> Data \
Centre Services, University Systems, University of Victoria  </pre>
  </div>

<br>______________________________________________________________________________<br>
 Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" \
rel="noreferrer" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
                
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" \
rel="noreferrer" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
                
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" rel="noreferrer" \
target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br> <br>
<br></blockquote></div>
</div></div><br>______________________________________________________________________________<br>
 Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" \
rel="noreferrer" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
                
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" \
rel="noreferrer" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
                
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" rel="noreferrer" \
target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br> <br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div>Kaladhar</div>
</div>
<br>______________________________________________________________________________<br>
 Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" \
rel="noreferrer" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
                
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" \
rel="noreferrer" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
                
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" rel="noreferrer" \
target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br> <br>
<br></blockquote></div>



______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic