On Friday 11 January 2013, Kevin Chadwick wrote:
On Thu, 10 Jan 2013 23:46:29 +0700
Robin Atwood robin.atw...@attglobal.net wrote:
Thanks for the tips, now I can get more output to tty1 if I want. I
still can't get any systemd messages to syslog-ng, however. A bit of
a mystery.
This may be way off as I expect systemd to never shape up to a point
that I will use it, but with a bit of luck this may point you in the
right direction. On Arch systemd avoiders had to change their
syslog-ng.conf to the following to get their logging back.
source src {
unix-dgram(/dev/log);
internal();
file(/proc/kmsg);
};
I already have that! It's the systemd source that seems to have run dry.
Cheers
-Robin
--
--
Robin Atwood.
Ship me somewheres east of Suez, where the best is like the worst,
Where there ain't no Ten Commandments an' a man can raise a thirst
from Mandalay by Rudyard Kipling
--
