Darryl I tested yesterday with the space and there is no difference. I did however make some progress with the following
source src { unix-stream("/var/log/skot"); internal(); udp(ip(0.0.0.0)
port(514)); };
This script does parse and it does create a file names "skot" and it
does bind with UDP 514, however it writes nothing. I think I know need
to specify the "facility" =="Local0" to which the sending device
defines. With Wireshark I can just listen to UDP514 and see the
truncated data, however syslog-ng seems not to be written that easy.
It appears that in the case where we want syslog-ng to listen to a port,
we cannot use regular source syntax and form. It appears from the manual
that the moment the source is a "port" the source logic and syntax
changes dramatically.
Now I think I only need to specify the correct facility. I dont think
(rightfully) syslog-ng has a command that globally listens to 'anything'
on a port
Your thoughts if you have time.
Scott
Darryl Gregorash wrote:
> On 2007-05-21 16:06, Registration Account wrote:
>
>> I was clear to perform a copy and paste. Sorry the syntax error remains.
>> I can see your equal () and equal {} I have not a clue why the syntax
>> wont parse.
>>
>>
> I pasted the line into a console and see I didn't mix up the
> braces/parentheses after all, as you've noted.
>
> All I can think of now is a syntax error in the documentation. The line
> I quote from there is as follows:
>
>
>>>> destination d_file { file("/var/log/skot" ); };
>>>>
>>>>
>
> The format in the actual syslog-ng.conf file on my system is instead
> suggestive of the following:
>
> destination d_file { file("/var/log/skot"); };
>
> Note the absence of the space following the file name.
>
> Yes, I'm really grasping at a rather small straw here.
>
>
>
smime.p7s
Description: S/MIME Cryptographic Signature
