hi all,
today I have added syslog support to all X2go Server scripts.
Currently, two log levels are used:
debug -> mostly for db debugging info -> write to syslog whenever one of the X2go Server commands is called
The default loglevel is ,,notice''. For this level, I plan to log if a
session has been started/suspended/resumed/terminated.
More to come later, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Fri, 2011-09-09 at 18:31 +0200, Mike Gabriel wrote:
hi all,
today I have added syslog support to all X2go Server scripts.
Currently, two log levels are used:debug -> mostly for db debugging info -> write to syslog whenever one of the X2go Server commands is called
The default loglevel is ,,notice''. For this level, I plan to log if a
session has been started/suspended/resumed/terminated.More to come later, Mike <snip> Not that it's critically important but, if you insert the word ERROR when logging an error condition, I believe it can be picked up by OSSEC for log reporting - John
Hi John,
On Fr 09 Sep 2011 18:52:22 CEST "John A. Sullivan III" wrote:
On Fri, 2011-09-09 at 18:31 +0200, Mike Gabriel wrote:
hi all,
today I have added syslog support to all X2go Server scripts. Currently, two log levels are used:
debug -> mostly for db debugging info -> write to syslog whenever one of the X2go Server commands
is calledThe default loglevel is ,,notice''. For this level, I plan to log if a session has been started/suspended/resumed/terminated.
More to come later, Mike <snip> Not that it's critically important but, if you insert the word ERROR when logging an error condition, I believe it can be picked up by OSSEC for log reporting - John
Not sure what your request is: shall I avoid that or include that as a
feature?
Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Fri, 2011-09-09 at 18:54 +0200, Mike Gabriel wrote:
Hi John,
On Fr 09 Sep 2011 18:52:22 CEST "John A. Sullivan III" wrote:
On Fri, 2011-09-09 at 18:31 +0200, Mike Gabriel wrote:
hi all,
today I have added syslog support to all X2go Server scripts. Currently, two log levels are used:
debug -> mostly for db debugging info -> write to syslog whenever one of the X2go Server commands
is calledThe default loglevel is ,,notice''. For this level, I plan to log if a session has been started/suspended/resumed/terminated.
More to come later, Mike <snip> Not that it's critically important but, if you insert the word ERROR when logging an error condition, I believe it can be picked up by OSSEC for log reporting - John
Not sure what your request is: shall I avoid that or include that as a
feature?Mike
Hi, Mike. It was just information. As you craft the message for error conditions, if you use the string ERROR, OSSEC users will be able to pick up those error automatically and alert on them. It would be nice feature for OSSEC users (like us!). Thanks - John
Hi all,
On Fr 09 Sep 2011 18:31:26 CEST Mike Gabriel wrote:
hi all,
today I have added syslog support to all X2go Server scripts.
Currently, two log levels are used:debug -> mostly for db debugging info -> write to syslog whenever one of the X2go Server commands is called
The default loglevel is ,,notice''. For this level, I plan to log if
a session has been started/suspended/resumed/terminated.
the syslogging feature in x2goserver and cups-x2go is now +/- complete
and ready for testing. For those interested in testing:
o install x2goserver+cups-x2go from our nightly builds (Debian/Ubuntu) o edit /etc/x2go/x2goserver o there should be a ini section [log] with only option loglevel= o switch it to err, warning, notice, info or debug here o use your x2goserver and watch the /var/log/syslog file meanwhile...
As I have edited mostly all x2goserver scripts to implement this,
there might be some typos or other bugs that sneaked in. Please help
with testing the modified code.
The full diff for x2goserver syslogging is this:
git diff
7f7ec2c82959950ef5ef2186b2c2ff658f8508ca..f12dab5a48c70cd32a54ddb5418948bd28dad2b1
Greets+Thanks, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Saturday 10 September 2011 08:14:51 Mike Gabriel wrote:
The full diff for x2goserver syslogging is this: git diff 7f7ec2c82959950ef5ef2186b2c2ff658f8508ca..f12dab5a48c70cd32a54ddb5418948bd28 dad2b1
Greets+Thanks, Mike
Mike,
shouldn't
[limit groups] #x2gousers=1
be
[limit groups] #x2gouser=1
?
I thought the group was x2gouser (singular), not x2gousers (plural).
And thanks for the debugging option! I'm sure it'll help many people.
IvanK.
Hi Ivan, On Sa 10 Sep 2011 15:14:57 CEST Ivan Kabaivanov wrote:
Mike,
shouldn't
[limit groups] #x2gousers=1
be
[limit groups] #x2gouser=1
?
No, the group x2gouser must stay empty!!!! Otherwise people in that group will be able to directly access the SQLite DB file. I have changed the user and group names completely now as they are only examples: <quote> index 61312ee..5fa6baf 100644 (file) --- a/x2goserver/etc/x2goserver.conf +++ b/x2goserver/etc/x2goserver.conf @@ -1,8 +1,8 @@ [limit users] -#beispielb=1 +#user-foo=1 [limit groups] -#x2gousers=1 +#bar-group=1 [log] # possible levels are: emerg, alert, crit, err, warning, notice, info, debug </quote> Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
-
Ivan Kabaivanov -
John A. Sullivan III -
Mike Gabriel