[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Replace LTSP show blocker FAM by GAMIN?



Am Montag 14 September 2009 schrieb José "L. Redrejo" Rodríguez:
> I strongly support this. I'm removing it too in the ltsp servers and
> workstations and don't find any reason to keep this installed.

Okay, great. Let's file a bug report on this -- and also against fam!
And let's remove this package (or have it replaced) by default 
installation.

As my server was upgraded, "locate kill |grep edu" delivered:


/etc/debian-edu/nightkill.conf
/usr/share/debian-edu-config/tools/logoutkill.sh
/usr/share/debian-edu-config/tools/nightkill.sh


Peeking into nightkill.sh gave me a dejavu:

# $Id: logoutkill.sh 42155 2008-07-02 12:54:32Z holger $
# This script could be run from /etc/kde2/kdm/Xreset by adding the line
# '/usr/share/debian-edu-config/tools/logoutkill.sh $USER'
# right before the line
# 'exit 0'


Mind the date and "kde2"!

Nevertheless, there ARE quite a few processes left behind (e.g. 
openoffice) that are not using any CPU time but memory. As opposed to 
htop, top counts also "zombies" (but not these ones) - I can give you 
some example:

$top -bn1|grep soffice
  330 de-realv  20   0  191m  19m 2668 S    0  0.5   0:00.14 soffice.bin
 2299 a12-tiwi  20   0  344m  21m 5416 S    0  0.6   0:00.02 soffice.bin
 3109 a12-kieb  20   0  344m  21m 5320 S    0  0.5   0:00.02 soffice.bin
 4121 sd-dekor  20   0  208m  21m 2828 S    0  0.5   0:00.32 soffice.bin
 4347 sd-lakuh  20   0  344m  22m 5416 S    0  0.6   0:00.02 soffice.bin
 4381 sd-lakuh  20   0  387m  25m 5588 S    0  0.7   0:00.02 soffice.bin
 5122 px-cehor  20   0  345m  22m 5416 S    0  0.6   0:00.02 soffice.bin
 5480 ig-alwag  20   0  189m  22m 2664 S    0  0.6   0:00.14 soffice.bin
10076 de-lumas  20   0  346m  22m 5444 S    0  0.6   0:00.02 soffice.bin
10908 sd-cafra  20   0  343m  21m 5372 S    0  0.5   0:00.02 soffice.bin
10973 de-saalb  20   0  344m  21m 5416 S    0  0.6   0:00.02 soffice.bin
12264 vhs09     20   0  205m  79m  55m S    0  2.0   0:09.96 soffice.bin
12292 a10-andu  20   0  343m  21m 5376 S    0  0.5   0:00.02 soffice.bin
13483 ls-janic  20   0  192m  20m 2664 S    0  0.5   0:00.14 soffice.bin
13903 pab-zer   20   0  194m  27m 2792 S    0  0.7   0:00.20 soffice.bin
13907 ig-sawie  20   0  343m  21m 5376 S    0  0.5   0:00.02 soffice.bin
16362 kl-islut  20   0  344m  22m 5416 S    0  0.6   0:00.02 soffice.bin
17280 vhs09     20   0  205m  27m 2904 S    0  0.7   0:00.20 soffice.bin
21905 a12-alsc  20   0  343m  22m 5384 S    0  0.6   0:00.02 soffice.bin
22245 a11-elsc  20   0  192m  20m 2672 S    0  0.5   0:00.14 soffice.bin
23856 de-rewyr  20   0  191m  20m 2964 S    0  0.5   0:00.36 soffice.bin
25847 sd-mipet  20   0  192m  19m 2800 S    0  0.5   0:00.14 soffice.bin
27788 de-niwol  20   0  213m  32m 2864 S    0  0.8   0:00.20 soffice.bin
27929 de-rewyr  20   0  203m  27m 2872 S    0  0.7   0:00.20 soffice.bin
31020 de-maeic  20   0  191m  19m 2816 S    0  0.5   0:00.14 soffice.bin
31649 de-maeic  20   0  191m  19m 2656 S    0  0.5   0:00.14 soffice.bin
32390 a12-phbe  20   0  181m  19m 3160 S    0  0.5   0:00.48 soffice.bin

Those are all left-behinds from during the past week.

I suggest to re-introduce those auto-kill scripts by defaults.

Additionally/alternatively, I have some energy-saving idea:

I remember pere having introduced some script that turns off terminals 
over night. Why not even turn off LTSP servers (apart from 
combiservers)? To do so
(1) The main server (tjener) must wake up them in the morning.
(2) LTSP servers have to check if they are able to wake on LAN
(3) LTSP servers that are so, have to shutdown at night.

1. Tjener: [cronjob at 6 am] for all known LTSP (LDAP?): etherwake!
         + touch /skole/tjener/home0/system/etherwake (rm after 10 min)
2. LTSP:   [at boot time]:
       if /skole/tjener/home0/system/etherwake exists (etherwake works!)
       => activate cronjob for shutting down at night.
3. LTSP:  [script to shutdown over night (only run if I am not tjener)]
       shutdown at midnight.

This idea has fixed times (midnight until 6 a.m.) that should be pre-
defined in ldap, so they can be changed on demand.
          
What do you think?
Regards
Ralf


Reply to: