<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="-1"><font face="Arial">If <font size="-1">you mean
write down what I have done with LTSP <font size="-1">on
Lubuntu (and not j<font size="-1">ust this rsyslog recipe),
I think I d<font size="-1">id <font size="-1">post</font>
up a <font size="-1">recipe for a standard 2-NIC LTSP5
setup on Lubuntu Precise some months ago.<br>
<br>
<font size="-1"><font size="-1">Now I'm still deep in
troubleshooting (or something) of </font></font>a
1-NIC <font size="-1">LTSP-PNP setup on Lubuntu <font
size="-1">Quantal. If I ever get th<font
size="-1">rough that, I expect that I would do <font
size="-1">another recipe.<br>
<br>
<font size="-1">Someone else on <font
size="-1">this list is running LTSP on
Lubuntu, but I don't remember who<font
size="-1">, and I don't think he posted
a<font size="-1">nything particular
about the parameters (1-NIC<font
size="-1"> or 2-NIC, etc.) </font>of
his setup<font size="-1">, so I don't
know if his project <font size="-1">uses
current ingre<font size="-1">dients.
But I sure would be happy to run
into some other Lub<font
size="-1">untu users
successfully running LTSP<font
size="-1">!<br>
<br>
</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font>
<div class="moz-cite-prefix">On 12/3/2012 7:31 PM, Phill Whiteside
wrote:<br>
</div>
<blockquote
cite="mid:CAD5cqVh4h_3J+TXH8d+U+F0QDODx-+qjJaS6H7GMBWsUkPugZw@mail.gmail.com"
type="cite">Hi John,
<div><br>
</div>
<div>I'm a couple of years out from when our last guy asked about
LTSP.. Back in 10.04 a teacher in a non 1st world country
'found' lubuntu. Ubuntu via GNOME was becoming 'too heavy' for
his out dated computer lab. He was so thankful for the ability
to actually have the quite ancient blade server be able to
continue to serve his students. </div>
<div><br>
</div>
<div>There are times in life when you think "did I make a
difference"? Well, all I will say is via the reverse speak of
'star wars'... <b>small in number, change they made</b>. We
answered his questions and got him up and running.</div>
<div><br>
</div>
<div>Lubuntu makes a difference, it is a really stripped back
system, go add to it what you need... But, may I make a request?
Please write down what you have done so that others who do not
have your technical knowledge, but have the heart to help have
it as a resource to help their class.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Phill.<br>
<br>
<div class="gmail_quote">On 3 December 2012 22:36, John Hupp <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:lubuntu@prpcompany.com" target="_blank">lubuntu@prpcompany.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>
<div class="h5"> <font size="-1"><font face="Arial"><font
size="-1"><font size="-1"><br>
</font></font></font></font>
<div>On 11/30/2012 4:47 PM, John Hupp wrote:<br>
</div>
<blockquote type="cite"> <font face="Arial" size="-1">On
Lubuntu Quantal, it looks like rsyslogd is
installed with a certain configuration -- probably
just for local logging -- but is not set to
auto-start.<br>
<br>
I'm trying to set up remote logs for an LTSP
client (to log to the LTSP server) for the sake of
troubleshooting a client boot problem. The LTSP
manual has this sample for syslog-ng's
configuration file /etc/syslog-ng/syslog-ng.conf:<br>
<br>
source net-udp { udp(); };<br>
destination remote {
file("/var/log/remote/$FULLHOST"); };<br>
log { source(net-udp); destination(remote); };<br>
<br>
Does anyone know if the rsyslogd would use the
same statements in its configuration file?<br>
</font><br>
</blockquote>
</div>
</div>
<font size="-1">I having a working recipe for this<font
size="-1"> (and I was wrong about rsyslog not
auto-starting<font size="-1"> -- it is good to go):</font></font><br>
<br>
To accomplish forwarding of syslog messages by TCP
(rather than by UDP or RELP):<br>
<br>
In /etc/rsyslog.conf for the client machine add this to
the end of the file:<br>
*.* @@<server's IP address>:10514<br>
<br>
For an LTSP network, if it is a standard LTSP 5 setup
with a chroot environment, then just edit the file as
above and update the image.<br>
<br>
For an LTSP network with an LTSP-PNP setup it is
trickier. For temporary troubleshooting you can just
modify /etc/rsyslog.conf, update the client NBD image,
then edit /etc/rsyslog.conf again with the settings
required for the server. If you want a permanent
forwarding setup that will not be overwritten by image
updates, then you would probably write a script in
/usr/share/ltsp/init-ltsp.d that modifies
/etc/rsyslog.conf in place on-the-fly during bootup
(using the stream editor command "sed"). But I have not
had a successful experience with that yet, so I merely
toss that out as a lead.<br>
<br>
-------------------<br>
<br>
In /etc/rsyslog.conf for the server where you want the
messages forwarded, un-comment these two lines in
rsyslog.conf:<br>
$ModLoad imtcp<br>
$InputTCPServerRun 10514<br>
<br>
This much alone on the server will cause forwarded
messages to be received on the server and incorporated
in the standard log file at /var/log/syslog. But they
will be added to the messages that are logged for the
server itself. That may do for your purposes since all
messages are tagged with the host name, but you can also
have the messages written to another file by adding
these lines to rsyslog.conf:<br>
<br>
if $fromhost-ip startswith '192.168.1.' then
/var/log/ltspclientlog<br>
& ~<br>
<br>
Substitute whatever client IP address applies in your
situation. The above command will separately log
received messages from any client with IP
192.168.1.xxx. Also substitute whatever log name you
would like for my choice of "ltspclientlog."<br>
<br>
The configuration above 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.<br>
</font><br>
</div>
<br>
--<br>
Lubuntu-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Lubuntu-users@lists.ubuntu.com">Lubuntu-users@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a
moz-do-not-send="true"
href="https://lists.ubuntu.com/mailman/listinfo/lubuntu-users"
target="_blank">https://lists.ubuntu.com/mailman/listinfo/lubuntu-users<br
clear="all">
<div><br>
</div>
-- <br>
</a><a moz-do-not-send="true"
href="https://wiki.ubuntu.com/phillw" target="_blank">https://wiki.ubuntu.com/phillw</a><br>
<br>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>