[gentoo-user] Re: configuring x2go on gentoo

[Nikos Chantziaras <realnc@arcor.de>]

On 02/02/2010 04:37 PM, Valmor de Almeida wrote:
> On Mon, Feb 1, 2010 at 1:57 PM, Nikos Chantziaras<realnc@arcor.de>  wrote:
>> On 02/01/2010 08:06 PM, Valmor de Almeida wrote:
> [snip]
>>
>> Don't know about the server configuration on Gentoo.  I only run the client
>> on my Gentoo box.  The server runs on a Debian machine and IIRC the
>
> Here are the steps I followed to configure and test the server.
>
> 1) emerge x2goserver  (needed to rebuild the kernel with FUSE)
> 2) following message from emerge of postgresql-8.1.11 did:
>         emerge --config =postgresql-8.1.11
> 3)  /etc/init.d/postgresql start
> 4) visudo and added
>      users ALL=(ALL) NOPASSWD: /usr/bin/x2gopgwrapper
> 5) run script to create database
>       cd /usr/share/x2go/script
>       ./x2gocreatebase.sh
> 6) /etc/init.d/postgresql restart
> 7) /etc/init.d/x2goserver start
>
> The /var/log/messages file is filled with
>
> Feb  1 17:45:56 xeon0 sudo:     root : TTY=unknown ; PWD=/ ; USER=root
> ; COMMAND=/usr/bin/x2gopgwrapper listsessionsroot xeon0
> Feb  1 17:45:56 xeon0 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Feb  1 17:45:56 xeon0 sudo: pam_unix(sudo:session): session closed for user root
> Feb  1 17:45:56 xeon0 su[3869]: Successful su for postgres by root
> Feb  1 17:45:56 xeon0 su[3869]: + ??? root:postgres
> Feb  1 17:45:56 xeon0 su[3869]: pam_unix(su:session): session opened
> for user postgres by (uid=0)
> Feb  1 17:45:57 xeon0 su[3869]: pam_unix(su:session): session closed
> for user postgres
> Feb  1 17:46:02 xeon0 sudo:     root : TTY=unknown ; PWD=/ ; USER=root
> ; COMMAND=/usr/bin/x2gopgwrapper listsessionsroot xeon0
> Feb  1 17:46:02 xeon0 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Feb  1 17:46:02 xeon0 sudo: pam_unix(sudo:session): session closed for user root
> Feb  1 17:46:02 xeon0 su[3880]: Successful su for postgres by root
> Feb  1 17:46:02 xeon0 su[3880]: + ??? root:postgres
> Feb  1 17:46:02 xeon0 su[3880]: pam_unix(su:session): session opened
> for user postgres by (uid=0)
> Feb  1 17:46:02 xeon0 su[3880]: pam_unix(su:session): session closed
> for user postgres
>
> Any ideas on how to stop this?

I get that too.  I just ignore it though.  If the messages bother you, I 
guess you can have syslog-ng filter them out.  It would probably be 
cleaner to suppress them at their origin - that would be sudo and su - 
but I don't know how.