After pondering over the problem of how to get remote logging working with the server running syslog-ng I came up with this solution.

Add these lines to /etc/syslog-ng/syslog-ng.conf:

# Romote logging turned on for ltsp clients

source src { unix-stream("/dev/log"); internal(); udp();
tcp(ip("192.168.1.60") port(514) keep-alive(yes)); };

Now it doesn't complain about not being able to connect to <server ip address>:514 though I haven't looked into what sort of logs it produces. I'm not sure if this is the "correct" way of doing it, maybe some syslog-ng expert can proof it.

Now for a question to another problem--

I've split the ltsp server onto two computers. One provides the kernel loading, logging and basic services then points the clients to get their xdm login from another, more powerful, computer. This has been working fine so far, except that I like to keep the servers in console mode but the diskless clients can't get a login unless the xdm server is in graphics mode. The option option on the ltspadmin tool to do what I want doesn't seem to work on this split configuration.

What do I need to do to get graphical logins on the clients without having to put the server in graphics mode?

Cheers.

--Dan


------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _____________________________________________________________________ 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

Reply via email to