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 is one writeup which gives a lot of detail on how to use LogRotate.
I think this is the Man page for LogRotate.
If you are just trying to figure out how to reduce the number of messages the above won't help.
Brian
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:
1. Re: auth.log growing... (Paul van der Vlis)
----------------------------------------------------------------------
Message: 1
Date: Thu, 19 Aug 2010 11:12:38 +0200
From: Paul van der Vlis <paul@vandervlis.nl>
To: x2go-dev@lists.berlios.de
Subject: Re: [X2go-dev] auth.log growing...
Message-ID: <4C6CF586.5050306@vandervlis.nl>
Content-Type: text/plain; charset=UTF-8
Mike Gabriel schreef:
> 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...
No sorry, I have not found a solution.
I think it would be easy to run x2gocleansessions as root to avoid the
auth.log mess-up, but maybe there is a better way.
Met vriendelijke groet,
Paul van der Vlis.
--
http://www.vandervlis.nl/
------------------------------
_______________________________________________
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 12
****************************************