02 May 14, 11:01PM
(This post was last modified: 02 May 14, 11:19PM by RandumKiwi.)
(02 May 14, 09:57AM)jamz Wrote:(01 May 14, 03:54PM)Mousikos Wrote: I thought Stef said (on irc) that whitespace doesn't matter anymore?It doesn't in servercmdline.txt, but it does if you put the switch in the command line.
(01 May 14, 11:11AM)RandumKiwi Wrote: Of course, this all depends on how you're issuing these command line options...
... and, as such, it's good to see that AC is definitely logging correctly, based on your output above.
(01 May 14, 03:54PM)Mousikos Wrote: No effect. Here's the weird thing, I'm pretty sure castle.log is being created. But 1) I have to sudo vim to view it, 2) The contents contain 0 lines, 0 bytes (unlike where syslog is actually being logged to)
Note how your cfg has these:
$FileOwner syslog
$FileGroup adm
Are syslog/adm able to write to the directory the logfile is stored in?
P.S: On debian, those settings are root/adm by default.
P.P.S: You've restarted rsyslog service each time, before you tested, right?
P.P.P.S: For testing, please remove &~
P.P.P.P.S: If all else fails, do it like normal syslog, as mentioned by jamz. I've found rsyslog's syntax to be a PITA sometimes (make sure rsyslog is up to date!!!)