Jim Kronebusch | 1 Sep 2007 04:12
Favicon

Re: Remote reboot in ltsp5 - Q & D

> Quick, dirty, gets the job done.

Scott, works perfectly and definitely gets the job done.  Only problem is it doesn't
properly quit these processes:

7196 	nobody 	0.0 % 	21:07 	/bin/sh /usr/sbin/nbdswapd
7213 	nobody 	0.0 % 	21:07 	/bin/nbd-server 0 /tmp/fileEEyGZb

Is this a problem and should they be manually killed?  I've noticed if clients aren't
shut down with the shutdown button at the login screen these processes are left over. 
If it isn't a big deal I'll just let them clean themselves up when the server reboots.

I have made scripts and put them on my desktop in a folder called "Client Shutdown".  I
have a script for each of my labs.  Now I can just double click a file and the whole lab
shuts down......awesome!

Thanks,
Jim

--

-- 
This message has been scanned for viruses and
dangerous content by the Cotter Technology 
Department, and is believed to be clean.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_____________________________________________________________________
(Continue reading)

Fajar Priyanto | 1 Sep 2007 04:25
X-Face

Re: Keeping sessions open?

On Friday 31 August 2007 15:43:59 Fredrik Kjellman wrote:
> Hi,
> I'm trying to get my user sessions to stay active even after the user
> logged out (as an alternative to closing the whole session). Is it possible
> to keep their workspace open when they turn of their thin client, and than
> (perhaps at another client) reconnect to this session and make it active
> again?
>
> Best regards,
> Fred

Hello Fred,
I'm not sure if this is possible, but I have been experimenting:
1. If we unplug the network cable for a short time (less than 1 minute), the 
session resumes. If longer, it fails to resume (hang).
2. If we unplug the cable and restart (hard reboot) the client, it doesn't 
resume.
3. If we turn off the server while keep the client running, next time the 
server up, the client automatically resumes (logon screen), no need to 
restart the client.

Cheers,
--

-- 
Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial 
http://linux2.arinet.org
09:21:03 up 1:09, 2.6.20-16-generic GNU/Linux 
Let's use OpenOffice. http://www.openoffice.org
-------------------------------------------------------------------------
(Continue reading)

Scott Balneaves | 1 Sep 2007 05:17
Picon

Re: Remote reboot in ltsp5 - Q & D

On Fri, Aug 31, 2007 at 09:12:11PM -0500, Jim Kronebusch wrote:
> > Quick, dirty, gets the job done.
> 
> Scott, works perfectly and definitely gets the job done.  Only problem is it doesn't
> properly quit these processes:
> 
> 7196 	nobody 	0.0 % 	21:07 	/bin/sh /usr/sbin/nbdswapd
> 7213 	nobody 	0.0 % 	21:07 	/bin/nbd-server 0 /tmp/fileEEyGZb

check your /etc/hosts.allow.  You should have:

nbdswapd: ALL: keepalive

in there.  If you do, they'll exit quietly and clean up after themselves
after 2 hours, all by their lonesomes.

If not, add it :)

Scott

--

-- 
Scott L. Balneaves | "Eternity is a very long time,
Systems Department |  especially towards the end."
Legal Aid Manitoba |    -- Woody Allen

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
(Continue reading)

Jim Kronebusch | 1 Sep 2007 05:38
Favicon

Re: Remote reboot in ltsp5 - Q & D

On Fri, 31 Aug 2007 22:17:41 -0500, Scott Balneaves wrote
> On Fri, Aug 31, 2007 at 09:12:11PM -0500, Jim Kronebusch wrote:
> > > Quick, dirty, gets the job done.
> > 
> > Scott, works perfectly and definitely gets the job done.  Only problem is it doesn't
> > properly quit these processes:
> > 
> > 7196 	nobody 	0.0 % 	21:07 	/bin/sh /usr/sbin/nbdswapd
> > 7213 	nobody 	0.0 % 	21:07 	/bin/nbd-server 0 /tmp/fileEEyGZb
> 
> check your /etc/hosts.allow.  You should have:
> 
> nbdswapd: ALL: keepalive
> 
> in there.  If you do, they'll exit quietly and clean up after themselves
> after 2 hours, all by their lonesomes.
> 
> If not, add it :)

Default Edubuntu install and the line is not there....I added it.

Thanks

--

-- 
This message has been scanned for viruses and
dangerous content by the Cotter Technology 
Department, and is believed to be clean.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
(Continue reading)

