[FreeNX-kNX] Problem with listsession

Aron auryn at wanadoo.es
Tue Jun 15 07:20:54 UTC 2010


On Lunes, 14 de Junio de 2010 13:04:07 chris at ccburton.com escribió:
> Aron <auryn at wanadoo.es> wrote on 14/06/2010 10:54:11:
> > On Jueves, 3 de Junio de 2010 11:11:40 chris at ccburton.com escribió:
> > > sergio garcia escriche <sergei.garcia at gmail.com> wrote on 26/05/2010
> > > 
> > > 15:03:48:
> > > > Hi,
> > > > 
> > > > I have freenx Version 3.2.0-74-SVN OS (GPL, using backend: 3.3.0). I
> > > > would like a kill a session from session name. I tried nxserver --
> > > > list and not show the session name. I tried listsession command and
> > > > show me the next message "command not found". Do you know how i can
> > > > kill session from session name??
> > > 
> > > If I understood what you meant by "session name" I might be able to
> 
> OK, sessionID.
> 
> > > suggest
> > > something.
> > > 
> > > You've looked at pkill -u I suppose ??
> > 
> > Same problem: the connections are working, but I can't see any of them:
> > # sudo nxserver --list
> > NX> 100 NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.4.0)
> > NX> 127 Sessions list:
> > 
> > Server     Display Username        Remote IP       Session ID
> > ------ ------- --------------- ---------------
> > --------------------------------
> > NX> 999 Bye
> 
> Hmmm, that's not right if there are running sessions.
> 
> Are you using "normal" ssh sessions ??
> 
> What is in
>                 /var/lib/nxserver/db/running
> when sessions are running but not showing.
> 
> Does it look like  . . .
> -rw-r--r-- 1 nx nx    306 2010-06-14 09:01
> sessionId{5B8BB116CD28C909CA1D10F5F8374C5B}
> -rw-r--r-- 1 nx nx    312 2010-06-14 09:16
> sessionId{67D9478BE5DE213376489A57FB0AD8CC}
> -rw-r--r-- 1 nx nx    305 2010-06-14 09:18
> sessionId{6D50EE53D20B4FF891998B3D06D498C7}
> -rw-r--r-- 1 nx nx    316 2010-06-14 11:18
> sessionId{C02C5A02F5A61B1747F7AC64E8CC6605}
> etc
> 
> This is where --list gets its data
> 
> What happens if you run
>          sudo /usr/bin/nxserver --terminate
> C02C5A02F5A61B1747F7AC64E8CC6605
> with the correct sessionID number substituted, on one of the entries.
> 
> Does it terminate ??
> 
> 
> I tend to just kill the offending nxagent(s)

Well, in my case, I've just reinstalled freenx-server and now it's working.

Thanks



More information about the FreeNX-kNX mailing list