If its just the size of the file that's a problem can you possibly just quota the log file's size?
Manage Log File size on Ubuntu<http://www.watchingthenet.com/how-to-manage-log-file-size-archive-deletion.html>is one writeup which gives a lot of detail on how to use LogRotate.
I think this is the Man page for LogRotate<http://linuxcommand.org/man_pages/logrotate8.html> .
If you are just trying to figure out how to reduce the number of messages the above won't help.
Brian
On Wed, Aug 18, 2010 at 6:00 AM, <x2go-dev-request@lists.berlios.de> wrote:
Send X2go-dev mailing list submissions to x2go-dev@lists.berlios.de
To subscribe or unsubscribe via the World Wide Web, visit https://lists.berlios.de/mailman/listinfo/x2go-dev or, via email, send a message with subject or body 'help' to x2go-dev-request@lists.berlios.de
You can reach the person managing the list at x2go-dev-owner@lists.berlios.de
When replying, please edit your Subject line so it is more specific than "Re: Contents of X2go-dev digest..."
Today's Topics:
- Re: x2go-home (Mike Gabriel)
- Re: auth.log growing... (Mike Gabriel)
- Re: auth.log growing... (John A. Sullivan III)
Message: 1 Date: Mon, 16 Aug 2010 21:45:39 +0200 From: Mike Gabriel <m.gabriel@das-netzwerkteam.de> To: alexander.croessmann@gmail.com Cc: x2go-dev@lists.berlios.de Subject: Re: [X2go-dev] x2go-home Message-ID: <20100816214539.16496cdfj6w0pr37@mail.das-netzwerkteam.de> Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed"
Hi Alex,
On Mo 16 Aug 2010 14:57:36 CEST Alexander Cr?ssmann wrote:
Hi Mike,
my problem is solved. As I wrote in my first mail, I tired to connect from the localhost to the localhost which did not work.
However, I have two more questions: privileges? The browser plugin?
- Is there a way to install the windows client without admin
x2goclient: I suppose no... x2goplugin: should be possible (like any other ff plugin)
- Is there a way to run the server admin GUI on gnome? I get the message that kcontrol is missing. Although kdebase is installed.
since kde4 there is no more debian/ubuntu package called kcontrol. The replacement of kcontrol in kde4 is called systemsettings (name of the .deb package).
I am not sure enough if the admin GUIs will plug into systemsettings in the same way as they do with kcontrol. If so, the developers might provide a package update with the respective dependencies.
For you a work-around could be to provide a dummy kcontrol package with equivs-build (check equivs package on Ubuntu/Debian), just to satisfy dependencies in the x2go packages. However, this is untested...
Alex
Best, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
mail: m.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Message: 2 Date: Tue, 17 Aug 2010 22:55:31 +0200 From: Mike Gabriel <m.gabriel@das-netzwerkteam.de> To: x2go-dev@lists.berlios.de Subject: Re: [X2go-dev] auth.log growing... Message-ID: <20100817225531.11071pykb6ap4if7@mail.das-netzwerkteam.de> Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed"
Hi Paul,
on Tue May 26 11:40:43 CEST 2009 you had this request to the x2go-dev list:
Hello,
After installing X2go I see my auth.log is growing. I see this:
May 25 06:53:22 server sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/x2gopgwrapper listsessionsroot server May 25 06:53:22 server su[17628]: Successful su for postgres by root May 25 06:53:22 server su[17628]: + ??? root:postgres May 25 06:53:22 server su[17628]: pam_unix(su:session): session opened for user postgres by (uid=0) May 25 06:53:22 server su[17628]: pam_unix(su:session): session closed for user postgres May 25 06:53:23 server CRON[16311]: pam_unix(cron:session): session closed for user root May 25 06:53:28 server sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/x2gopgwrapper listsessionsroot server (...)
I did a "/etc/init.d/x2goserver stop" and that helps. And I can still login on the X2go server!
I see it is checking the database, but I don't understand why exactly. Is it really necessary to do this every 5 seconds?
echo "select agent_pid, session_id, display, server, status,
to_char(init_time,'DD.MM.YY*HH24:MI:SS'),cookie,client,gr_port,
sound_port,to_char(last_time,'DD.MM.YY*HH24:MI:SS'),uname,
to_char(now()-init_time,'SSSS'),fs_port from sessions
where server='$2' order by status desc;"|psql -t x2go_sessions ;;I saw you can change the sleep-time (5 seconds) in this script: /usr/sbin/x2gocleansessions but I am not sure this is a good idea...
With regards. Paul van der Vlis.
have you already found a solution to this??? I experience the same issue tried to look for a sudo hack to silence log file output but was not successful...
Any ideas on this? Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
mail: m.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Message: 3 Date: Tue, 17 Aug 2010 17:08:41 -0400 From: "John A. Sullivan III" <jsullivan@opensourcedevel.com> To: x2go-dev@lists.berlios.de Subject: Re: [X2go-dev] auth.log growing... Message-ID: <1282079321.24219.14.camel@denise.theartistscloset.com> Content-Type: text/plain; charset="UTF-8"
Hi Paul,
on Tue May 26 11:40:43 CEST 2009 you had this request to the x2go-dev
On Tue, 2010-08-17 at 22:55 +0200, Mike Gabriel wrote: list:
Hello,
After installing X2go I see my auth.log is growing. I see this:
May 25 06:53:22 server sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/x2gopgwrapper listsessionsroot server May 25 06:53:22 server su[17628]: Successful su for postgres by root May 25 06:53:22 server su[17628]: + ??? root:postgres May 25 06:53:22 server su[17628]: pam_unix(su:session): session opened for user postgres by (uid=0) May 25 06:53:22 server su[17628]: pam_unix(su:session): session closed for user postgres May 25 06:53:23 server CRON[16311]: pam_unix(cron:session): session closed for user root May 25 06:53:28 server sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/x2gopgwrapper listsessionsroot server (...)
I did a "/etc/init.d/x2goserver stop" and that helps. And I can still login on the X2go server!
The x2goserver daemon isn't actually the server; it starts the x2gocleansessions daemon which cleans up after sessions in various states every five seconds as you note below. The actual connections to the server are all driven from the client via ssh by calling various scripts on the server.
I see it is checking the database, but I don't understand why exactly. Is it really necessary to do this every 5 seconds?
echo "select agent_pid, session_id, display, server, status,
to_char(init_time,'DD.MM.YY*HH24:MI:SS'),cookie,client,gr_port,
sound_port,to_char(last_time,'DD.MM.YY*HH24:MI:SS'),uname,
to_char(now()-init_time,'SSSS'),fs_port from sessions
where server='$2' order by status desc;"|psql -t x2go_sessions ;;I saw you can change the sleep-time (5 seconds) in this script: /usr/sbin/x2gocleansessions but I am not sure this is a good idea...
I posted a description of what the various parts of X2Go do to the list a while ago. It included a discussion of the session cleanup process if you would find that helpful.
With regards. Paul van der Vlis.
have you already found a solution to this??? I experience the same issue tried to look for a sudo hack to silence log file output but was not successful...
Any ideas on this? Greets, Mike
We did not find a way to silence the logs and, in our case, it was even worse because we were doing LDAP lookups every five seconds for the postgres user. However, we did consolidate to a single, centralized database for all X2Go Servers. We also created a single cleanup daemon to clean up all X2Go Servers so that we didn't have hundreds of daemons all running every five seconds. We had the advantage that our X2Go Servers were built on VServers to the cleanup up script has direct access to the file systems on all the X2Go Servers. The routine could probably be easily hacked to provide the same access via SSH and use a single cleanup daemon. I posted the patches and documentation a while ago.
I have some more changes to post which refine it but have not had the time to document and post them. If someone does have the time, the patches should really be rewritten to be configurable options. As I posted them, they are a rip and replace patch - almost more of a fork which is the last thing on Earth I want to do . . . well . . . almost the last thing ;-) - John
X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
End of X2go-dev Digest, Vol 20, Issue 11