David Nielson | 1 Sep 2007 16:11
Picon

Re: Keeping sessions open?

Fajar Priyanto wrote:
> On Friday 31 August 2007 15:43:59 Fredrik Kjellman wrote:
>   
>> Hi,
>> I'm trying to get my user sessions to stay active even after the user
>> logged out (as an alternative to closing the whole session). Is it possible
>> to keep their workspace open when they turn of their thin client, and than
>> (perhaps at another client) reconnect to this session and make it active
>> again?
>>
>> Best regards,
>> Fred
>>     

This is a great idea. One thing I would like to have for my network is a 
persistent "bittorrent" user, who would have only one program open, but 
have it going all the time, persistently. Any user with the password 
would be able to log in, check the status of torrents, add or remove 
torrents, and then log out and have the server be swarming day and night 
until their downloads were finished.

Is this possible?

-David

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
(Continue reading)

Frank Cox | 1 Sep 2007 18:14
Favicon

inter-user messaging

What is the best way to implement an inter-user message system on a LTSP
server?  It's currently running Fedora Core 6 with Gnome desktops.

The objective is to allow pop-up messages between users, sort of a "private MSN
chat"  thing.

--

-- 
MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Jim McQuillan | 1 Sep 2007 18:22

Re: inter-user messaging

Frank,

I use jabber (ejabberd) and gaim

makes a great Instant messaging system.

Jim McQuillan
jam@...

Frank Cox wrote:
> What is the best way to implement an inter-user message system on a LTSP
> server?  It's currently running Fedora Core 6 with Gnome desktops.
> 
> The objective is to allow pop-up messages between users, sort of a "private MSN
> chat"  thing.
> 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Frank Cox | 1 Sep 2007 18:49
Favicon

Re: inter-user messaging

On Sat, 01 Sep 2007 12:22:49 -0400
Jim McQuillan <jam@...> wrote:

> Frank,
> 
> I use jabber (ejabberd) and gaim
> 
> makes a great Instant messaging system.

Now that looks like the real McCoy!

Thanks, Jim.  Now I have a project for this weekend....

--

-- 
MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Mats Lundqvist | 3 Sep 2007 09:30
Picon

Re: Keeping sessions open?

Hello David...

Vnc is exactly what you need. It'll create a persistant session, bound
to a single user. And when you're done checking your torrents, just
close your vnc-client.

2007/9/1, David Nielson <naptastic@...>:
> Fajar Priyanto wrote:
> > On Friday 31 August 2007 15:43:59 Fredrik Kjellman wrote:
> >
> >> Hi,
> >> I'm trying to get my user sessions to stay active even after the user
> >> logged out (as an alternative to closing the whole session). Is it possible
> >> to keep their workspace open when they turn of their thin client, and than
> >> (perhaps at another client) reconnect to this session and make it active
> >> again?
> >>
> >> Best regards,
> >> Fred
> >>
>
> This is a great idea. One thing I would like to have for my network is a
> persistent "bittorrent" user, who would have only one program open, but
> have it going all the time, persistently. Any user with the password
> would be able to log in, check the status of torrents, add or remove
> torrents, and then log out and have the server be swarming day and night
> until their downloads were finished.
>
> Is this possible?
>
(Continue reading)

Ondrej Valousek | 3 Sep 2007 13:50
Picon
Favicon

Re: Keeping sessions open?

Hi all,
We use nomachine NX client to make persistent sessions (i.e. whole
desktop is running in NX) but freeNX would work as well.
This is also much faster than VNC.
Note that plain X11 protocol can not be made persistent, this can only
be achieved via NX/VNC/Citrix ICA
Ondrej

Mats Lundqvist wrote:
> Hello David...
>
> Vnc is exactly what you need. It'll create a persistant session, bound
> to a single user. And when you're done checking your torrents, just
> close your vnc-client.
>
> 2007/9/1, David Nielson <naptastic@...>:
>   
>> Fajar Priyanto wrote:
>>     
>>> On Friday 31 August 2007 15:43:59 Fredrik Kjellman wrote:
>>>
>>>       
>>>> Hi,
>>>> I'm trying to get my user sessions to stay active even after the user
>>>> logged out (as an alternative to closing the whole session). Is it possible
>>>> to keep their workspace open when they turn of their thin client, and than
>>>> (perhaps at another client) reconnect to this session and make it active
>>>> again?
>>>>
>>>> Best regards,
(Continue reading)


Gmane