IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 11 November 2009   (all times are UTC)

00:00
<sbalneav>
Well, I'd start by setting SCREEN_02 = shell
00:00
and checking /var/log/ldm.log on the thin client itself.
00:01
Although, changing the name of the chroot from /opt/ltsp to /opt/thinsys isn't hiding anything, since dpkg -l will show you've got the packages installed.
00:01
plus, ltsp-update-image, ltsp-update-sshkeys, etc, will still be there, etc.
00:02
<honey-badger>
the one whowould be adminstring wont have the root acesss
00:03
<sbalneav>
you don't need root to do a dpkg -l, or ls -l /usr/sbin/ltsp* :)
00:04
<honey-badger>
even the splash screen displays the path despite it being set.
00:04
I understand that. for that I am just counting on plain old luck. that the user wont see it. :)
00:05
<sbalneav>
There's a very good possibility that /opt/ltsp might be hardcoded in some places.
00:05
<honey-badger>
anyway its weird that it is such a pain in the back just to change the /opt/ltsp thing.
00:06
<sbalneav>
Why?
00:06
<honey-badger>
yeah that was my concern
00:06
<sbalneav>
If you didn't want to call it "Gnome" but instead "Elf", imaging how hard THAT would be.
00:06johnny has joined #ltsp
00:06
<honey-badger>
I mean wouldn't it be more wise/modular just to provide a DEFINE variable for where it would be installed etc..
00:07
<sbalneav>
We do.
00:07
But multiple people code on this project
00:07
one of them may have forgotton.
00:07
If you find where they've done it, please feel free to file a bug.
00:07
<honey-badger>
I went thru most of the scripts. looking for hardcoded /opt/ltsp/ path
00:08
but when it came to binaries Im all high n dry.
00:08
<sbalneav>
Did you actually build the chroot as /opt/thinsys?
00:08
or did you build it as /opt/ltsp, and then try renaming after?
00:09
<honey-badger>
/usr/bin/ltspfsd: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, stripped
00:10
no I tried building as /opt/thinsys
00:10
plain old renaming wuld be bit stupid.
00:11
<sbalneav>
lol
00:11alkisg has joined #ltsp
00:11
<honey-badger>
so. what are my options ?
00:11
<sbalneav>
I gave them to you.
00:12
enable SCREEN_02 = shell, and see why it's not logging in
00:13
<honey-badger>
in lts.conf ?
00:13
<sbalneav>
That's correct.
00:13
<honey-badger>
lemme get back to u. I hope u stick around
00:14
<cyberorg>
honey-badger, what does not work if you just rename /opt/ltsp to /opt/whatever?
00:15
<honey-badger>
cyberorg: that is the million dollar question that I am asking
00:15
<cyberorg>
client does not care where the chroot is on the server, you may have to point nfsroot path to new place
00:16
<sbalneav>
honey-badger: did you do it in dhcpd.conf as well?
00:16
in /opt/ltsp?
00:16
err
00:16
/etc/ltsp?
00:16
<cyberorg>
hi sbalneav :)
00:17
<honey-badger>
sbalneav: yeah. I did change them in /opt/ltsp as well i.e to /opt/thinsys
00:17
<sbalneav>
Hello cyberorg
00:17
<cyberorg>
honey-badger, pastebin your dhcpd.conf
00:19
<honey-badger>
one dhcpd coming up http://pastebin.ca/1666024
00:20
<alkisg>
And the clients boot fine, they're just not able to log in?
00:21
<honey-badger>
yeah. booting fine but no logins
00:21
<sbalneav>
have you checked ldm.log on the thin client yet?
00:22
<alkisg>
Then try SCREEN_02 = shell as sbalneav said, and from that local terminal, do: ssh username@server
00:22
<honey-badger>
yeah tried to cat those. but there are not ldm.logs being generated
00:22
<alkisg>
Change the "user" to some existing username, but leave "server" as it is.
00:22
<honey-badger>
the SCREEN_02 = shell crashes the ldm
00:22klausade has quit IRC
00:22
<sbalneav>
on the thin client? There should be
00:23
"crashes" the ldm?
00:23
Define, please?
00:23
<honey-badger>
http://pastebin.ca/1666036
00:23klausade has joined #ltsp
00:23
<honey-badger>
i.e no x windows prompting. just the plain old shell. (which ofcourse wont log me in)
00:24
<alkisg>
honey-badger: at that prompt, press alt+ctrl+f2
00:24
You'll see that it's already logged in as root
00:24
<sbalneav>
ok, you also need to add SCREEN_07 = ldm
00:24
then you can switch back and forth between clt-alt-f7 and ctl-alt-f2
00:25
<cyberorg>
"honey-badger> yeah. booting fine but no logins" that has nothing to do with where nfsroot is placed on the server
00:25
<sbalneav>
cyberorg: That's why I'm trying to get the ldm.log looked at
00:26
so we can see what ldm thinks is going on
00:26
<cyberorg>
honey-badger, comment #SYSLOG_HOST=192.168.0.1
00:27
<sbalneav>
cyberorg: may not work unless he's got remote syslogging turned on on his server.
00:27
<honey-badger>
commentd
00:27
<cyberorg>
sbalneav, yup, that is why remove that line, so ldm.log gets created on the client
00:28
<sbalneav>
Oh, did he have it in? I didn't notice.
00:28
been a long day
00:28
<cyberorg>
:)
00:28
<sbalneav>
just got back from the hospital with my dad.
00:31
<honey-badger>
attempting ssh session as abc
00:31
in set_message
00:31
ssh_chat: looking for ssword: from ssh
00:33
<sbalneav>
that's it?
00:33
<honey-badger>
logged in successfully eastablised ssh session
00:33
process returned no status
00:34
executing rc files.
00:35
<sbalneav>
ok, so, looks like it got logged in.
00:35
that's good
00:35
<honey-badger>
n now a blank screen with a pointer on screen 7
00:36
<sbalneav>
that what you've been getting before?
00:36
<honey-badger>
yeah
00:36
<sbalneav>
ok, so you are getting logged in.
00:36
something's just hanging
00:37
checked .xsession-errors on the users' home dir?
00:37
<honey-badger>
wat is hangings
00:37
okay
00:38
<sbalneav>
Here's my question:
00:38
do things work ok IF you just leave things at the default of /opt/ltsp?
00:38
i.e. have you tested this?
00:39
<honey-badger>
yeah it will be on pastebin
00:40
http://pastebin.ca/1666053
00:41
<sbalneav>
ok, lots of potential problems in there
00:42
but before I spend any more time debugging this, have you tested LTSP on this platform in it's default setup of /opt/ltsp?
00:43
<honey-badger>
yeah with /opt/ltsp it works but changing base dir creates prob
00:45
<sbalneav>
Well, line's 30-34 seem to be what's killing you.
00:46
have you tried setting LDM_DIRECTX = True in the lts.conf file?
00:47
<honey-badger>
yeah previously i tried that but then commented
00:49
<sbalneav>
can you:
00:49
1) :> .xsession errors in one of the users home dirs
00:49
2) enable LDM_DIRECTX
00:49
<honey-badger>
you want me to enable ldm_directx =true
00:50
<sbalneav>
3) try logging in as that user
00:50
<honey-badger>
okay
00:50
<sbalneav>
4) paste the .xsession_errors
00:54Kicer86 has joined #ltsp
00:57
<sbalneav>
honey-badger: Gonna have to do it fast, it's 1:00 AM here, and I'm gettin' tired...
00:57
<honey-badger>
okay
00:59
no errors in .xsession-errors
00:59
n one more thing i found two strange things in ldm.log
01:00
<sbalneav>
No errors?
01:00
nothing?
01:00
<honey-badger>
establishing session with 192.168.0.254
01:00
yeah
01:00
<sbalneav>
it's just empty?
01:00
<honey-badger>
yes
01:01
<sbalneav>
Your server's ip address is 192.168.0.254, yes?
01:01
<honey-badger>
i have emptied it before booting the thinclient
01:01
no
01:01
<sbalneav>
no?
01:01
<honey-badger>
my server ip address is 192.168.0.1
01:01
<Kicer86>
i guess 254 is client ;)
01:01
<honey-badger>
no client is 192.168.0.20
01:02
<sbalneav>
you haven't set a SERVER= line in your lts.conf file
01:02
<Kicer86>
then wth is 254?:>
01:02
<honey-badger>
no
01:02johnny has left #ltsp
01:02
<sbalneav>
ltsp defaults to 192.168.0.254 for the server
01:02
<honey-badger>
yeah i read it once somewhere
01:03
<sbalneav>
Maybe in our docs?
01:03
!docs
01:03
<ltspbot`>
sbalneav: "docs" is For the most current documentation, see http://wiki.ltsp.org/twiki/bin/view/Ltsp/LtspDocumentationUpstream
01:03
<honey-badger>
yeah
01:03
not so sure
01:03
<sbalneav>
ok, so, set a SERVER= value
01:03
<honey-badger>
value will take ip
01:03
i guess
01:03
<sbalneav>
yes
01:04
Has your server always had 192.168.0.1?
01:04
<honey-badger>
yes
01:04
use static ip
01:06
<sbalneav>
ok so if you set a SERVER=, does it work?
01:06
<honey-badger>
thanks buddy
01:06
it worked
01:07
<alkisg>
# check for NFS root
01:07
server=$(sed -ne '/ltsp.*nfs/ { s/^\([^:]*\):.*$/\1/; p; q }' /proc/mounts)
01:07
ltsp is hardcoded there...
01:07
file: ltsp_config
01:08
<sbalneav>
ok
01:08
alkisg: Where's that?
01:08
<honey-badger>
sbalneav: thanks alot
01:09
<sbalneav>
ah, ltsp_config
01:09
ah, so, it couldn't auto-figure out the server address
01:09
<alkisg>
Right
01:09
<sbalneav>
setting one fixed it. ok
01:09
<alkisg>
And it defaulted to .254
01:10
<sbalneav>
right, I knew we must be autodetecting something somewhere.
01:10
ok.
01:10
problems fixed, my dad's safe, i'm heading to bed.
01:10
night all
01:10
<alkisg>
G'night sbalneav
01:12
<honey-badger>
sbalneav: g'night sbalneav
01:15ogra has quit IRC
01:15foxbuntu has quit IRC
01:15um|U has quit IRC
01:16um|U has joined #ltsp
01:21alkisg1 has joined #ltsp
01:22alkisg has quit IRC
01:39johnny has joined #ltsp
01:51alkisg1 has quit IRC
02:03alkisg has joined #ltsp
02:05alkisg has quit IRC
02:07ogra has joined #ltsp
02:07foxbuntu has joined #ltsp
02:09alkisg has joined #ltsp
02:38alkisg has quit IRC
02:44ltsppbot has quit IRC
03:11evilx has quit IRC
03:20Ahmuck_ has quit IRC
03:26ltsppbot has joined #ltsp
03:30mikkel has joined #ltsp
03:32Selveste1_ has joined #ltsp
03:56Selveste1_ has quit IRC
04:11ltsppbot has quit IRC
04:52ltsppbot has joined #ltsp
04:55Sarten-X2 is now known as Sarten-X
05:00Selveste1_ has joined #ltsp
05:03hersonls has joined #ltsp
05:08johnny has left #ltsp
05:49Kicer86 has quit IRC
05:51Kicer86 has joined #ltsp
06:13hersonls has quit IRC
06:14hersonls has joined #ltsp
06:16pmatulis has joined #ltsp
06:25Sarten-X has quit IRC
06:26Sarten-X has joined #ltsp
06:35Selveste1_ has quit IRC
06:44
<vlt>
Hello. One of my LTSP clients produces high network load on x11 port 6006, in both directions. Any idea what could cause this?
07:04Selveste1_ has joined #ltsp
07:09Kicer86 has quit IRC
07:11ogra has quit IRC
07:11vvinet has quit IRC
07:11ogra has joined #ltsp
07:13honey-badger has quit IRC
07:18alkisg has joined #ltsp
07:18shawnp0wers has joined #ltsp
07:22ftherese has joined #ltsp
07:23
<ftherese>
what is the simplest way to get an nfs server running on an ltsp server?
07:23
I saw some documentation about using LDAP to authenticate
07:23
but I don't want to deal with LDAP
07:24
am I barking up the wrong tree?
07:28
<alkisg>
NFS has nothing to do with LDAP, the one is used for sharing folders, the other for authentication
07:30
<ftherese>
ok... so is there anything particular about setting up NFS for LTSP?
07:30
<alkisg>
distro? Ubuntu?
07:30
<ftherese>
yes
07:31wima1 has joined #ltsp
07:31
<alkisg>
https://help.ubuntu.com/community/UbuntuLTSP/LTSPWithoutNFS
07:32
Just curious, what's the reason for switching to NFS?
07:38
<ftherese>
I actually don't want to switch... my problem is that I am running ltsp servers with very small hard drives, and I can't have the user's home directories on them
07:38garymc has joined #ltsp
07:39Selveste1_ has quit IRC
07:39
<garymc>
anyone know how i can get .pdf files to save and reopen correctly in ubuntu LTSP?
07:39
<alkisg>
ftherese: so what are you thinking to do? use an nfs server for the home dirs? Why not put the ltsp server in that new nfs server?
07:39
garymc: .pdf files are no different with LTSP than without LTSP.
07:39
<garymc>
well when i save them they wont open up
07:40
<alkisg>
You can ask in #ubuntu
07:40
It's not an LTSP problem...
07:40
<garymc>
its not?
07:40
ok
07:42
<ftherese>
alkisg: problem is - we have a large external hard drive running off of windows that I would have used to store the home directories - via samba - but permission issues and inability to create folders as specific users has slowed me down. All I need is a way to mount a shared /home (I am running four different ltsp servers)
07:42vvinet has joined #ltsp
07:44
<ftherese>
oops... I have a problem
07:44
<alkisg>
Well if you'll be accessing this drive from all 4 LTSP servers concurrently, then yup, I guess you need NFS.
07:45
<ftherese>
I might get disconnected
07:45
<alkisg>
But I wonder if nfs servers for windows exist, and if they're reliable
07:45
<Appiah>
they do exist
07:45
but if they are stable ...
07:45
<ftherese>
that won't be necessary...
07:45
<Appiah>
well you will find out
07:45
<ftherese>
I found a 120 GB drive that I replaced one server with
07:46
so if I can just get that server set up as a nfs server
07:46bobby_C has joined #ltsp
07:46
<ftherese>
so that the other servers can mount it's /home
07:46
I should be ok
07:47
I just don't know how to set up an nfs server, and I didn't know if there were any particularities or recommendations for LTSP env.
07:47
<ogra>
install the right package and edit /etc/exports
07:47
<alkisg>
ftherese: anyway, using NFS homes is a different subject from using NFS with LTSP
07:47
<garymc>
im getting NO hel pin Ubuntu
07:48
<alkisg>
That link I gave you was for changing the clients to *boot* with NFS instead of nbd.
07:49
garymc: well, you could try the Ubuntu forums, or some other means of getting help... It's an open community, when we get someone to help us we're lucky :)
07:51isojussi has joined #ltsp
07:51
<isojussi>
is it possible to change ldm login screen language in ubuntu 9.10?
07:52
<alkisg>
isojussi: sure. Is ldm translated in your language?
07:52
(the package, I mean)
07:52
<isojussi>
finnish
07:52
?
07:52
<alkisg>
lets see the sources...
07:53
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ldm-trunk/annotate/head%3A/po/fi.po
07:53
<ftherese>
brb
07:53ftherese has left #ltsp
07:54
<alkisg>
Looks semi-translated. Just install language-pack-fi in the chroot.
07:54
...and rebuild the image
07:54
<isojussi>
ok
07:57Kicer86 has joined #ltsp
08:00Gadi has joined #ltsp
08:02
<wima1>
is there somewhere a description on how pulseaudio is set up in ltsp?
08:02
like, how is the daemon started
08:02
how do apps know where the sound goes
08:02
stuff ike that
08:02
<Gadi>
wima1: look in /opt/ltsp/i386/usr/share/ltsp/ltsp-init-common
08:03
wima1: and apps no where to go with an environment variable
08:03
set on login
08:03
PULSE_SERVER
08:03isojussi has quit IRC
08:03
<wima1>
ah
08:04
cause we are seeing lots of problems since the upgrade to ubuntu 9.04
08:04
pulsed dies on the clients
08:04
and i hae no idea how to debug this
08:04
<Gadi>
wima1: I believe there is a pulseaudio bug with certain intel audio chipsets or something
08:06
best way to debug would probably be to launch pulseaudio manually on a shell session on the thin client and make it die and see the console errors
08:06
or, alternatively, edit the ltsp-init-common call to pipe stderr to a /tmp file on the client and look inside it when you make it die
08:07
<wima1>
i make it log to the server now, but it doesn't tell me a lot
08:07
<Gadi>
well, it wont
08:07
<wima1>
is there a way to increase logging?
08:07
<Gadi>
pulseaudio logs to stderr
08:07
not syslog
08:07
afaik
08:07
<wima1>
ah
08:07
ok
08:07
i'll look into that
08:07
thanks
08:08
<Gadi>
no problem - let us know what you find - I know others have come in with a similar problem
08:08Selveste1_ has joined #ltsp
08:10
<wima1>
BTW, i just saw the clients have a VIA 8237, not an intel
08:11
<kdegel_>
So what have people been doing with VIA chipsets + DVI in the lts.conf? I tried what ltsp.org suggested and I am able to get the monitor to turn on, just not showing anything
08:11kdegel_ is now known as kdegel
08:12
<ogra>
Gadi, https://lists.ubuntu.com/archives/jaunty-changes/2009-November/009927.html ...
08:12
not sure, but that probably might help some here for which PA committed suicide after a few mins
08:13Selveste1__ has joined #ltsp
08:13
<wima1>
kdegel: we use the analog output on all our clients, sorry
08:13
<Gadi>
kdegel: use via's proprietary driver
08:14
instead of openchrome
08:14
<kdegel>
Gadi: thanks, I will see how to do that
08:15* Gadi apologizes for the blatant heretical anti-opensource community solution
08:15
<Gadi>
:)
08:15
<kdegel>
oh wait, is that just by using XSERVER = via ?
08:15
<Gadi>
but, theoretically, via's been working with the opensource community more and more
08:15
no
08:16
you need to download the binary
08:16
from via's site
08:16
<kdegel>
and install it on ubuntu or inside chroot?
08:16
<Gadi>
modify the install script so that it doesnt use uname -r for the kernel
08:16
and install it in the chroot
08:16
it takes a little monkeying
08:17
but it should work in the end
08:17
<kdegel>
hmmm...maybe it would be easier to keep the dvi-vga adapters and somehow just force the resolution to be higher
08:17
its strange, with the adapter, then the display shows the desktop, but only at 800x600
08:18
<Gadi>
kdegel: your Xorg log file will guide you along the way
08:18
thats not strange
08:18
<kdegel>
oh, I thought it was :(
08:18
<Gadi>
nah - it prolly has no DDC
08:18
<kdegel>
like 'you work with an adapter? but not straight dvi cable?' haha I guess I don't know enough of how LTSP works
08:19
<Gadi>
set the X_HORZSYNC and X_VERTREFRESH
08:19mikkel has quit IRC
08:19
<Gadi>
its not LTSP
08:19
its X
08:19
<kdegel>
I tried that, that is how I was able to get the monitors to come on
08:19
just not showing anything
08:19
yes, I meant xorg, not ltsp, sorry, reading while typing
08:19
<Gadi>
well, you need to use your Xorg logs to know whats going on
08:20
but, many times adapters screw with things
08:20
KVM switches, too
08:20
<kdegel>
yes :( we have found this out
08:20
<Gadi>
they are mostly passive devices
08:20mikkel has joined #ltsp
08:20
<Gadi>
and not always bidirectional
08:20
<kdegel>
are people successful in getting the adapters to show the correct resolution?
08:21
<Gadi>
I have adapters with some intel chipsets
08:21
<kdegel>
and you have been successful?
08:21
<Gadi>
sometimes they do screwy things and you need to specify what you want
08:21
but, yeah
08:21
there is nothing about the adapter that makes things not work
08:21
oh, wait
08:21
of course, your output needs to be DVI-I
08:21
and not DVI-D
08:22
are you sure you have a DVI-I output?
08:22
DVI-D only outputs digital signals, so a simple adapter for analog wont work
08:22
there are no analog signals to begin with
08:22
:)
08:23
<kdegel>
well the adapter way of hooking it up, is the way that we can get it to work at 800x600
08:23
dvi - vga
08:23
<Gadi>
ah, ok
08:23
<kdegel>
so I guess they are DVI-I
08:23
<Gadi>
then it must be DVI-I
08:23
<kdegel>
and that is the way most of our stores are, I was just thinking that we could just get rid of those and utilize
08:23
DVI-DVI
08:23
<Gadi>
does your driver support Xrandr?
08:24
<kdegel>
but I think it might be easier to get these with the adapters to just force 1024x768
08:24scottmaccal has joined #ltsp
08:24
<kdegel>
Gadi: I'm not sure, I will do some searching and see if I can find any info
08:24
<sbalneav>
Gadi: You pinged
08:25
<Gadi>
ok - well, the #1 best resource is your xorg log file on the client
08:25
it will tell you more than everything you wanted to know
08:25Selveste1_ has quit IRC
08:25
<Gadi>
sbalneav: yeah - first, hows ur dad?
08:25garymc has quit IRC
08:25
<kdegel>
Gadi: so just oging to the client and viewing the xorg in /var/log/ will be local to the thin client?
08:26
<scottmaccal>
Morning all.
08:26
<Gadi>
kdegel: from a shell
08:26
or from an ltsp-localapps xterm
08:26
but, yeah - you want the one on the thin client
08:27
<kdegel>
ok, its kind of hard to understand which logs from where to view with LTSP because so much is shared
08:27
<Gadi>
kdegel: yeah - just ask yourself: where does the Xserver run?
08:27
wherever the server runs is where the log will be
08:27dro has joined #ltsp
08:28
<kdegel>
yeah
08:29
<sbalneav>
Pneumonia
08:30
<Gadi>
that sucks
08:30
<sbalneav>
It was touch and go for a bit
08:30
he's 79
08:30
<Gadi>
does past tense mean ur out of the woods?
08:30
<sbalneav>
a complete diabetic and a polio survivor
08:30
yeah
08:30
<Gadi>
\o/
08:30
<kdegel>
jeesh
08:31
<sbalneav>
they got the fever down, gave him some of the GOOD antibiotics, and sent him home to recuperate.
08:31
We were only at the hospital for about 8 hours.
08:34
<Gadi>
sbalneav: thats either a sign of good health or socialized medicine -> glad to hear it sounds like the former ;)
08:34scottmaccal has quit IRC
08:34
<sbalneav>
both, actually
08:34* Gadi was going to bug you with a C question, but I cheated with a system call in the end
08:34
<Gadi>
:)
08:35
<sbalneav>
we jumped right to the front of the line, got a private strecher bay in emerg, whole thing.
08:36
will all the H1N1 going around, unless you're actually hemorraging, they want to get you out quick, so you don't get any sicker.
08:36
so once they diagnosed it, we were given the cure, and sent off.
08:39scottmaccal has joined #ltsp
08:41* scottmaccal is not happy that he is being forced to use non-free software to produce what his class needs and worse, take the time to get it to work the way it should
08:41
<kdegel>
Gadi: I think I am misunderstanding something
08:42
<sbalneav>
which softwar?
08:42
<scottmaccal>
Visio
08:42
<kdegel>
to be clear, I should be able to go to the thin client, pull up a terminal, and view /var/log/Xorg.o.log (or whatever its called) and see my issue?
08:43
<Gadi>
kdegel: not exactly
08:43
<scottmaccal>
I am taking a class that involves a lot of flow charts and such.
08:43mikkel has quit IRC
08:44
<Gadi>
you need to either have a shell session on the thin client (eg. SCREEN_07=ldm SCREEN_02=shell) and switch to the shell to view the log
08:44
<kdegel>
yeah I thought I was doing somethingwrong
08:44
<Gadi>
OR you need to open a terminal window
08:44
and type:: ltsp-localapps xterm
08:44
<kdegel>
from the thin client, right?
08:44
<Gadi>
that should bring up an xterm window running on the thin client
08:44
<kdegel>
let me try this
08:44
<Gadi>
right
08:44
and in the xterm window, you can look at the log
08:45bieb has joined #ltsp
08:45* Gadi thinks he just made a samsung netbook start to smoke with the audio volume set too high
08:46* Gadi shakes his head at poor hardware design
08:46
<kdegel>
ok ltsp-localapps doesn't seem to be a valid command
08:46mikkel has joined #ltsp
08:51RK has quit IRC
08:53
<zamba>
i have a problem with my TC
08:53
opening a few tabs in firefox nearly renders the computer useless
08:53
especially if it's an online newspaper with some ads and flash
08:58
<alkisg>
!flash
08:58
<ltspbot`>
alkisg: "flash" is Yes, flash sucks. Make sure you have LDM_DIRECTX=True in your lts.conf file, or if it's just youtube you're after, try the HQtube plugin. Install greasemonkey for firefox, and see http://userscripts.org/scripts/show/24999
08:59
<zamba>
i have LDM_DIRECTX=True
08:59
and it still - frankly - sucks
08:59Selveste1___ has joined #ltsp
09:00Selveste1__ has quit IRC
09:02
<wima1>
i'm trying to update pulse on the clients to version 0.9.15
09:03mikkel has quit IRC
09:03
<wima1>
however, the post install script fails
09:03
it want's to restart pulsed
09:04
<Gadi>
wima1: try: export LTSP_HANDLE_DAEMONS=False
09:04
<wima1>
is there a way to install a package and skipping the post-install script?
09:04
<Gadi>
and install it
09:04
<wima1>
gadi: same result.
09:05
initscript pulseaudio, action "stop" failed.
09:05
<Gadi>
wima1: ok, so: mount -t proc proc /proc
09:05
and install it
09:05
then stop the daemon
09:06
and umount /proc
09:06
<wima1>
ah. that did it
09:06
thanks
09:08
i hope this solves the audio problems.
09:09
<kdegel>
Gadi: could you point me to the right link as to force a resolution out of a thin client?
09:09
I just want one resolution, forced
09:10
<Gadi>
kdegel: what distro are you on again?
09:11CAN-o-SPAM has joined #ltsp
09:14
<kdegel>
Gadi: I have a 8.04 and a 9.10 (ubuntu) server in my testing lab
09:14
<Gadi>
well, on the 9.10, you can do:
09:14
XRANDR_DISABLE=True
09:14
X_MODE_0=1024x768
09:14
<kdegel>
oh, thta doesn't work on 8.04?
09:14
<Gadi>
(I am making the assumption that the driver doesnt handle xrandr properly)
09:15
on 8.04, substitute XRANDR_DISABLE=True with CONFIGURE_X=True
09:15
iirc
09:15
<kdegel>
ahh, that explains it :)
09:15
<Gadi>
there were some changes in the way certain things were handled
09:16
<kdegel>
so just create a lts.conf file and put the [Default] above it and that should be good?
09:16
<Gadi>
right
09:16
you may also need the X_HORZSYNC and X_VERTREFRESH
09:20
<kdegel>
I might because that didn't work
09:20
still has 2 options, 800x600 and 600x480 or whatever it is
09:25Brian_H has joined #ltsp
09:26mikkel has joined #ltsp
09:26mikkel_ has joined #ltsp
09:27dro has quit IRC
09:29
<kdegel>
Gadi: so you are able to get higher resolutions with a dvi-vga adapter by just doing what you mentioned?
09:30
<Gadi>
kdegel: again, this has nothing to do with the adapter per-se
09:30
<kdegel>
oh
09:30
<Gadi>
it has everything to do with what modes your monitor will accept
09:30
and what modes you tell the driver to present
09:30
the adapter is merely a passthorough
09:31
and the only problem that it may introduce is to make the driver unable to autodetect the right modes
09:31
but, it should not limit your ability to force the right modes
09:31
<kdegel>
well I can put the monitor on another thin client with a vga hookup and all resolutions are available, so I guess its because the thin client can't detect which monitor it has because of the adapter?
09:31
<Gadi>
if you get a shell on the thin client
09:31
and scp /var/log/Xorg*log to the server
09:32
and pastebot it
09:32
I can help tell you what it means
09:32
<kdegel>
ok, let me try that again
09:32
<Gadi>
is the other thin client the same VIA chipset using the same driver?
09:32
if not, you cannot draw that conclusion
09:33
<kdegel>
I have 2 thin clients, one is a neoware with a vga output, the other is a wyse with a dvi output, we have vga monitors
09:33
<Gadi>
right
09:33
so, all you can conclude is that the driver you are using on the DVI one with the adapter is unable to collect the supported modes of the monitor
09:34
and therefore, falling back on default modes
09:34
<kdegel>
the command you told me to type before, ltsp-localapps isn't a default command
09:34
<Gadi>
that fit the default sync frequencies for that driver
09:34
in which distro?
09:34
<kdegel>
8.04
09:34
<Gadi>
8.04 predates localapps
09:34
<kdegel>
ahh
09:34
<Gadi>
so, you're right
09:35
you have to set SCREEN_07=ldm, SCREEN_02=shell
09:35
boot the client
09:35
<kdegel>
ok, should I just boot up the 9.10 distro? might make things easier?
09:35
<Gadi>
and ctrl-alt-f2
09:35
yeah, it would
09:35
<kdegel>
ok, give me a few minutes
09:35
<Gadi>
of course, you will also have a different driver for that card
09:35
:)
09:36
<kdegel>
well we are going with 9.10, I just have a 8.04 to be able to figure out the bugs because of distro changes or other changes
09:36
<ltsppbot>
"alkisg" pasted "proposed lts.conf for kdegel" (6 lines) at http://pastebot.ltsp.org/1
09:36
<Gadi>
if you are going with 9.10, do all your troubleshooting on 9.10
09:36
because the via driver in 9.10 is probably light-years ahead of the one in 8.04
09:37
back in April, 2008, DVI thin clients were not as common as today
09:37
keep that in mind
09:37
<ogra>
yeah, 8.04 is ancient :)
09:37
<kdegel>
yeah we are just having minor buggy issues with 9.10, which is why, when this dvi issue came up, I threw up a 8.04 box, just ot make sure it wsn't a bug with 9.10
09:38
:( I like 8.04
09:38
<ogra>
10.04 will be better ;)
09:38
<kdegel>
I know :)
09:38
<Gadi>
you sound like the Windows guy on the MAC commercial ;)
09:38
<kdegel>
it might be when I can finally switch to ubuntu as a desktop :)
09:39
although, I have been hoping this for some time :(
09:39dro has joined #ltsp
09:39
<Appiah>
well kdegel this year is the year of the linux desktop
09:39
:D
09:40
<alkisg>
We'll even be able to type Greek in flash sites :D
09:40
<ogra>
now thats what i want !
09:44scottmaccal has quit IRC
09:45rjune has joined #ltsp
09:45Kicer86 has quit IRC
09:45Brian_H has quit IRC
09:45
<kdegel>
Gadi: thta ltsppbot thing, should that be in lts.conf? I am asuming yes
09:46
<Gadi>
kdegel: actually, no
09:46
if you are using 9.10 now
09:46
simply do:
09:47johnny has joined #ltsp
09:47
<Gadi>
[default]
09:47
XRANDR_DISABLE=True
09:47
X_MODE_0=1024x768
09:47
X_HORZSYNC=30.0-88.0
09:47
<kdegel>
ok
09:47
<Gadi>
X_VERTREFRESH=50.0-85.0
09:47
like that
09:47
<kdegel>
oh wait, you are saying no?
09:47
<Gadi>
in lts.conf
09:48
<kdegel>
ok
09:48
<Gadi>
if XRANDR were working, you would use: XRANDR_MODE_0 = 1024x768
09:48
to force the mode
09:48
and you would not have XRANDR_DISABLE=True
09:48
<kdegel>
maybe I should try that first?
09:48Kicer86 has joined #ltsp
09:48
<Gadi>
sure
09:49
but, if that worked, it would appear as a choice in screeen resolution in the gnome session
09:49
which, it sounds like it didnt
09:49
<kdegel>
I have the xorg.log file, would you like it?
09:49
<Gadi>
unless that was because you did not have the sync frequencies in there
09:49
sure, pastebot it
09:49
!pastebot
09:49
<ltspbot`>
Gadi: "pastebot" is The LTSP pastebot is at http://pastebot.ltsp.org. Please paste all text longer than a line or two to the pastebot, as it helps to reduce traffic in the channel. A link to the content will be pasted in the channel.
09:50
<kdegel>
yeah I was going to pastebin it, but either way
09:52
<ltsppbot>
"kdegel" pasted "xorg.7.log" (864 lines) at http://pastebot.ltsp.org/2
09:53
<Gadi>
(II) CHROME(0): <default monitor>: Using default hsync range of 31.50-37.90 kHz (II) CHROME(0): <default monitor>: Using default vrefresh range of 50.00-70.00 Hz
09:53
did you see those two lines?
09:53
it is falling back on default ranges
09:53
with such narrow ranges, the only available modes are the 800x600 and 640x480
09:54
that tells you that it cannot get the ranges from the monitor
09:54
and you absolutely NEED X_HORZSYNC and X_VERTREFRESH
09:54
you most likely do not need to force the mode at all
09:55
as long as you set wider sync ranges, which will include more available valid modes
09:55
make sense?
09:55
(II) CHROME(0): Not using default mode "1024x768" (hsync out of range)
09:55
<kdegel>
crap I was jut looking at something on ltsp.org that mentioned to place lts.conf in /opt/ltsp/i386/etc/ and I have been putting it in /var/lib/tftpboot/ltsp/i386/
09:56
<Gadi>
like that - it rejects 1024x768 because the horizontal sync is too small
09:56
<kdegel>
the new way is to put it in the later right?
09:56
<ogra>
since several years, yes
09:56
<kdegel>
yeah ok,
09:56
<Gadi>
put it in: /var/lib/tftpboot/ltsp/i386/lts.conf
09:56
<kdegel>
Gadi: I'm looking at the code now
09:57
ahh yeah Gadi I see what you are saying
09:57Kicer86 has quit IRC
09:57
<kdegel>
code/log*
10:02
Gadi: this is kind of funny
10:02artista_frustrad has quit IRC
10:02
<kdegel>
so that worked, but its like the monitor doesn't know that its getting the signal, yet its displaying it
10:03alkisg1 has joined #ltsp
10:03Kicer86 has joined #ltsp
10:03artista_frustrad has joined #ltsp
10:03
<kdegel>
the resolution is at 1024x786 and has other options, but the monitor has its 'monitor out of range' dialog going across the monitor
10:04
the default of lenovo/ibm monitor window that pops up if the signal is out of range
10:04
its kind of funny, I might take a picture
10:05
<alkisg1>
you may want to lower X_VERTREFRESH to 75 or even less
10:05
<kdegel>
I'm going to find the exact numbers from lenovo and see if that helps
10:06
<Gadi>
yeah - some monitors will do that
10:06
<kdegel>
I've never seen that before
10:07
<Gadi>
usually decreasing the refresh rate, as alkisg suggests resolves it
10:07
<kdegel>
I just started laughing, I guess I have had too much coffee :)
10:07
<Gadi>
if its an LCD, just bump the top end of the range to either 75 or 65
10:08
what you are seeing is the disconnect between hardware and firmware in the monitor
10:08
:)
10:08
<kdegel>
well thats kind of the thing, this will be put in places with lcd and crt's
10:08
<Gadi>
the firmware says "if Im being driven more than what I am spec'd for, display a message"
10:08
the hardware says, "yeah, I can do that"
10:10Selveste1___ has quit IRC
10:12alkisg has quit IRC
10:14wima1 has quit IRC
10:17
<kdegel>
Gadi: looks like this is going to work, maybe it will be a good reason to force us to just throw away all crt's ;)
10:17
or just deal with 75hrz
10:17
M*
10:23dro has quit IRC
10:23Ahmuck-Jr has joined #ltsp
10:27dro has joined #ltsp
10:28ltspbot has joined #ltsp
10:28sbalneav has joined #ltsp
10:28wima has joined #ltsp
10:31alkisg1 has quit IRC
10:41
<rjune>
!g
10:41
<ltspbot>
rjune: "g" is Gadi!!!!!!!!!!!!!!!!!!!!!!!!
10:43Kicer86 has quit IRC
10:49otavio has quit IRC
10:50spectra has joined #ltsp
10:54tstafford has joined #ltsp
10:57staffencasa has joined #ltsp
10:57
<Ahmuck-Jr>
with ltsp, one needs to chroot to update the ltsp client?
10:58
ie, aptitude in chroot?
10:59
<johnny>
yes..
10:59
actuallly.. you don't..
10:59
you can tell apt to use a different root
10:59
i just don't know the switch
11:03wima has quit IRC
11:11coordinador has joined #ltsp
11:12
<coordinador>
hi, i have a urgent problem, i have many /lib/gnome/mixer_applet2 process running in many users and the process uses 100% of cpu!
11:13
and everything is very very slow, this happened suddenly
11:13otavio has joined #ltsp
11:13
<coordinador>
*/lib/gnome-applets/mixer_applet2
11:14artista-frustrad has joined #ltsp
11:14artista_frustrad has quit IRC
11:16dro has quit IRC
11:25
<Gadi>
coordinador: remove the mixer applets?
11:26Selveste1___ has joined #ltsp
11:27
<coordinador>
Gadi, ill do that, is this a bug?
11:27
im using ubuntu 9.04
11:27* Gadi has no clue
11:28
<coordinador>
i will kill all mixer applets
11:29
<Gadi>
you can probably remove them from the default session using sudo gconf-editor
11:29
and drilling down to apps/panel
11:29
or some such
11:29
<coordinador>
i killed it all and it works :)
11:30
<Gadi>
well, until they log in again
11:30
;)
11:31dro has joined #ltsp
11:33
<coordinador>
:o
11:34
Gadi, do you know how to edit the new grub menu?
11:34
since there is no menu.lst
11:40
<dro>
coordinador: can't you modify it when the system first boots, can change things before it boots into the os
11:40
coordinador: at the grub menu
11:42
<coordinador>
ok, ill reboot
11:42coordinador has quit IRC
11:44
<kdegel>
Gadi: have you ever had nan issue where the thin clients that were using a dvi-vga adapter ended up failing over to the 800x600 resolution?
11:47
<Gadi>
failing over?
11:47
if you set a screen resolution in your gnome desktop, it will use that after you log in
11:47
<kdegel>
default
11:47
<Gadi>
instead of the one from lts.conf
11:47
if thats what you mean
11:47
<kdegel>
well of course, but I don't have the options of going any higher anymore
11:47
<Gadi>
oh
11:48
did something happen to your lts.conf?
11:49
<kdegel>
I was messing with the lts.conf file, trying to see what Hz I could put the LCD's at (figuring I could just go with 60) and then the thin clients went back to the 800x600 resolution and I was unable to change it. I then put the lts.conf file back to how it was originally when it was working, and the thin clients still booted up to 800x600 with no option to change
11:51
<Gadi>
kdegel: make sure you dont have a syntax error in the lts.conf file
11:51
if you do, the whole file is not read
11:51
and it will be as if you have no file
11:53
you can probably check your syntax with: /opt/ltsp/i386/usr/sbin/getltscfg -a -c /var/lib/tftpboot/ltsp/i386/lts.conf
11:53
tho, I have never done it that way
11:53
:)
11:56
<kdegel>
Gadi: baaahh!!! user-error PEKAC
11:57
for some reason the [ wasn't infront of Default anymore
11:57
sorry to bother you, I know I have taken up a lot of your time :)
11:57
<Gadi>
not at all
11:57* Gadi can multitask
12:00sebas891 has joined #ltsp
12:11Lns has joined #ltsp
12:11otavio has quit IRC
12:14
<kdegel>
Gadi: well thats good, because I have been googling for another thing that I am curious about. How can you disable the 'preferences' button on the login screen so a user can't choose what session to log in?
12:20
<sebas891>
hi folks, A question, is it possible to assign an hostname to a terminal client? (ubuntu 9.04)
12:21
I set one in the dhcp server, but it has no effect. it still shows ltsp190 as the hostname of the client.
12:21Brian_H has joined #ltsp
12:21Egyptian[Home]1 has quit IRC
12:22
<johnny>
setting on the dhcp server should work..
12:22
sebas891, that's why i use dnsmasq tho..
12:22
does the dhcp and dnsmasq
12:23
<sebas891>
the client should take the name that comes from the dhcp server. ok.
12:23
I use pfsense as a dhcp server.
12:23Egyptian[Home] has joined #ltsp
12:24
<sebas891>
when, I do local install of linux, it uses the name from the dhcp server.
12:27davidj has joined #ltsp
12:31otavio has joined #ltsp
12:46dro has quit IRC
12:48dro has joined #ltsp
12:51
<johnny>
i wonder if you have to adjust the chroot dhcp client config
12:53
sebas891, in the chroot i see send host-name "<hostname>";
12:53
looks like we tell the dhcp server ours.. instead of using the one we get
12:53
even though we request the one from the server
12:53
<sebas891>
ah!
12:54
so it's the other way around.
12:55
johnny: in which file, do you see that ?
12:56
<johnny>
/etc/opt/ltsp/etc/dhcp3/dhclient.conf
13:01
<sebas891>
send host-name "<hostname>";
13:01
request subnet-mask, broadcast-address, time-offset, routers,
13:01
domain-name, domain-name-servers, domain-search, host-name,
13:02
maybe, we can just comment out the line. send host-name "<hostname>";
13:02
<johnny>
give it a shot.. and rebuild it
13:03
<sebas891>
:) l'll try that.
13:03
<johnny>
there were some terrible problems back in the day when i used gentoo and accepted the server provided hostname
13:03
the default gentoo dhcp config would take the hostname
13:03
<sebas891>
soon.
13:03vvinet has quit IRC
13:03
<johnny>
so if you connected via networkmanager
13:04
or anything really
13:04
but after being logged into X
13:04
it would change your hostname, and then no X apps would work anymore
13:04
it was suck
13:04
<sebas891>
in deed.
13:04
<johnny>
sebas891, so that functionality (to accept hostnames) is not good for average users
13:05rjune has quit IRC
13:08dro has quit IRC
13:08artista-frustrad has quit IRC
13:08johnny has quit IRC
13:08ogra has quit IRC
13:08ltsppbot has quit IRC
13:08um|U has quit IRC
13:08japerry has quit IRC
13:08FGXR6 has quit IRC
13:08ltsplogbot has quit IRC
13:08jbrett has quit IRC
13:08zamba has quit IRC
13:08dberkholz has quit IRC
13:08Wastrel_ has quit IRC
13:08dmarkey has quit IRC
13:08kusznir has quit IRC
13:08brendan0powers has quit IRC
13:08kas has quit IRC
13:08lejo has quit IRC
13:08mushroomblue has quit IRC
13:08sepski has quit IRC
13:08vlt has quit IRC
13:08tarzeau has quit IRC
13:08Appiah has quit IRC
13:08_UsUrPeR_ has quit IRC
13:09alkisg has joined #ltsp
13:09Ahmuck-Jr has quit IRC
13:10DawnLight has joined #ltsp
13:13tstafford has quit IRC
13:19vvinet has joined #ltsp
13:21korcan has quit IRC
13:38Gadi has left #ltsp
13:44rjune has joined #ltsp
13:46
<DawnLight>
hey, i've some problem with an rcfile not running
13:46
i don't get it
13:47
the file seems ok because it runs by itself ok
13:47
i mean when i run it manually
13:47sepski has joined #ltsp
13:47tarzeau has joined #ltsp
13:47Appiah has joined #ltsp
13:47vlt has joined #ltsp
13:47_UsUrPeR_ has joined #ltsp
13:47kas has joined #ltsp
13:47lejo has joined #ltsp
13:47mushroomblue has joined #ltsp
13:48dro has joined #ltsp
13:48artista-frustrad has joined #ltsp
13:48johnny has joined #ltsp
13:48ogra has joined #ltsp
13:48ltsppbot has joined #ltsp
13:48um|U has joined #ltsp
13:48japerry has joined #ltsp
13:48FGXR6 has joined #ltsp
13:48kusznir has joined #ltsp
13:48zamba has joined #ltsp
13:48Wastrel_ has joined #ltsp
13:48ltsplogbot has joined #ltsp
13:48jbrett has joined #ltsp
13:48dberkholz has joined #ltsp
13:48dmarkey has joined #ltsp
13:48brendan0powers has joined #ltsp
13:48
<DawnLight>
hello
13:48
<alkisg>
Hi
13:49
<DawnLight>
i've some trouble running an rcfile
13:50
i've defined it in lts.conf and put it in the chroot's /etc/init.d
13:50
made it executable
13:50
need i define the file with a path?
13:50
in lts.conf, that is
13:51
<johnny>
yes
13:51
<DawnLight>
aha
13:52
that explains it
13:52
thanks. i'll try now
13:53
<alkisg>
Docs: http://www.ltsp.org/~sbalneav/LTSPManual.html#modules-scripts
13:54Gadi has joined #ltsp
13:54
<sebas891>
johnny: no luck, I edited the dhclient.conf commenting out the line send host-name "<hostname>";
13:54benGREEN has quit IRC
13:54stgraber has quit IRC
13:54Kevin` has quit IRC
13:54Kevin`_ has joined #ltsp
13:54stgraber_ has joined #ltsp
13:54benGREEN has joined #ltsp
13:55
<sebas891>
I see this file etc/dhcp3/dhclient-enter-hooks.d/debug saying.
13:56
All these scripts
13:56
# are called from /etc/dhcp3/dhclient-script,
13:56
but the dhclient-script is not there...
13:57
<johnny>
get a non ltsp setup working first i guess
13:57
<sebas891>
that is working for me a non ltsp.
13:58
<johnny>
ah.. i wonder if it has to do with what happens before we get itno the chroot then
14:00
<sebas891>
do you have some pointers for me? :)
14:06bobbyC has joined #ltsp
14:07
<johnny>
not at the moment, i have to do other work for now
14:07
alkisg, perhaps you know
14:07* alkisg looks at the logs...
14:08bobby_C has quit IRC
14:09
<alkisg>
sebas891: can you upload your dhcpd.conf?
14:16
sebas891: I'm not sure if you can send a hostname from dhcpd.conf in Jaunty, maybe not. I'm sure you *can* send a hostname from pxelinux.cfg/01-mac-address. And, you could also patch the init scripts a little to send the hostname. Finally, I think we fixed it in Karmic...
14:17
<sebas891>
alkisg: hum, I use pfsense, which has a web interface for the management of hostname and assign.
14:17
<alkisg>
*patch the init scripts to *accept* the hostname
14:19
<sebas891>
Isn't it better to accept the hostname from the dhcp server? (in theory)
14:20
<alkisg>
Sure, you can patch the scripts to support that
14:20
I don't know why it wasn't supported from the beginning
14:21
I think we fixed it at summer, so if you put stgraber's ppa in your sources, you should get an updated version for jaunty that supports that
14:23
The file that does this is /opt/ltsp/i386/usr/share/initramfs-tools/scripts/nfs-bottom/ltsp
14:23
You can just get the last version of this file from launchpad...
14:24Sarten-X has quit IRC
14:24
<dro>
alkisg: that is cool, specific hostnames per mac address?
14:24
<alkisg>
Yeah some person requested that, and vagrantc accepted the patch
14:25
I don't see where that could be useful, though
14:25
<dro>
I have 20+ spare units just sitting around. if their client dies, I just swap it out lol
14:25
someone was bored
14:25
<alkisg>
Your dns server won't be aware of these hostnames....
14:25* alkisg offered the ip-based patch :)
14:26
<dro>
no reason to know hostnames or ip's of the thin clients
14:26
<alkisg>
Why not?
14:26
<dro>
no port forwarding or anything like that
14:26
<alkisg>
How can you open remotely the clients with WOL if you don't know their mac address?
14:26
<dro>
yea i guess it could help ppl
14:26
lol that makes sense
14:26
lol
14:26
<johnny>
alkisg, it can be aware
14:26
you send the hostname
14:27
and your dhcp server can update dns
14:27
so you don't have to come up with clever names for all of em :)
14:27
<alkisg>
johnny: not with that patch.. it doesn't send dynamic dns updates
14:27
<johnny>
no
14:27
not on it's own
14:27
but i used that in gentoo too
14:27
so i know which client i was working on in vbox :)
14:28
<alkisg>
Speaking of which, has anyone been able to get bind (or dnsmasq) to accept the dns updates that the windows clients send?
14:28
<DawnLight>
ltsp is irrigating my sprouts
14:29
<dro>
i think the trick in that is allowing a specific user to update the dns records on the windows server
14:29
and that user, has to be the same login that you use on linux
14:29vvinet has quit IRC
14:29
<dro>
and then you allow for unsecured updates or some bs on the windows side
14:30
<alkisg>
dro: "on the windows server" ==> do you mean with the windows dns server? Can't bind be used?
14:30
(I'd like to have a linux server and both linux & windows clients, but no windows server)
14:31stgraber_ is now known as stgraber
14:32
<alkisg>
Hi stgraber! Do you think making 11100 the default italc port for Lucid would be a good idea? /me would like to make a patch about that...
14:33
<DawnLight>
at least i'm trying to make it do that
14:33bobbyC has quit IRC
14:33
<dro>
alkisg: i think bind can run on windows, but I don't use it
14:33
<stgraber>
I'm pretty sure quite a few public docs say it's 5800 and 5900, so I'd go with 11100 only if the standard port is already taken
14:33bobbyC has joined #ltsp
14:34Sarten-X has joined #ltsp
14:34spectra has quit IRC
14:34
<stgraber>
mainly because 5800 and 5900 are registered ports where 11000+ aren't supposed to be used by VNC
14:34
<dro>
stgraber: yea 5800 and 5900 are usually vnc
14:34
<alkisg>
stgraber: the problem is, when ica launches, it can't know if e.g. vino will start right after that
14:34
Both are run from /etc/xdg, so italc may start first
14:35
Then vino will conflict, and the user will see 100% xorg usage without being able to pinpoint the problem
14:35
<stgraber>
has somebody reported that bug against vino ?
14:35
<alkisg>
Sure, we could send a patch for vino, but... yeah
14:35
They seem to go to the opposite direction
14:36
I.e. they had a GUI option to change the port, and they *removed* it
14:36
and really, italc isn't vnc compatible, so it shouldn't take up the VNC ports
14:36
italc 2.0 *will* use 11100.
14:36
<stgraber>
italc is perfectly VNC compatible, it's just usin vnc over SSL
14:37
<alkisg>
Can you use vinagre with ica?
14:37
Or italc with vino?
14:37
<DawnLight>
yo, i'm really trying to make my ltsp client irrigate my sprouts and i'm struggling with the scripts to do that
14:37
<stgraber>
nope because vinagre doesn't support VNC over ssl
14:37
<sebas891>
alkisg: /usr/share/initramfs-tools/scripts/nfs-bottom/ltsp, in deed I see the hack to build the hostname.
14:37
<DawnLight>
i don't really know bash
14:37
<alkisg>
sebas891: http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/files
14:38
<stgraber>
yes, you can use italc to control vino
14:38
<alkisg>
stgraber: so is the italc ssl implementation a "standard" one? I don't think it can cooperate with any standard vnc client...
14:38
<stgraber>
it should be a standard one, it's simply calling x11vnc after all ;)
14:39
<alkisg>
Ah, doens't it use any ssl lib on top of that? ok..
14:39
<DawnLight>
this is my init script which i define to be run in lts.conf http://pastebin.com/f1c173028
14:39
<stgraber>
alkisg: where did you read that italc 2.0 will be on 11100 ?
14:39
<alkisg>
stgraber: but still, it's a really annoying problem, and if italc is going to change the port anyway, why not make the change earlier...
14:40
<DawnLight>
i've openssh-server installed on the client so i can log in to see what's up
14:40
<alkisg>
stgraber: http://sourceforge.net/mailarchive/forum.php?thread_name=200812281333.43713.tobias.doerffel%40gmail.com&forum_name=italc-devel
14:40primeministerp has quit IRC
14:40primeministerp has joined #ltsp
14:41
<DawnLight>
so as you can see... is anyone following?
14:42
<stgraber>
hmm, ok, didn't remember that part of Tobias' mail.
14:42
<DawnLight>
this is the mentioned irrigate.sh http://pastebin.com/f7bfb932c
14:42
<stgraber>
if we want to switch to 11100 we'll need to make sure everything works just fine as it used to, so basically making sure nobody ever has to set 11100 in the iTalc GUI
14:42
and make sure that a standalone ica will listen on 11100 too, ...
14:43
so we don't break iTalc with LTSP or users starting italc/ica manually
14:43
<alkisg>
sure, I can make a patch for that, and we have enough time to test it in all cases for lucid
14:43
<stgraber>
so that's patching both ica-launcher and italc-launcher + ica and italc themselves (the actual c++ code)
14:43
<alkisg>
Why? Aren't the launchers enough?
14:43
I think we *only* have to change 2 lines in ica-launcher
14:44
(no, 4, there are 2 more for ltsp)
14:45
<stgraber>
I have users who use italc-launcher for the initial configuration, then use italc without the launcher
14:45
so they can keep the layout of the computers in the UI and stuff like that
14:45
<alkisg>
I also do that, it works fine in Karmic with custom ports
14:45
<stgraber>
so if we change the port, we should change it everywhere or we'll get bug reports for sure
14:46
<alkisg>
But the point is that the ports should be automatically moved if they are in use
14:47
E.g. suppose that an LTSP client wants to use port 11134, and it's in use. It should be able to select another port without problems
14:47
It currently does that, but of course with ica-launcher
14:47
ica standalone shouldn't be launched
14:47
Italc on the other hand just reads a configuration file, so no problem there
14:48
And italc-launcher can read both ports from xprops
14:48
(or from avahi, for other computers)
14:49
<stgraber>
right but things like: Start italc => Add a workstation manually => Set the IP
14:50
won't work as you'll need to manually set the port
14:50
because it'll try 5800 by default
14:50
<alkisg>
Right, so c++ code should be patched too
14:50
Hmm....
14:50
<Gadi>
DawnLight: don't irrigate your sprouts in the foreground
14:50
<stgraber>
same with ica, as italc will automatically connect to 11000 by default, ica should listen on 11100 by default
14:50
<Gadi>
otherwise, nothing else gets done
14:50
:)
14:51
<sebas891>
alkisg: if I change something in the script /opt/ltsp/i386/usr/share/initramfs-tools/scripts/nfs-bottom/ltsp I've to do ltsp-update-image and ltsp-update-kernels to get the changes activated. no?
14:52
<Gadi>
sebas891: you need to run update-initramfs -u
14:52
<alkisg>
sebas891: update-initramfs -u and ltsp-update-kernels
14:52
<Gadi>
in the chroot
14:53
<sebas891>
ok .
14:53
<alkisg>
stgraber: you're right, it's more hussle than I imagined, and the code has many hardcoded references to 5800/5900 ... :(
14:53
BTW, a second idea... why not move the italc-devel ppa to the edubuntu one? It'll give worth to the edubuntu ppa ;)
14:54
<DawnLight>
Gadi: look
14:54
<alkisg>
(I mean, cancel the italc ppa, and move the italc builds to edubuntu-testing etc)
14:54
<stgraber>
alkisg: that'd make sense
14:54
<DawnLight>
Gadi: i'm doing it in the foreground?
14:55hersonls has quit IRC
14:55
<DawnLight>
Gadi: i thought that i was doint it in the background by launching '/opt/irrigate.sh &'
14:55
<Gadi>
DawnLight: ah,nm - does it run from a shell?
14:55
<DawnLight>
what do you mean by that?
14:56
forgive my ignorance
14:56
<Gadi>
if you ssh into the client or drop to a shell on the client
14:56
and run it by hand
14:56
<DawnLight>
yes
14:56
<Gadi>
no errors?
14:56
<DawnLight>
i run ./irrigate.sh and it runs
14:56
like it is supposed to
14:56
but on bootup it seems to only do the loop once
14:57
<Gadi>
how do you set it to run on bootup?
14:57
<DawnLight>
because it obviously ends i don't see the process running and the log file that it writes has only two entries
14:57
on and off
14:57
this is my init script which i define to be run in lts.conf http://pastebin.com/f1c173028
14:58
^
14:58
<Gadi>
with RCFILE_01?
14:58
<DawnLight>
right
14:58
<Gadi>
I believe RC scripts dont work well with daemonized things, because the controlling shell gets killed somewhere along the way
14:58
you probably need to dissociate the daemon from the controlling shell
14:59
<DawnLight>
what are you calling a daemon?
14:59
<Gadi>
your while loop
14:59
:)
14:59
<DawnLight>
huh
14:59bieb has left #ltsp
14:59
<DawnLight>
so how do i do that?
14:59
and why does it get killed?
14:59
<Gadi>
well, why don't you try a different approach:
15:00
make your little script an initscript
15:00
but put at the top a call to source /usr/share/ltsp/ltsp_config
15:00
and an abort variable
15:00
so, say IRRIGATE=True
15:00
<alkisg>
Why not use a cron job instead? I think Lns has a wiki page for that...
15:00
<Gadi>
in lts.conf
15:01
ah, or a cron job
15:01
that would work, too
15:01
<DawnLight>
does cron do seconds?
15:01
<alkisg>
Not the interval
15:01
Keep the "small" sleep
15:01
And put the cron to run every 480 seconds - whatever you have as a long duration
15:02
<DawnLight>
ok... that may work
15:02
<alkisg>
(maybe I'm saying this upside-down, me looks at the script...)
15:02
https://help.ubuntu.com/community/UbuntuLTSP/ChrootCronjobs
15:04
<Gadi>
DawnLight: are you on ubuntu 9.10?
15:04* DawnLight wonders if he could make this whole thing an lts.conf based setup so his other clients won't start irrigating the whole place
15:04
<DawnLight>
yes, 9.10 Gadi
15:04* Gadi thinks stgraber incorporated the cron stuff upstream
15:04
<Gadi>
stgraber?
15:05
<ltsppbot>
"alkisg" pasted "cron-based script for DawnLight" (12 lines) at http://pastebot.ltsp.org/3
15:05
<alkisg>
DawnLight ^^ I meant that you just kept the duration, and put "interval" in cron
15:05
<DawnLight>
hmm tasty
15:06
<Gadi>
and if you source /usr/share/ltsp/ltsp_config, you can make duration and interval lts.conf-programmable
15:07
and if you use logger, you can log to syslog and optionally pick up the logs server-side
15:07
<DawnLight>
i don't quite get that
15:07
<Brian_H>
anyone know in kubuntu where you disable the "you will be logged out in 30 seconds" message?
15:08
<DawnLight>
all this is neat
15:08
<ltsppbot>
"Gadi" pasted "lts.conf-programmable duration" (13 lines) at http://pastebot.ltsp.org/4
15:09
<johnny>
Brian_H, ask in #kubuntu
15:09
you might not be able to at all tho
15:09
<ltsppbot>
"Gadi" pasted "lts.conf-programmable duration and log to syslog" (10 lines) at http://pastebot.ltsp.org/5
15:10
<alkisg>
Hmmm more stuff with less lines... :D
15:10
<DawnLight>
wow Gadi this is so cool
15:10
<Gadi>
so many possibilities
15:10
:)
15:11
<DawnLight>
yeah
15:11
so how do i set it up in lts.conf?
15:11
<Gadi>
ltsp_config will set your lts.conf params as environment variables
15:11
<DawnLight>
hrm
15:11
<Gadi>
so, in the above example, you would set: DURATION=10
15:11
in lts.conf
15:12
to change from 5 (default) to 10
15:12
<DawnLight>
and what if i would also like to play with the interval in lts.conf?
15:12
<Gadi>
well, if stgraber's lts.conf param for cron is already in there... (not sure)
15:12
<DawnLight>
that's a different story now, isn't it
15:12
<Gadi>
then, it would be set there
15:14
<DawnLight>
do we find out?
15:14
<Gadi>
ah, it seems it might be
15:14
<DawnLight>
yes
15:14
<Gadi>
CRONTAB_0 = "<a valid crontab line>"
15:14
or maybe it is
15:14
<DawnLight>
wow
15:14
<Gadi>
CRONTAB_00
15:15
CRONTAB_01
15:15
like that
15:15
<DawnLight>
this is by looking at the source?
15:15
<Gadi>
yeah
15:15
but, I was looking upstream
15:15
it would be in lts-setup
15:15
er,
15:15
ltsp-setup
15:15
which is prolly in /opt/ltsp/i386/etc/init.d/ltsp-setup
15:15
<DawnLight>
i'll get it
15:16
you mean ltsp-client-setup?
15:16
<Gadi>
yeah, maybe
15:16
is CRONTAB in there?
15:17
<DawnLight>
yes i see the thing
15:17
ahuh
15:18
<Gadi>
so, you should be able to do something like: CRONTAB_01 = "*/6 * * * * root /path/to/myscript"
15:18
which should run your script every 10 minutes or so
15:18
<DawnLight>
so i put the file in there in the chroot and the interval is using the crontab lts.conf entry and the duration is an lts.conf patameter
15:19
<Gadi>
adjustable by the first entry
15:19
right
15:19
<DawnLight>
i can work cron a little bit
15:20
ok this is awesome i'm preparing it right now
15:21shawnp0wers has quit IRC
15:28
<DawnLight>
waiting for the image to rebuild. thanks a lot Gadi
15:29
anywhere i can throw a good word?
15:30
<Gadi>
a good word?
15:30
<rjune>
your local synagogue?
15:30
<Gadi>
like a howto?
15:30
lol
15:31
I would say on UbuntuWiki
15:31
<rjune>
Gadi, I was adapting to the audience. if it were me, I would say the local catholic churge
15:31
<Gadi>
you can write up how you irrigate your sprouts with LTSP
15:31
<rjune>
church too
15:31
<Gadi>
rjune: quiet from the peanut gallery ;)
15:31
<rjune>
grumble grumble.
15:32
<Gadi>
hehe
15:32
<DawnLight>
i will. i will
15:33
with pictures
15:33
:)
15:34
the /etc/cron.d/ltsp is empty
15:35
two spaces after the =
15:37
<Gadi>
two spaces after the =?
15:37lucascoala has joined #ltsp
15:38
<Gadi>
ah!
15:38
silly stgraber
15:38Selveste1___ is now known as Selveste1
15:39
<Gadi>
don't put a space after or before the = sign
15:39
for that parameter
15:39
<DawnLight>
hm
15:40
thanks for the tip
15:40
<Gadi>
cat $ltsconf | grep -E "^CRONTAB_[0-9]{2}=" | sed -e "s/.*[0-9]\{2\}=\"//g" -e "s/\"$//g" >> $CRON_FILE
15:40
he actually cats lts.conf to get that parameter
15:40
<DawnLight>
should i report that as a bug?
15:40
<Gadi>
most likely so the shell does not try to expand the *
15:40
in the cron line
15:40tstafford has joined #ltsp
15:40
<Gadi>
well, its not a bug really
15:40
just a gotcha
15:40
:)
15:41
<DawnLight>
looks like a bug to me
15:41
<Gadi>
:)
15:41
so picky
15:41
<DawnLight>
i'm reporting it!
15:45
:P https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/480950
15:46
anyway it still doesn't work
15:47
CRONTAB_01="*/6 * * * * root /opt/irrigate.sh
15:47
<Gadi>
don't use single quotes
15:47
<DawnLight>
this is what i have there
15:47
with a double quote in the end
15:47
<Gadi>
ah, dont put spaces in the beginning of the line
15:47
<DawnLight>
grr
15:47
<Gadi>
lol
15:47
stgraber!
15:48
<DawnLight>
ok last reboot
15:48
<Gadi>
lol
15:48* Gadi thinks he code it that way to mess with you
15:48
<Gadi>
*coded
15:49
<DawnLight>
thank god you're here then
15:49* Gadi is just reading his grep
15:50
<DawnLight>
ahuh!
15:50
it works
15:51
<Gadi>
\o/
15:51brendan0powers has quit IRC
15:51
<DawnLight>
so where am i seeing the log?
15:52
<Gadi>
did you use logger?
15:52
<DawnLight>
yes
15:52
exactly what you pasted
15:52
<Gadi>
ah, you have to set your server syslog to accept remote logging
15:52
so, on the server, edit /etc/default/syslog
15:52
or whatever
15:53
and add a "-r" to the options
15:53
and restart the syslog service
15:53
<DawnLight>
ahuh
15:55
<Gadi>
if you want to disable syslog on some clients, just set SYSLOG_HOST="/dev/null"
15:55
you may not want all of your clients logging to the server
15:55dro has quit IRC
15:56
<_UsUrPeR_>
hey, has anybody had any luck with booting a client to rdesktop in 9.04? I have IP v4 forwarding turned on for localapps, along with the chmod /etc/resolv.conf for the chroot...
15:56
but when I boot my client, it comes up with a blinking screen...
15:56
like it's *trying* to connect, but can't bring up the rdesktop session
15:58
here's my current lts.conf: http://pastebin.com/m47f19a23
15:58
<DawnLight>
hmm
16:00
<_UsUrPeR_>
windows server is win2k8 R2
16:01
I'll cross this bridge tomorrow :
16:01
:P
16:02
<DawnLight>
thanks a lot Gadi . good night
16:04DawnLight has quit IRC
16:07alkisg has quit IRC
16:14bobbyC has quit IRC
16:26davidj has quit IRC
16:34CAN-o-SPAM has quit IRC
16:36coordinador has joined #ltsp
16:36
<coordinador>
hi
16:41mikkel_ has quit IRC
16:41mikkel has quit IRC
16:43* Lns wakes up
16:43Schmick has joined #LTSP
16:43Schmick has left #LTSP
17:13vagrantc has joined #ltsp
17:27lonchiton has joined #ltsp
17:27lonchiton has left #ltsp
17:29Ahmuck has joined #ltsp
17:29Ahmuck is now known as Ahmuck-Sr
17:39
<Ahmuck-Sr>
does flash have to be installed in chroot as well?
17:39
ie, download adobe flash in chroot and install?
17:42
<coordinador>
Ahmuck-Sr, if you want to run Firefox locally, yest.
17:42
*yes
17:43
But normally not
17:44sebas891 has left #ltsp
17:51Gadi has left #ltsp
17:56glocke has joined #ltsp
17:56glocke has left #ltsp
18:24lucascoala_ has joined #ltsp
18:35cyberorg has quit IRC
18:40lucascoala has quit IRC
18:41staffencasa has quit IRC
18:50cyberorg has joined #ltsp
18:58Brian_H has quit IRC
19:02Lns has quit IRC
19:25vagrantc has quit IRC
19:51vvinet has joined #ltsp
20:13alexqwesa_ has joined #ltsp
20:26pmatulis has quit IRC
20:28Patina has quit IRC
20:29alexqwesa has quit IRC
20:30Patina has joined #ltsp
20:34Patina has quit IRC
20:34Patina has joined #ltsp
21:12coordinador has quit IRC
21:58alkisg has joined #ltsp
22:28yanu has quit IRC
22:29yanu has joined #ltsp
22:51lucascoala_ has quit IRC
22:56pimpministerp has joined #ltsp
22:57pimpministerp has quit IRC
23:43alkisg has quit IRC
23:57alkisg has joined #ltsp