|00:14||MorningSon has quit IRC|
|00:41||alkisg has quit IRC|
|00:51||daya has quit IRC|
|00:51||daya has joined #ltsp|
|01:41||Mava has quit IRC|
|01:48||gnunux has joined #ltsp|
|02:21||komunista has joined #ltsp|
|02:31||alkisg has joined #ltsp|
|02:44||alkisg has quit IRC|
|02:45||alkisg has joined #ltsp|
|02:46||alkisg has quit IRC|
|03:22||komunista has quit IRC|
|03:37||alkisg has joined #ltsp|
What's the purpose of the 000-init-whitelist plugin? It deletes some rc.d links and so some services don't start on thin/fat clients: http://ltsp.pastebin.com/4tyEJhSw
|03:59||Gremble has joined #ltsp|
That's probably the reason why some people here complain about cups, ondemand, sendsigs, rc.local, binfmt-support, openbsd-inetd, winbind etc not working with localapps and fat clients...
If that list is indeed needed, it should be revisited
I think Debian doesn't use that list at all, it's commented out: #RCS_WHITELIST=$ ...
So maybe Ubuntu should sync with Debian on this, i.e. in Ubuntu/000-basic-configuration
|04:20||Gremble has quit IRC|
I reported it at https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/694066
I'll try commenting them out, building a fat chroot, and if it works OK I'll commit it...
|04:38||jimjimovich has joined #ltsp|
good morning everyone
what's the best way to put run a script each time a user logs into ltsp?
the script needs to be run as that user
Put it in the server /etc/xdg/autostart
(as a .desktop file, see examples there)
thanks, that's exactly what i was looking for!
|04:45||alexqwesa has quit IRC|
|04:46||alexqwesa has joined #ltsp|
|04:50||baiki has joined #ltsp|
|04:55||baiki has quit IRC|
|05:11||komunista has joined #ltsp|
|05:14||daya has quit IRC|
|05:14||daya has joined #ltsp|
|05:21||Gremble has joined #ltsp|
|05:25||gnunux has quit IRC|
|05:29||baiki has joined #ltsp|
@alkisg hi. i updated this bugreport with the graca output from the thin client
01:00.0 VGA compatible controller : VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 [S3 UniChrome Pro] [1106:3344] (rev 01)
baiki: nice, it seems that *only* unichrome cards are affected
one more question: since I can't see any different on the thin clients screen resolution i assume i am modifying the wrong lts.conf. Is this the right path: /var/lib/tftpboot/ltsp/i386/lts.conf
i try to set this value "X_MODE_0 = 1024x768" in /var/lib/tftpboot/ltsp/i386/lts.conf and afterwards an image update but.... nope :-(
Don't forget to put [Default] on top of it
ok, will try right now. thanks a lot.
baiki: you don't need to update the image when you modify lts.conf
|05:44||baiki has quit IRC|
|05:52||baiki has joined #ltsp|
@alkisg nope. did not work out for me. i used this: http://pastebin.com/p8NRL3Kr
baiki: "compiz" :: the default window manager in gnome is gnome-wm, which automatically chooses compiz if it thinks that the card supports it. Compiz is causing login problems to some clients (LP #673072). To disable it, see !disable_compiz. To restore it, see !restore_compiz
baiki: Error: "XRANDR_MODE_0" is not a valid command.
alkisg: "localxterm" :: while sitting on a thin client, open a gnome terminal. In that, run: ltsp-localapps xterm. An xterm will open. That xterm runs locally, so any commands you enter there are executed directly on the client.
baiki: "disable_compiz" :: To disable compiz, try: sudo gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type string --set /desktop/gnome/session/required_components/windowmanager metacity
baiki: open a localxterm (on the client) and run: getltscfg -a
|06:06||baiki has quit IRC|
|06:06||Trixboxer has joined #ltsp|
|06:08||baiki has joined #ltsp|
@alkisg here is the output of getltscfg -a: XRANDR_MODE_0="1024x768" (newline) export XRANDR_MODE_0
baiki: ok, now run this: xrandr
and pastebin the output
|06:15||baiki has quit IRC|
alkisg: "xauthority" :: to access the client X session from a local root shell, try: eval $(tr '\0' '\n' < /proc/$(pidof -s ldm gdm-simple-greeter gnome-session | cut -d' ' -f1)/environ | egrep '^DISPLAY=|^XAUTHORITY=') && export DISPLAY XAUTHORITY
|06:20||baiki has joined #ltsp|
@alkisg can't open pastebin
Screen 0: minimum 640 x 480, current 800 x 600, maximum 800 x 600 default connected 800x600+0+0 0mm x 0mm 800x600 60.0* 56.0 640x480 60.0
baiki: ok the problem is that your monitor timings aren't correctly detected
Is that on the openchrome thin client?
possible. it's a CRT (and old) 17"
What's the graphics card driver? openchrome?
yes, on the hpt3350. if i do this on the TC itself i get: can't open display if i enter xrandr
Wait wait what?
if i do this on the TC itself i get: can't open display if i enter xrandr ==> ?
Just open a gnome-terminal on the thin client (=the TC) and run xrandr...
That shouldn't say "can't open display"...
yes, the 800x600 output is from the gnome-terminal
Try putting those in lts.conf:
(also keep the XRANDR_MODE_0)
and reboot the client
|06:31||baiki has quit IRC|
|06:36||jimjimovich has left #ltsp|
|06:41||Gremble has quit IRC|
|06:43||baiki has joined #ltsp|
@alkisg yes man!! the h/v sync and refresh did the job. thanks a lot. got i question for today left: LDM_ALLOW_USER does not work. can login with all users
|06:51||baiki has quit IRC|
|07:06||alkisg has quit IRC|
|07:09||jimjimovich has joined #ltsp|
okay, I now have a startup script running when a user logs in, how can I run a script when they log out?
|07:16||baiki has joined #ltsp|
|07:19||komunista has quit IRC|
|07:20||baiki has quit IRC|
|07:22||Mobe_ has joined #ltsp|
|07:24||Mobe has quit IRC|
|07:27||litlebuda has joined #ltsp|
|07:41||alkisg has joined #ltsp|
alkisg: thanks for your tip on running a script at login. how would i run one at logout?
alkisg: Error: "xexit" is not a valid command.
jimjimovich: Error: "exit" is not a valid command.
i see there's an xexit thing in the ltsp bazaar code on launchpad
There's no standard way to run scripts at logout, because e.g. xorg might crash so those scripts wouldn't be called
One ltsp dev, sbalneav, made the xexit package which tries to execute stuff at logout
Why do you want to run scripts at logout?
i need to be able to clean up some apps that don't shut down correctly, etc
For example? Can't you clean them on logon?
I guess I could, they're just sitting around taking up memory while the user is not logged in
Which ones? I'm asking because there's a difference if the app crashed or xorg crashed or even if the user unplugged the power cord of the client...
yeah, i know. the one that's bothering me right now is my own app. i probably just don't know how to launch it correctly so that it shuts down when the user logs out. it's a ruby app
but I've had problems with Evolution not shutting down right too and the process hanging around after logotu
evolution-data-server does that yeah
Normally programs are launched inside the x-session, so they're closed when it finishes
If you made your program run within the x session, it would be automatically killed
i'm launching a background ruby process when the user logs in, how could i make it run within their x session?
So anyway yeah xexit will kill those apps for you
x apps, gtk apps etc belong to the session, and e.g. gtk and qt automatically declare themselves as session clients
I don't know about console apps...
the ruby process runs as that user, so i don't quite understand why it keeps running when the user logs out (i'm not that much of a guru)
Noone tells it to close
The session only keeps track of processes that declare that belong to it
OK anyway the xexit package will close those apps for you
okay, thanks. i'll also look into making my app behave correctly so that i don't need xexit :)
If you find a solution for console apps for this, please notify me :)
|08:07||Mobe_ has quit IRC|
|08:13||litlebuda has quit IRC|
|08:17||jimjimovich has quit IRC|
|08:20||BWMerlin has joined #ltsp|
|08:26||BWMerlin has quit IRC|
|08:35||artista_frustrad has quit IRC|
|08:37||jd42 has quit IRC|
|08:39||jd42 has joined #ltsp|
|08:42||jd42 has quit IRC|
|08:48||jd42 has joined #ltsp|
|09:13||Mobe has joined #ltsp|
|10:17||m4xx has quit IRC|
|10:22||[censored] has joined #ltsp|
|10:26||MorningSon has joined #ltsp|
|10:42||Gremble has joined #ltsp|
|10:43||Gremble has quit IRC|
|11:02||[censored] is now known as m4xx|
|11:38||Kicer86 has joined #ltsp|
|11:39||vagrantc has joined #ltsp|
vagrantc, what does commit #1757 mean? (comment out RC*_WHITELIST defaults, as they are not respected properly in squeeze.)
There are a lot of useful but disabled services in thin/fat clients so I'm thinking it might be better if the RC*_WHITELISTs were disabled in Ubuntu too...
Did you notice any problems after commenting them out?
bbl, will see the irclogs
|12:09||alkisg has quit IRC|
alkisg: ah, irc logs ... well ... debian's insserv (which manages /etc/rc?.d/ symlinks) ignores the whitelisting, and the implementation of whitelisting in ltsp was pretty ugly and hackish anyways, so i just commented it out.
alkisg: didn't notice any problems, but they weren't being respected at all... might be totally different with Ubuntu's upstart or whatever manages init.
|12:27||otavio has joined #ltsp|
|12:27||otavio has joined #ltsp|
|12:29||otavio has quit IRC|
|12:29||otavio has joined #ltsp|
|12:29||otavio has joined #ltsp|
|12:41||alkisg has joined #ltsp|
|12:53||alkisg has quit IRC|
|13:13||alkisg has joined #ltsp|
The whitelisting works in Ubuntu, i.e. ltsp-build-client disables all non-whitelisted services. And that's the problem, because some services are needed...
If some services really need to be disabled (didn't see any so far), then blacklisting might be better than whitelisting, especially with localapps and fat clients
And if it could be done from an initramfs script or an initscript, it'd be even better, as now purging and re-installing a service re-enables it
But I didn't find any service that needs blacklisting so far...
the whitelisting was introduced in the frenzy to speed up boot times
but i always thought it was too heavy-handed
alkisg: but how the debian scripts work, i'm not sure there's a way to even blacklist something
vagrantc: update-rc.d doesn't work?
short of removing or modifying the scripts in /etc/init.d/
alkisg: not really
might work until the next package update
(removing the script from an initramfs script was what I thought some time ago before seeing the ltsp whitelists...)
but then insserv reorders all the rc?.d scripts
*the scripts in /etc/init.d
Or even replacing them with symlinks to a dummy script
So that the rc.d/* symlinks are not broken...
to do that for read-only NFS would eat nearly half a meg of ram
Why? Just for a dozen symlinks?
i guess could bind-mount the blacklisted ones with dummy scripts
that would be the most efficient approach
But I didn't find yet any service that needs to be disabled, so I'm guessing much less than a dozen bind-mounted symlinks will be needed...
can't bind-mount symlinks
but you can bind-mount a dummy file
Ah. OK, dummy files then
List of services that were disabled in my fat chroot:
apparmor binfmt-support bluetooth brltty cups dns-clean fancontrol kerneloops lm-sensors nbd-client networking ondemand openbsd-inetd pcmciautils pppd-dns pulseaudio rc.local rsync saned sendsigs speech-dispatcher umountfs umountnfs.sh umountroot unattended-upgrades urandom winbind wpa-ifupdown x11-common
Which of those need blacklisting? pulseaudio, unattented-upgrades...
i've heard network-manager and gdm do evil
network-manager can be used to control vpns etc
If we write an "eth0 manual" in /etc/network/interfaces, then it doesn't touch that interface
gdm doesn't do evil if ldm writes the default-display-manager in debconf and in /etc
which will get overriden on upgrades
of gdm, at least
It doesn't do that for me
ldm doesn't implement pax displayicus managerius
Let me check the code I put, I think in the fat client plugin...
echo '/usr/sbin/ldm' > "$ROOT/etc/X11/default-display-manager"
echo 'ldm shared/default-x-display-manager select ldm' | chroot "$ROOT" debconf-set-selections
Those should be part of the ldm code
When gdm was upgraded for me, ldm was kept as the default display manager
it's been years since i looked into it, so maybe it respects local changes now
And that would also solve any other *dm problems, if kdm or some else dm is installed (assuming they all read that shared/default-x-display-manager debconf setting)
they're supposed to
and ldm should as well
And reconfiguring gdm showed ldm and gdm in the debconf dialog, so afaik it worked ok...
So what I'm saying is, those services like network-manager or gdm that can "properly" be worked around, don't need to be disabled...
(btw in ubuntu those are upstart scripts so the current whitelisting doesn't remove them)
if pax displayicus managerius is any easier to implement than it used to be, we should probably do it in ldm's postinst
|14:14||dlezcano has joined #ltsp|
|14:16||Trixboxer has quit IRC|
|14:17||alexqwesa has quit IRC|
|14:18||alexqwesa has joined #ltsp|
|14:19||dlezcano has quit IRC|
|14:31||dlezcano has joined #ltsp|
|15:23||Kicer86 has quit IRC|
|15:32||alkisg has quit IRC|
|15:34||vagrantc has quit IRC|
|15:36||baiki has joined #ltsp|
|15:44||Mobe has quit IRC|
|16:02||alkisg has joined #ltsp|
|17:20||alkisg has quit IRC|
|19:07||ltspbot` has joined #ltsp|
|19:09||ltspbot has quit IRC|
|19:24||otavio has quit IRC|
|21:36||yeedl has joined #ltsp|
|22:23||yeedl has quit IRC|
|22:28||cyberorg has quit IRC|
|22:35||cyberorg has joined #ltsp|