Updated how-to for the new rsyslog format and logging to a separate
file:
1) Create /etc/rsyslog.d/20-ltsp.conf with the following contents:
ruleset(name="remote") {
action(type="omfile" file="/var/log/ltsp-clients.log")
}
# bind ruleset to tcp listener and activate it:
module(load="imudp")
A quick how-to for those seeking to enable remote logging for ltsp
clients in Ubuntu.
1) Uncomment the following lines in /etc/rsyslog.conf:
# provides UDP syslog reception
$ModLoad imudp
$UDPServerRun 514
2) Restart rsyslog:
sudo service rsyslog restart
3) Set the following line in lts.conf:
This bug was fixed in the package ltsp - 5.4.2-2ubuntu1
---
ltsp (5.4.2-2ubuntu1) quantal; urgency=low
* Merging from Debian. Remaining changes:
- Include dhcpd.conf configuration using 192.168.0.1/24 instead of upstream
192.168.67.0/24 (until we deal with upgrades
Fix released in LTSP 5.4.1.
** Changed in: ltsp
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/697387
Title:
SYSLOG option in lts.conf not documented
To
Committed: Defaulted local syslog, define SYSLOG_HOST in lts.conf for
remote logging.
** Changed in: ltsp
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/697387
** Changed in: ltsp (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/697387
Title:
SYSLOG option in lts.conf not documented
To manage notifications about
Agreed with alkisg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/697387
Title:
SYSLOG option in lts.conf not documented
To manage notifications about this bug go to:
Maybe the following line could be changed in the code:
- if [ -z $SYSLOG ] || [ $SYSLOG = remote ]; then
+ if [ ${SYSLOG_HOST-localhost} != localhost ]; then
The weird ${SYSLOG_HOST-localhost} syntax means if SYSLOG_HOST is set, but
empty, then return the string localhost.
So to disable remote
Another problem is that the default configuration file name is defined in the
configure_syslog() function as:
syslog_conf=/etc/rsyslog.d/ltsp.conf
That, in Ubuntu, doesn't override the defaults in
/etc/rsyslog.d/50-default.conf, so by default LTSP clients log locally,
not on the server, contrary
To complete Alkis point: as one need to setup also the server
rsyslog.conf, I don't see why default SYSLOG is true.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/697387
Title:
SYSLOG option in
Current behaviour of configure_syslog() seems a little weird, shouldn't
it just be SYSLOG=true or false ? Or replace SYSLOG by
SYSLOG_REMOTE=true or false, to make the option clearer?
** Attachment added: varlistentry for SYSLOG in lts.conf.xml
** Changed in: ltsp (Ubuntu)
Status: New = Triaged
** Also affects: ltsp
Importance: Undecided
Status: New
** Changed in: ltsp
Status: New = Triaged
** Changed in: ltsp
Importance: Undecided = Low
--
You received this bug notification because you are a member of
12 matches
Mail list logo
