On 12/3/2012 9:39 PM, Vagrant Cascadian wrote:
On Mon, Dec 03, 2012 at 05:54:45PM -0500, John Hupp wrote:
was having trouble finding documentation of how to do that with rsyslog (only
syslog-ng). I imagine that various people here could whip up this
configuration in about a minute (I see now that I failed to ask here), but I
had to dig and study it off-and-on for a couple days.
Why not set SYSLOG_HOST=server in lts.conf?
On the server, uncomment the lines in /etc/rsyslog.conf:
$ModLoad imudp
$UDPServerRun 514
That uses UDP instead of TCP, but should work fine.
Thanks for the information about splitting the log files into separate files
per client.
live well,
vagrant
Setting SYSLOG_HOST is the general-case provision, but the lts.conf
documentation indicates that if SYSLOG_HOST=server is unset, it will
default to directing messages to the LTSP server, which was fine in my
little setup. So I did not set SYSLOG_HOST or SERVER.
By the way, this very setting figured into this paragraph that I wrote
earlier:
The configuration above [/i.e. my recipe/] will cause the client
syslog messages to be logged in both /var/log/ltspclientlog and
/var/log/syslog. I don't know why. The "& ~" command is supposed
to stop further processing of the message after it is written to
ltspclientlog. Perhaps I misunderstood the documentation and
forwarded messages are *always* written to syslog, and then perhaps
other files as well. Or perhaps LTSP has some functionality in it
that causes forwarded messages to be written to syslog.
Which is to say, AFAIK, setting up rsyslog on the server and client as I
indicated should be allthat is needed to set up syslog forwarding. Yet
here is the lts.conf setting for SYSLOG_HOSTwhich also purports to
direct messages, and I don't know what the mechanism is.
--------------------
And if one activates reception of messages by UDP on the server, then in
the client's /etc/rsyslog.conf the single line to add would be:
*.* @<server's IP address>
(This instead of prepending the server address with @@ as I did in my
example for transmission by TCP.)
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
