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


Channel log from 11 December 2006   (all times are UTC)

00:17Capricorn^80 has quit IRC
00:51empiric has joined #ltsp
00:51
<empiric>
hi all
00:51
i have installed ubuntu +ltsp4.2
00:51
all is good
00:51
but i have diferent monitors
00:51
and lcds
00:51
some 17'' moniotrs are not working
00:51
any idea
01:00krins has joined #ltsp
01:00empiric has quit IRC
01:00
<krins>
hi all
01:01
my monitors wont get disply in ubuntu +ltsp4.2
01:01
any idea
01:10Capricorn^80 has joined #ltsp
01:17MoL0ToV has joined #ltsp
01:39
<krins>
helo
01:39
my screens are blinking
01:39
some of not all
01:58
one one mac hine i saw
01:58
XDMCP fatal server error maximum session declined maximum no of open session reached
01:58
any idea
01:58
i have changed vi /etc/X11/gdm/gdm.conf
01:58
and make XDMCP = true
01:58
here i found max session filed its disabled
02:09redguy_ has joined #ltsp
02:10redguy_ has left #ltsp
02:20redguy_work has joined #ltsp
02:38
<krins>
Hello
02:39krins has quit IRC
02:44Capricorn^80 has quit IRC
03:00krins has joined #ltsp
03:00
<krins>
hi
03:01
i have some screen resolution prbs
03:13
<wizzy>
krins: There are some settings for max open xdmcp sessions in gdm.conf
03:13
screen resolution - change settings in lts.conf
03:42ogra has joined #ltsp
03:59krins has quit IRC
04:00krins has joined #ltsp
04:12bobby_C has joined #ltsp
04:20FernandoMM has joined #ltsp
04:30Kodex has joined #ltsp
04:31Avatara has joined #ltsp
04:32
<krins>
wizzy
04:33
yes i have mate maxsession=50
04:33
ok
04:33
but strange things are going on
04:33
with some of my monitors
04:36
http://pastebin.ca/275228
04:36
see the link
04:38
i have some moniotrs working at X_MODE_0 = 800x600 X_MODE_1 = 1024x768
04:38
but now it wont works
04:39Capricorn^80 has joined #ltsp
04:43
<krins>
yanu
04:43
u there
04:43
any one knows
04:43
am changing settings in lts.conf
04:43
but it seems nothing going to change
04:43
i am using ubuntu+ltsp4.2
04:48
gdm[3278]: (child 3349) gdm_slave_alrm_handler: ws081.ltsp:0 got ARLM signal, to ping display
04:49
what this error mean
04:56
helo
05:03ogra has quit IRC
05:11
<krins>
wizzy
05:13ogra has joined #ltsp
05:17yanu has quit IRC
06:00Skarmeth has joined #ltsp
06:02Envite has joined #ltsp
06:02
<Envite>
Hello all from Spain
06:02
Hola a todos desde España
06:16vykarian has joined #ltsp
06:16
<vykarian>
morning =]
06:19Skarmeth has quit IRC
06:22
<cliebow>
mornings 8~)
06:30bricode has joined #ltsp
06:52Stevec has joined #ltsp
06:52Kodex has left #ltsp
07:02msinhore has joined #ltsp
07:08
<krins>
morning cliebow
07:08
hai i got some prbs in ubuntu+ltsp4.2
07:08
some of my old monitors wont get display
07:09
<vykarian>
krins booting runlevel 3 or 5?
07:09
<krins>
5
07:09
i have FUITSU seimens and IBM monitors
07:09
seimens have 2 models one works fine and other wont
07:09
no idea whats going on
07:10
<Envite>
frefcuencies?
07:10
<vykarian>
i'm not expert in runlevel 5
07:10
<Envite>
i had some issues with monitor frecuencies when started in ltsp
07:10
<vykarian>
but setting resolution for 640x480 for start could help?
07:11
<Envite>
use a multimode modeline
07:11
<vykarian>
07:12jammcq has quit IRC
07:13Stevec has quit IRC
07:27Envite has quit IRC
07:31Envite has joined #ltsp
07:34vagrantc has joined #ltsp
07:35
<ogra>
vagrantc, !
07:35
morning
07:35
<vagrantc>
ogra: indeed!
07:35* vagrantc can't sleep
07:36
<ogra>
vagrantc, mdz forwarded me a mail from you where you complain about policy bugs in ltspfs ...
07:36
why dont you file them ?
07:36cliebow_ has joined #ltsp
07:36
<ogra>
s/dont/didnt/
07:36
<vagrantc>
ogra: well, i already talked to you about them, and to you there were a non-issue :P
07:37
<ogra>
well, but if theyx hold up the package for debian adoption i'm fine to fix it ...
07:37
is it only the manpages or anything else ?
07:37
sbalneav has to change it btwe
07:37
<vagrantc>
it's the editing of configuration files in the .postinst scripts
07:38
i think those were the main changes.
07:38
also, all of the bzr branches i could find were out of sync with the packages in ubuntu
07:38
<ogra>
sbalneav has the most recent branch iirc
07:38
i only upload his package ....
07:39
<vagrantc>
it was more out of date than yours
07:39
<ogra>
hmm
07:39
<vagrantc>
well, the packaging branch.
07:39
<ogra>
i need to talk to him then
07:39
my branch only has patches for his package ... that shoul have been merged
07:40
<vagrantc>
ogra: scotty hasn't been around much ... i should probably email.
07:40
<ogra>
the postinst ? you mean /etc/modules ? that can even be dropped, it depends on fuse-utils anyway, which cares for the module loasding
07:40
<vagrantc>
i get so used to irc with certain people sometimes...
07:40
<ogra>
well, real bugs would also help ;)
07:40
<vagrantc>
ogra: i made patches in my bzr branch, did you get the mail with mention of my bzr branch?
07:41
<ogra>
i tent to forget about things you pointed out on irc :)
07:41
nope
07:41
*teand
07:41
argh
07:41
*t e n d
07:41
<vagrantc>
i also cross-posted it to pkg-ltsp-devel
07:41
<ogra>
hmm, when ?
07:41
<vagrantc>
ogra: honestly, i have no idea where to report bugs.
07:42
Sat, 9 Dec 2006 17:24:26 -0800
07:42
<ogra>
https://launchpad.net/distros/ubuntu/+source/ltsp/+filebug
07:42
https://launchpad.net/distros/ubuntu/+source/ltspfs/+filebug
07:42
<vagrantc>
like i'll remember that.
07:43
<ogra>
the latest msg from you i have in pkg-ltsp-devel is from NOV 28th
07:43
<vagrantc>
ogra: hrm. i got my own message ...
07:43
<ogra>
oh207, wow, it just hit my inbox this second
07:44
you forgot to mention that users have to be in the fuse group
07:44
<vagrantc>
yes, i realized that/
07:44
i'll probably discuss it a little bit in a debian-edu meeting later today
07:45
<ogra>
the postinst can really go right away, we dont need it aqnymore (fuse-utils cares)
07:45
<vagrantc>
ogra: sorry for any headaches i've caused you- i thought it was essentially a "wontfix" :P
07:45
<ogra>
the manpage issue can be solved by moving the scripts to /usr/lib/ltspfs
07:45
well, the functionallity moved to fuse-utils :)
07:45
<vagrantc>
manpage issues?
07:45
<ogra>
there are four scripts without manpage
07:46
<vagrantc>
ah, yes.
07:46
<ogra>
(see the lintian override file)
07:46
i'm not sure whys they are in /usr/bin now ...
07:46
i'Äll clearify that with sbalneav
07:46
<vagrantc>
it probably wouldn't be a *bad* thing to have manpages for them :P
07:46
and lintian warnings are non-fatal.
07:47
<ogra>
not really, a user should never use them directly
07:47
<vagrantc>
so i felt the best thing, from a debian perspective, is to be reminded to make some manpages
07:47
<ogra>
so /usr/lib is the right place imho
07:47
<vagrantc>
well, knowing how likely i am to skip documenting anything, i appreciate the warning.
07:47
/usr/share (if they're arch-independent)
07:48
<ogra>
right, but they shouldnt have any manpages, they are executed by udev or by ltsp-client and not designed to be run by users ...
07:48
<vagrantc>
there are *lots* of manpages for things not in *bin.
07:49
<ogra>
right, /usr/share then
07:50
<vagrantc>
at any rate, etch just froze today, so i'm not likely to want to make any major changes in the near future for debian. :)
07:50
<ogra>
still, if scripts that act as a clutch between different other scripts are there, they shouldnt have manpages but good inline documentation ... all people that will ever read that docs are programmers :)
07:50
<vagrantc>
not that ltspfs will make it into etch :(
07:50
hopefully i don't need any tweaks to ldm in etch to get localdev working ... i tested it months ago ...
07:52
<ogra>
can you send me a list with the things in ltsp you want changed (like the optional socket instead of a static one) ?
07:52
(or file bugs)
07:53
<vagrantc>
ogra: would you prefer a list of things i want changed, or patches? :)
07:53
<ogra>
as you like
07:53
i have some time to code myself in the next weeks ;)
07:53
<vagrantc>
they let you do coding?
07:54* vagrantc almost forgot that
07:54* vagrantc hides
07:54
<ogra>
even though that will be sucked up by ltsp-manager and edubuntu-auth-server/client
07:54
sometimes they do ... between the travelling :P
07:57
(dunno if you read my blog :) )
07:59
<vagrantc>
ogra: no
07:59* vagrantc sees that fuse-utils in debian doesn't handle loading the fuse modules
08:00
<ogra>
it should .... through some weird udev tweaking which i rip out in ubuntu
08:00
(its incompatible with ubuntus udev as is)
08:01
<vagrantc>
how does udev support it?
08:01* vagrantc looks
08:02
<ogra>
udev loads the module if /dev/fuse is accessed
08:02
there is an udev rule
08:02
<vagrantc>
i thought udev only worked when the module is loaded, not loading the module...
08:02
onlyrules i see are for setting the permissions
08:02
<ogra>
and the postinst calls some udev reload mechanisms that arent used in ubuntu
08:03
<bricode>
ogra: does the ltsp-build-client --workstation work as of yet? I'm starting to play around with it.
08:04
<ogra>
bricode, not yet, ltsp in feisty is broken currently give it one or two days so the new dependencies are moved to main
08:04
i havent merged the fat-client tree yet
08:05
<bricode>
ogra: groovy. I'm starting to play around with it. I got it to do some stuff last night. Boot up with kernel and such, but homedir stuff was broken, so no gdm login.
08:05
ogra: I'd like to help out with testing on this. I've got a setup that's working as a testbed.
08:06
<ogra>
https://launchpad.net/people/ogra/+branch/ltsp/feisty-fat-clients has the --workstatiojn plugin
08:07
it will still need bits and pieces for different desktops (currently it only installs edubuntu-desktop and makes the nece4ssary dirs writeable
08:08
i'm planning something like --workstation ubuntu/kubuntu/xubuntu/edubuntu
08:08
so the option gets a switch for the preferred desktop
08:10
<bricode>
ogra: I remember you talking about that down at Google.
08:10
ogra: I'm also interested in that because of xubuntu's use of xfce.
08:10
<ogra>
ah, right, you are brian :)
08:10
hi there :)
08:10
<bricode>
ogra: check :)
08:11
<ogra>
i just got the remaining patches to edsadmin, so we're on our way with the ldap stuff ... (thats what's currently holding up the fat-client implementation)
08:11
<bricode>
ogra: finally get settled back in Europe?
08:11
<ogra>
yeah
08:12
i had to do some east europe travelling though ...
08:12krins has quit IRC
08:12
<bricode>
ogra: I've downloaded the feisty-fat-client stuff using bzr. What's the best way to start using it?
08:13
<ogra>
bzr diff -r452..454 in the source tree should show you the code
08:13
<bricode>
And I make those changes to my current set of files?
08:13
<ogra>
apart from that, you should be able to just run apt-get build-dep ltsp; debiuld
08:14
right
08:14
you change anyth9oing in the code tree and run bzr --commit afterwards
08:14
<bricode>
Okay. I'm still getting used to debian packages and ubuntu flow.
08:14
<ogra>
of you want me to merge your stuff, copy it on a webserver (sftp and bzr push)
08:15
<bricode>
Cool beans.
08:15
<ogra>
theere is no need to know the poackaging to submit patches though
08:15
;)
08:15
<bricode>
I used Gentoo for too long. I think I'm broken :)
08:15
<ogra>
heh, many of our developers come from gentoo ;)
08:16* ogra will be afk for 1h or so ... bbl
08:16
<bricode>
Yeah, when you actually want to get something done it's worth switching :) It took me about 5 hours to get a Ubuntu box up and running.
08:16
<ogra>
thats long :)
08:16
<bricode>
Needed custom kernel and funk for 1TB RAID.
08:16
And different nvidia drivers.
08:16
<ogra>
ah, ok, then its normal :)
08:20Envite has quit IRC
08:24Skarmeth has joined #ltsp
08:35Capricorn^80 has quit IRC
08:42vaineh has joined #ltsp
08:52J45p3r_ has joined #ltsp
08:53
<bricode>
ogra: Is there a way to use a local repository so that I don't have to keep downloading everything with ltsp-build-client?
09:09oh207 has quit IRC
09:09MoL0ToV has quit IRC
09:14Shmattie has quit IRC
09:18
<vagrantc>
bricode: --mirror file:///
09:18
<bricode>
vagrantc: so I just feed the directory where I've downloaded all of the packages?
09:18
<vagrantc>
bricode: though, even better, set up a local web server and do --mirror http://127.0.0.1/...
09:18
bricode: it's needs to be an apt repository...
09:19
<ogra>
easiest is to just use a CD iso and mount it -o loop :)
09:19
<bricode>
vagrantc: Where's the apt repository on Ubuntu? Can I use apt-cache or something?
09:19* vagrantc agrees with ogra
09:20
<bricode>
bricode: digs up install cd
09:20
<ogra>
it needs to bew a feisty CD for the feisty client by default ...
09:20
*be
09:21
<bricode>
ogra: Okay. Need to move a few bits then :)
09:21
<ogra>
:)
09:21Gadi has joined #ltsp
09:22
<bricode>
I need a faster internet connection. 3 Mbit just doesn't cut it.
09:22
Hey Gadi.
09:23
ogra: Have a link to feisty cd?
09:24
<ogra>
http://cdimage.ubuntu.com/releases/feisty/herd-1/
09:24sepski has joined #ltsp
09:25
<bricode>
Excellent. I'm still finding my Ubuntu legs.
09:31
<Gadi>
bricode: mornin - give me a sec - im hittin the ground runnin this mon morning
09:32
<bricode>
Gadi: No worries. Have some news for you.
09:36gentgeen__ has joined #ltsp
09:47oh207 has joined #LTSP
09:50Avatara has quit IRC
09:51Avatara has joined #ltsp
10:00
<bricode>
Gadi: let me know if you got my other mesages.
10:07jammcq has joined #ltsp
10:07
<jammcq>
howdie kids
10:09Avatara has quit IRC
10:15andresmujica has joined #ltsp
10:17
<Gadi>
bricode: nope
10:17
mornin, jammcq
10:17
<bricode>
Humm. Weird.
10:17
<Gadi>
you may need to identify with Nickserv
10:23sepski has quit IRC
10:28efra has joined #ltsp
10:28
<bricode>
Haven't used irc in like 8 years.
10:28
<efra>
Hi everybody
10:45
<vykarian>
hey
10:50Egyptian[Home] has quit IRC
10:52Egyptian[Home] has joined #ltsp
11:01yanu has joined #ltsp
11:02Egyptian[Home] has joined #ltsp
11:17sbalneav has joined #ltsp
11:17
<sbalneav>
Morning all
11:17
<efra>
morning sbalneav
11:28
<vagrantc>
sbalneav: YOU!
11:28* vagrantc smiles
11:29
<sbalneav>
Me?!?!
11:29
Hey!
11:29
Quick question:
11:29
<vagrantc>
sbalneav: we's got some ltspfs talking to do :P
11:29
<sbalneav>
Sure.
11:29
<vagrantc>
we missed it for etch, but might be able to get it into debian-edu/etch.
11:29
<sbalneav>
I'm using xdmcp for login, and users just shut off their boxes at the login prompt.
11:30
<vagrantc>
ok...
11:30
<sbalneav>
leaving a hung nbd-server. And a file in /tmp
11:30
<vagrantc>
yeah...
11:30
<sbalneav>
any way to have these time out after a while? Or the 2 am pkill cronjob's the way to go? :)
11:31
<vagrantc>
well, you can set a timeout on the nbd-server ... but it might yank your terminal's swap out from under you... so that's no good.
11:32
i was thinking you could basically write a little nbd-ping on the terminal that just does a read from a random segment of the nbd device now and again, and then you set the nbd-server timeout to something higher than that ...
11:32
<sbalneav>
Meh.
11:32
<vagrantc>
the ideal way is to get nbd smart enough to implement the pinging stuff itself.
11:32
<sbalneav>
cron's easy :)
11:33
yeah. For later.
11:33
So, what can I help you with ltspfs wise?
11:33
<vagrantc>
i bet i could write a little nbd-pinging thing in a matter of minutes...
11:33
sbalneav: well, none of the branches are in sync with the current packages in ubuntu.
11:34
sbalneav: and ogra wondered why a bunch of stuff was in sbin/bin directories ...
11:34FernandoMM has quit IRC
11:34
<vagrantc>
i forget what all else, off the top of my head ... been trying to get the packages compliant with debian policy.
11:34
<sbalneav>
Hmmm, the "upstream" one SHOULD be in sync with the ubuntu one.
11:35* vagrantc notes the use of SHOULD
11:35
<sbalneav>
If it's not, then ogra fixed something, and I missed a note from him.
11:35
<vagrantc>
i think the "static dev" stuff is missing from bzr ...
11:35
<sbalneav>
Whatever's needed to get them ok, policy wise, let me know, and I'll fix 'em
11:36
<vagrantc>
grab the .orig.tar.gz from ubuntu, and compare it to your upstream branch ...
11:36
<bricode>
um, what's ltspfs used for?
11:36
<sbalneav>
ok, I'll check into that later today. Seems like I've got an NFS bug killing me :(
11:36
<vagrantc>
bricode: local device access from the LTSP server.
11:37
<bricode>
vagrantc: like usb/cdrom/whatever serverside?
11:37
<vagrantc>
bricode: yeah. accessing the thin-client's devices from the server (where users usually log in).
11:38
<bricode>
vagrantc: ah. Other way around. Check. So accessing thin client's usb/flash.
11:38
<vagrantc>
bricode: correct.
11:39
<bricode>
vagrantc: Doesn't that create a whole lot of devices on the server since each thin client may have multiple devices?
11:40
<vagrantc>
bricode: sort of, yes. though it's done in such a way that that shouldn't be much of a problem. though i guess it may require patches to some programs.
11:41
<bricode>
Nifty.
11:41
<cliebow_>
sbalneav:
11:41
<sbalneav>
Hey cliebow
11:41
Ugh. Looks like my NFS problem's a kernel bug :(
11:42
Woe is me, I have to compile a kernel :(
11:42
<cliebow_>
sbalneav: Hi: im getting "backend initialization failed setting up a script for instaling ldap.
11:43
am i missing a library? db4.2 and db4/2 util are there
11:43
<bricode>
sbalneav: Winnipeg cold yet? :)
11:43
<sbalneav>
Nah. only -3 c
11:43
cliebow_ what did you install? slapd?
11:43
<cliebow_>
yeah
11:44
going by my working slapd on the lappie
11:57andresmujica has quit IRC
11:59
<bricode>
!vi
11:59
<ltspbot>
bricode: Error: "vi" is not a valid command.
12:03
<jammcq>
sbalneav: Scotty !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
12:04
<sbalneav>
Hey jammcq
12:20cliebow_ has quit IRC
12:26primeministerp has quit IRC
12:27primeministerp has joined #ltsp
12:31cliebow_ has joined #ltsp
12:47J45p3r__ has joined #ltsp
12:50J45p3r_ has quit IRC
12:50vaineh has quit IRC
12:50Skarmeth has quit IRC
12:50neuralis has quit IRC
12:50monteslu has quit IRC
12:50bronze has quit IRC
12:50dberkholz has quit IRC
12:50str4nd has quit IRC
12:50ccherrett has quit IRC
12:50brich has joined #ltsp
12:51neuralis has joined #ltsp
12:51weeswordy has joined #ltsp
12:51str4nd has joined #ltsp
12:51dberkholz has joined #ltsp
12:52ccherrett has joined #ltsp
12:54monteslu has joined #ltsp
12:54vaineh has joined #ltsp
12:55Skarmeth has joined #ltsp
12:55bronze has joined #ltsp
12:58
<str4nd>
hmm
12:58
freenode is broken?
12:58
<weeswordy>
Hi vagrantc - you got a minute to spare?
12:59
still struggling with ltsp5
13:00
I think it's a font problem I have now.
13:09vykarian has quit IRC
13:13
<vagrantc>
weeswordy: font problem, eh?
13:13
<weeswordy>
Well, maybe...
13:14
Terminals now boot fine, up to the point where X starts - then the keyboard dies
13:14
I have seen a few error messages about fonts, and putting 2 and 2 together, I got 16
13:15
Have tried booting to a shell, and the keyboard then works, though the machine persistently asks for a login
13:16
interspersed with command prompts
13:16
Hope my explanation makes some sort of sense!
13:19
<vagrantc>
strange ...
13:19
i don't suspect it's really a font problem.
13:20
weeswordy: have you set SCREEN_NN where NN is less than 10 ?
13:20
weeswordy: in lts.conf
13:21efra has quit IRC
13:21
<vagrantc>
weeswordy: and is this ubuntu or debian?
13:21
<weeswordy>
Yes - I copied a working ltsp4-2 lts.conf into the directory
13:21
It's debian etch
13:21
<vagrantc>
well, you musn't set SCREEN_NN where /etc/inittab is already spawning something.
13:22
i.e. SCREEN_01 through SCREEN_06, on a typical debian system.
13:22
(though maybe sometimes you can use SCREEN_04+
13:22
)
13:23
weeswordy: got it?
13:27
<weeswordy>
Yep - I can use the keyboard, but it is just running as a PXE booted machine, with a local login
13:27
no login to the server, as normal with ltsp
13:28
Is the lts.conf file way different in this version, and if so, is there a guide of some sort?
13:28
<vagrantc>
there's one for ubuntu, which is pretty similar.
13:28
the main difference is that in many cases, you shouldn't even need an lts.conf
13:29
<weeswordy>
sounds good,
13:29
is the plan to still connect to the server for all the user's requirements?
13:30
<vagrantc>
and that you have to watch out for conflicts with things in inittab
13:30
weeswordy: that's the default, but certainly not the only option.
13:30
<weeswordy>
How do I tell it which server to connect to?
13:30
is it just an X command in inittab?
13:31
<vagrantc>
weeswordy: are you using ldm or xdmcp (gdm/kdm/xdm) ?
13:31
ldm is the default ...
13:31
<weeswordy>
gdm
13:31
<vagrantc>
SCREEN_07=startx
13:32
<weeswordy>
OK, just trying that now
13:32
<vagrantc>
as for specifying the server .... i don't remember off the top of my head. i don't think it's any different from ltsp 4.x
13:33
<weeswordy>
It all makes a lot more sense now - you are my hero!! :)
13:33sepski has joined #ltsp
13:33
<weeswordy>
Thanks
13:33
<vagrantc>
i try :)
13:33
<weeswordy>
Just while you are there - if I want some local apps, I just chroot to /opt/Ltsp
13:33
and install debs or compile packages
13:33egypcio has quit IRC
13:34
<vagrantc>
chroot /opt/ltsp/ARCH apt-get install foo
13:34
weeswordy: where ARCH is likely i386
13:34
<weeswordy>
Marvellous!
13:35
<vagrantc>
but having a mixed remote/local login requires a lot of tinkering
13:35
<weeswordy>
Hopefully off to play with voip apps now - thanks again for your help.
13:35
<vagrantc>
at the moment, it's simplest to do everything locally, or everything remotely.
13:36egypcio has joined #ltsp
13:36
<weeswordy>
Can I run a local app in a similar way to version 4.2 - I got that sort of working ok?
13:36efra has joined #ltsp
13:37
<vagrantc>
weeswordy: there's no built-in support for it- you will have to manually configure all the stuff required...
13:37sepski has quit IRC
13:38
<weeswordy>
Ah well, if I get it going, I will try to write up some notes about it for laughs!
13:45
<bricode>
VoIP apps huh? Interesting.
13:48efra has quit IRC
13:51ogra has quit IRC
14:08ccjoe has quit IRC
14:09ccjoe has joined #ltsp
14:22bill_c has joined #ltsp
14:27
<bricode>
Does anyone know where the xorg.conf is pulled from if you're doing a fat client setup?
14:28
<sbalneav>
Well, depending on HOW you're setting up the fat client, ether in the nfs choot, or it's auto-generated.
14:29
<bricode>
sbalneav: Is there an easy way to tell? I've edited the chroot one, and it's not being pulled in.
14:29
sbalneav: So, where is it autogenerated?
14:30
<sbalneav>
First of all, HOW are you setting up a fat client? That's not a standard part of LTSP.
14:31
<bricode>
sbalneav: I know :)
14:31
sbalneav: I'm using Oliver's workstation plugin.
14:31
<sbalneav>
So, you've done a full "apt-get install ubuntu-desktop" under the chroot?
14:32
<bricode>
sbalneav: Yes, the script does that for you. Except it uses Edubuntu instead of Ubuntu.
14:32
<sbalneav>
Then it should be pulling it from $CHROOT/etc/X11/xorg.conf
14:33
<vagrantc>
autogenerates.
14:33
<sbalneav>
In a full fat-client install?
14:33
<vagrantc>
it gets generated on each boot, most likely.
14:33
unless you configure it otherwise.
14:34
if there's no configuration in lts.conf telling a client to do anything else, it will autogenerate it.
14:34
<bricode>
vagrantc: lts.conf on server or $CHROOT?
14:34
<vagrantc>
bricode: chroot
14:35
is there an lts.conf on the server (other than within the chroot) ?
14:36
<bricode>
Nope.
14:36
I found it.
14:36
Is there documentation for lts.conf file?
14:36
Nevermind. There's an example.
14:46
<cliebow_>
sbalneav: all that bothered was an extra space in slapd.conf
14:46mymarrandy has joined #ltsp
14:47radoeka has joined #ltsp
14:48
<bricode>
vagrantc: Any hints on how to make it so the autogenerated xorg.conf doesn't stomp the one I want?
14:49
<vagrantc>
bricode: specify XF86CONFIG=/path/to/config-file
14:49
i think.
14:50
<bricode>
Yep.
14:50
vagrantc: Just found it in the lts-parameters file.
14:50
<mymarrandy>
dhcp server on 192.168.1.254 - ltsp server on 192.168.1.200 second NIC on 192.168.2.254 - ws/thinclients on 192.168.2.x - Question - how do i stop the thin-clients from getting an address from the 192.168.1.254 dhcp server ?
14:51
<vagrantc>
mymarrandy: put them on separate physical networks?
14:51
<mymarrandy>
which, occasionally, they do and abort during the boot
14:52
can you explain further
14:52
<vagrantc>
mymarrandy: have one switch for 192.168.1.x network, and one switch for 192.168.2.x ...
14:55
mymarrandy: does that make sense?
14:55
<mymarrandy>
how does that work ?
14:55
hmmm...could do with some explanation of how it fixes the issue
14:56
<vagrantc>
you have two network cards on your ltsp server? plug one of them into one switch, and the other into another switch.
14:56
the thin-clients are doing a broadcast to get an ip address, by physically separating them, there is no way they will get dhcp from the wrong dhcp server.
14:57
mymarrandy: that's assuming you are running a dhcp server on your ltsp server ...
14:58
<mymarrandy>
yes, two, actually, that's what i have already
14:58
<vagrantc>
you have two separate servers both running dhcpd ? or you have two dhcpd's running on one server?
14:59
<mymarrandy>
hmm..will need to check my setup.
15:00
<pscheie>
in a server with 2 nics, what controls which interface the dhcpd listens to?
15:00
is it a setting in /etc/dhcpd.conf? I see no reference in there to a specific eth0 or eth1.
15:00
<mymarrandy>
wait one
15:01Gadi has left #ltsp
15:01
<vagrantc>
typically, the the subnet declaration controls it
15:01
<jammcq>
huh?
15:01
<pscheie>
Is it just determined by the network number, e.g. it hands out 192.168.0 addys on the 192.168.0.254 interface?
15:01
<vagrantc>
pscheie: basically, yes.
15:02
<jammcq>
but, it will still receive requests on whatever interfaces are set on the command line
15:02
<vagrantc>
sure, but it will only respond to ones it's configured to respond to.
15:02
<pscheie>
which command line?
15:02
<jammcq>
when dhcpd starts, from the init script
15:03
and the options are usually set in a config file, the location of which depends on the distro
15:05
<mymarrandy>
internet comes in - goes to a firewall that has a dhcp server - to a switch - one port goes to 192.168.1.254 2nd nic assigned to 192.168.2.254 to a second switch - to the WS
15:06
I guess I don't get what your saying
15:06
<pscheie>
on fc5/k12ltsp, I don't see anything that specifically ties it to eth0, aside from it having addy 192.168.0.254
15:07dfjkghsjkg has joined #ltsp
15:07dfjkghsjkg has left #ltsp
15:07
<vagrantc>
mymarrandy: and you're saying that you're getting dhcp responses from the firewall's dhcp server on thin-clients plugged into the second switch?
15:08
<mymarrandy>
oh, mean having another nic on the firewall that has the 192.168.2.x interface and running the sever toi that ?
15:09
<vagrantc>
mymarrandy: that's not what i meant, no.
15:09
<mymarrandy>
The DHCP/ARP broadcast from the WS hits the switch, it goes to 192.168.2.254 on the ltsp server, as port forwarding is on, it goes out to the second switch and then hits the firewall DHCP server that responds with an offer
15:10
<pscheie>
The idea I'm pondering is having multiple nics such that each nic would handle a separate physical network but with just one dhcpd.conf
15:10
<vagrantc>
pscheie: that's easy.
15:11
mymarrandy: why are you forwarding DHCP ports?
15:11
<pscheie>
and just assign a different scope to each nic
15:11
yes, it seems like it would be easy--just want to make sure I'm not missing something or oversimplifying
15:12
<mymarrandy>
there are two interfaces in the ltsp server and packets are forwarded by default, otherwise wjen the WS came up, they would never get to the internet
15:13
it's not ports as such as the ARP broadcast as they WS don't have an IP yet
15:13
<vagrantc>
mymarrandy: port forwarding, or NAT ?
15:13
<mymarrandy>
sorry, your right, NAT
15:13
bad terminology...my bad
15:13
<vagrantc>
i've never seen NAT get take over DHCP requests before.
15:15
<mymarrandy>
aghh..my head hurts
15:15
<jammcq>
dhcp uses ethernet broadcasts, that doesn't go THROUGH a router
15:16cliebow_ has quit IRC
15:16cliebow_ has joined #ltsp
15:18
<mymarrandy>
I can fix it, by setting all my systems to static and turning off the firewall router so there is only one (the ltsp) dhcp server running, but...that's not a good fix for many people
15:18
Any ideas what i should be looking for ?
15:19
<jammcq>
I don't think we understand your current config, because what you described already, about your dhcp going through NAT just isn't possible
15:21* vagrantc agrees with jammcq
15:22
<mymarrandy>
it's going across the ltsp server interfaces from the 192.168.2.x (Workstations) to 192.168.1.254 (ltsp internal) and out through the second interface on 192.168.1.200 and reaching the dhcp server at 192.168.1.254
15:23
<jammcq>
no it's not
15:23
it can't
15:23
<mymarrandy>
typo - ignore that
15:23
<jammcq>
dhcp doesn't do that
15:24
<vagrantc>
mymarrandy: does the dhcpd.conf have multiple subnet declarations?
15:24
<mymarrandy>
it's going across the ltsp server interfaces from the 192.168.2.x (Workstations) to 192.168.2.254 (ltsp internal) and out through the (ltsp external) on 192.168.1.200 and reaching the dhcp server at 192.168.1.254
15:24
which one, ltsp or the firewall
15:24
<vagrantc>
ltsp server
15:25
<mymarrandy>
No, they both have one - wasn't thinking clearly
15:26
usually i get the response from the ltsp dhcp server as it hits it first, but occasionally i see a reponse from the firewall server with an offer and then the WS aborts
15:26
<vagrantc>
mymarrandy: you sure there aren't any cables connecting the two switches directly?
15:27
<mymarrandy>
No, they are separate, but your right, I will have to check again. Maybe I will have to start over.
15:29
if you mean the WS switch then no. It's a test system and the 2 WS connect to the switch that goes to the ltsp server internal port ie. 1 cable from the ltsp server to switch and 2 cables to the two servers
15:30J45p3r__ has quit IRC
15:30* vagrantc is clueless
15:30
<vagrantc>
i tried. i give up. :P
15:30
<mymarrandy>
they all sit next to each other, 3 cables in the switch, 2 to the WS and one to the internal ltsp server NIC
15:32
<bricode>
Humm. That's irritating. They don't actually say to copy/edit the lts.conf in the /etc dir.
15:33
<mymarrandy>
It puzzles me too - if I pull the external ltsp cable, the problem goes away. if I turn off the firewall dhcp, the problem goes away, if both DHCP servers are on, i see boot aborts and the logs show a response from the firewall DHCP so the ARP/broadcast requests are getting to the firewall DHCP server
15:34
and back obviously
15:36Skarmeth has quit IRC
15:38
<jammcq>
mymarrandy: are the 2 switches connected together?
15:38vagrantc has quit IRC
15:47
<mymarrandy>
not directly. one sits between the ltsp server and the clients, the other sits between the firewall and the ltsp server
15:47sbalneav has quit IRC
15:48
<mymarrandy>
I don't believe the day has gone - I need to go and i'll do some more searching and testing - I need to get this boot relible/consistent
16:01
tks for the hints - regards
16:01mymarrandy has quit IRC
16:08J45p3r has joined #ltsp
16:20bricode has left #ltsp
16:20bricode has joined #ltsp
16:29pscheie has quit IRC
16:35jammcq has quit IRC
17:01radoeka has quit IRC
17:02Stevec has joined #ltsp
17:05brich has quit IRC
17:06moose5435 has joined #ltsp
17:11Stevec has left #ltsp
17:32bill_c has quit IRC
17:45bobby_C has quit IRC
17:52bricode has quit IRC
18:20mauricio has joined #ltsp
18:26jammcq has joined #ltsp
18:26
<jammcq>
hey all
18:28
<mauricio>
hey jimm
18:29
alguien es de la universidad nacional de colombia?
18:30
<jammcq>
heh, no hable espaniol
18:38FernandoMM has joined #ltsp
18:39Stevec has joined #ltsp
18:49
<mauricio>
im very happy becouse i can bypass all the proxy from my University
18:53
i have hacked 1 server from my university and 1 ISP and 1 simple server uuuyuuuuyyjjjujj
19:01mauricio has quit IRC
19:06* msinhore
19:32Stevec has left #ltsp
19:35mauricio has joined #ltsp
20:00FernandoMM has quit IRC
20:12andresmujica has joined #ltsp
20:13J45p3r has quit IRC
20:46andresmujica has left #ltsp
20:48mauricio has quit IRC
21:02vagrantc has joined #ltsp
23:59tomcats has joined #LTSP