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

Request log from specific day:

Channel log from 14 March 2011 (all times are UTC)

00:20	alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
00:20	alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
00:43	alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
00:45	alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
00:46	shawnp0wers (~Adium@linuxjournal/staff/shawnp0wers) joined #ltsp.
00:50	shawnp0wers (~Adium@linuxjournal/staff/shawnp0wers) left irc: Client Quit
01:34	dobber (~dobber@89.190.197.77) joined #ltsp.
01:38	Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) joined #ltsp.
01:39	herytjb (~heryatmad@210.79.217.15) joined #ltsp.
01:39	Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) left irc: Client Quit
01:41	Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) joined #ltsp.
01:41	bobby_C (~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) joined #ltsp.
01:41	herytjb (~heryatmad@210.79.217.15) left irc: Remote host closed the connection
01:43	herytjb (~heryatmad@210.79.217.15) joined #ltsp.
01:44	herytjb (~heryatmad@210.79.217.15) left irc: Read error: Connection reset by peer
01:46	herytjb (~heryatmad@210.79.217.15) joined #ltsp.
01:47	herytjb (~heryatmad@210.79.217.15) left irc: Read error: Connection reset by peer
01:48	herytjb (~heryatmad@210.79.217.15) joined #ltsp.
02:04	mrcarrot (~lasse@86-60-154-229-dyn-dsl.ssp.fi) joined #ltsp.
02:05	<mrcarrot> with ubuntu 10.10 i can not get language choice to work with ldm... the list is empty even though i have locales installed
02:06	i have locales generated for en_US.UTF-8, sv_FI.UTF-8, fi_FI.UTF-8
02:06	still, nothing in the list
02:15	<alkisg> !localxterm
02:15	Darn the bot's gone
02:15	Sit on a client. Run: ltsp-localapps xterm. An xterm will open.
02:15	On that xterm, run: nc server 9571
02:15	Did you get a list of locales?
02:20	<mrcarrot> nope, i did not get
02:20	what am i missing when i am not getting a list?
02:22	<alkisg> Now sit on the server, and try: nc localhost 9571
02:22	Did you get a list of locales?
02:25	<mrcarrot> nope, still nothing
02:26	<alkisg> OK, now on the server run: ldminfod
02:27	Got a list?
02:27	<mrcarrot> yes
02:27	<alkisg> grep ldminfod /etc/inetd.conf
02:28	<mrcarrot> ah, so it is a service not turned on... yeah, it is commented out
02:29	<alkisg> OK uncomment and run sudo invoke-rc.d openbsd-inetd restart
02:29	<mrcarrot> thank you very much!!
02:30	<alkisg> If it was turned off automatically, file a bug
02:30	You're welcome
02:30	<mrcarrot> it must have been a bug...
02:36	Henning1 (~henning@p508A2196.dip.t-dialin.net) joined #ltsp.
02:36	Da-Geek (~Da-Geek@nat/redhat/x-ucnsbjkyokishjeu) joined #ltsp.
02:43	<mrcarrot> okay, another problem: i once added by mistake one locale, that should not be in the list from ldminfod. even though i have removed it from system, it still appears there
02:44	what files does really ldminfod read?
02:44	<alkisg> locale -a
02:49	Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) left irc: Quit: I Leave
02:51	<mrcarrot> thanks, i solved it
02:53	cyberorg (~cyberorg@opensuse/member/Cyberorg) left irc: Ping timeout: 255 seconds
02:57	cyberorg (~cyberorg@opensuse/member/Cyberorg) joined #ltsp.
03:03	ogra (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
03:03	ogra (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Changing host
03:03	ogra (~ogra@ubuntu/member/ogra) joined #ltsp.
03:16	<Henning1> ltsp 5.2.1 on Ubuntu 10.04, HP laptop ze5700 as client, I'm unable to connect a local printer via USB, Device not recognized at all when plugged in, Printer works fine when connected to Ubuntu installed on local hard drive, USB Thumb drives work fine when using the machine as ltsp client
03:18	tried to add module def MODULE_01=usblp.ko, PRINTER_0_TYPE=U, PRINTER_0_DEVICE=/dev/lp0 and PRINTER_0_PORT=9100
03:18	Anything more I can check?
03:20	herytjb (~heryatmad@210.79.217.15) left irc: Quit: Ex-Chat
03:40	<muppis> Henning1, check is there anyone listening port 9100 at clientside.
03:44	<Henning1> There isn't. Neither on the LTPS itself nor on the client
03:45	<muppis> Did you use mac or IP in lts.conf?
03:47	<Henning1> mac
03:47	<muppis> Try IP.
03:48	<Henning1> trying, rebooting
03:50	Trixboxer (~Trixboxer@office.supportdepartment.net) joined #ltsp.
03:51	<Henning1> Had no effect
03:57	<muppis> You shouldn't need usblp.ko module defined in lts.conf
03:57	garymc (~chatzilla@host81-148-15-59.in-addr.btopenworld.com) joined #ltsp.
03:57	mrcarrot (lasse@86-60-154-229-dyn-dsl.ssp.fi) left #ltsp.
04:00	Nick change: zz_evil_root -> evil_root
04:01	Nick change: evil_root -> zz_evil_root
04:03	zamba (marius@flage.org) left irc: Ping timeout: 255 seconds
04:04	<Henning1> Tried it without the module def in the first place. Removed option again, rebooted, no change. Also tried adding all other printer relevant options to the default section
04:05	The client need kernel option "nomodset" when booted as ltsp client. There's no chance that this has something to with the issue?
04:08	<muppis> Hmph. Couldn't not connect my virtual LTSP enviroment, so can't check required daemon to neede be running in client.
04:22	andygraybeal (~andy.gray@obsidian.casanueva.com) left irc: Remote host closed the connection
04:31	zamba (marius@flage.org) joined #ltsp.
04:56	<Henning1> Well, guess we're giving up on that one for today. I'll try it again on another day. Thanks for your help though.
04:56	Henning1 (henning@p508A2196.dip.t-dialin.net) left #ltsp.
05:20	otavio (~otavio@debian/developer/otavio) joined #ltsp.
05:22	garymc (~chatzilla@host81-148-15-59.in-addr.btopenworld.com) left irc: Ping timeout: 246 seconds
05:26	otavio (~otavio@debian/developer/otavio) left irc: Quit: leaving
05:26	otavio (~otavio@debian/developer/otavio) joined #ltsp.
05:30	Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) left irc: Quit: KVIrc Insomnia 4.0.2, revision: 4740, sources date: 20100627, built on: 2010-08-08 18:29:00 UTC http://www.kvirc.net/
05:33	Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) joined #ltsp.
05:41	garymc (~chatzilla@host81-148-15-59.in-addr.btopenworld.com) joined #ltsp.
05:47	ogra (~ogra@ubuntu/member/ogra) left irc: Excess Flood
05:48	ogra (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
05:48	ogra (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Changing host
05:48	ogra (~ogra@ubuntu/member/ogra) joined #ltsp.
05:48	andygraybeal (~andy.gray@obsidian.casanueva.com) joined #ltsp.
05:51	<garymc> Anyone know if this is a fix for transfered calls not showing or even recording at all? http://www.freepbx.org/forum/freepbx/users/call-monitoring-stops-when-call-is-tranferred-internally#comment-26562
05:52	wrong room sorry
05:54	garymc (~chatzilla@host81-148-15-59.in-addr.btopenworld.com) left irc: Quit: ChatZilla 0.9.86 [Firefox 3.6.15/20110303024001]
06:02	alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
06:09	ogra (~ogra@ubuntu/member/ogra) left irc: Excess Flood
06:10	ogra (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
06:10	Nick change: ogra -> Guest42034
06:10	Guest42034 (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Changing host
06:10	Guest42034 (~ogra@ubuntu/member/ogra) joined #ltsp.
06:11	Nick change: Guest42034 -> ogra_
06:15	cyberorg (~cyberorg@opensuse/member/Cyberorg) left irc: Remote host closed the connection
06:20	Gadi (~romm@ool-18bbe47a.static.optonline.net) joined #ltsp.
06:25	otavio (~otavio@debian/developer/otavio) left irc: Ping timeout: 252 seconds
06:27	otavio (~otavio@189.114.111.55) joined #ltsp.
06:27	otavio (~otavio@189.114.111.55) left irc: Changing host
06:27	otavio (~otavio@debian/developer/otavio) joined #ltsp.
06:27	otavio (~otavio@debian/developer/otavio) left irc: Client Quit
06:27	otavio (~otavio@189.114.111.55) joined #ltsp.
06:27	otavio (~otavio@189.114.111.55) left irc: Changing host
06:27	otavio (~otavio@debian/developer/otavio) joined #ltsp.
06:29	otavio (~otavio@debian/developer/otavio) left irc: Client Quit
06:29	otavio (~otavio@debian/developer/otavio) joined #ltsp.
06:39	cyberorg (~cyberorg@opensuse/member/Cyberorg) joined #ltsp.
06:49	markit (~marco@adsl-156-149.38-151.net24.it) joined #ltsp.
06:52	ggsict (~GRAVESEND@194.80.20.10) joined #ltsp.
06:52	matt___ (4b909aa5@gateway/web/freenode/ip.75.144.154.165) left irc: Quit: Page closed
06:57	shawnp0wers (~Adium@linuxjournal/staff/shawnp0wers) joined #ltsp.
07:00	<ggsict> New here. I'm not sure how to use this correctly but here goes...Having trouble with ltsp subnet on a larger windows domian. The ltsp server I have set up as a sub net is working fine except I can't log onto the windows domain from the clients. My ltsp server is joined to the domain and I can log-on to the domain from the ltsp server. I can log onto the ltsp server (as local user) from a client and I can ping the whole network, browse the web etc. I can't l
07:00	og directly onto the domain via the clients. My ltsp server has 2 nics; one connecting it to the domain (static IP) and the other pumping out dhcpd to a switch that my clients connect to. I have NAT working. Can anybody tell me where I'm going wrong? Thanks
07:01	a bunch of that text went missing
07:02	I'm new here and not sure how to use the service
07:10	drdata (~drdata@pool-173-57-189-158.dllstx.fios.verizon.net) left irc: Ping timeout: 260 seconds
07:15	alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
07:15	andygraybeal (~andy.gray@obsidian.casanueva.com) left irc: Quit: Ex-Chat
07:18	shawnp0wers (~Adium@linuxjournal/staff/shawnp0wers) left irc: Quit: Leaving.
07:25	komunista (~slavko@adsl-195-098-015-248.dynamic.nextra.sk) joined #ltsp.
07:37	alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
07:38	shawnp0wers (~Adium@linuxjournal/staff/shawnp0wers) joined #ltsp.
07:40	Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) left irc: Quit: KVIrc Insomnia 4.0.2, revision: 4740, sources date: 20100627, built on: 2010-08-08 18:29:00 UTC http://www.kvirc.net/
07:45	Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) joined #ltsp.
07:53	ggsict (~GRAVESEND@194.80.20.10) left irc: Quit: Leaving
07:59	Roasted_ (~jason@206.82.22.190) joined #ltsp.
07:59	MorningSon (~MorningSo@cpe-70-114-21-95.satx.res.rr.com) joined #ltsp.
07:59	<Roasted_> morning, fellas
07:59	shawnp0wers (~Adium@linuxjournal/staff/shawnp0wers) left irc: Ping timeout: 260 seconds
08:04	dobber (~dobber@89.190.197.77) left irc: Remote host closed the connection
08:09	dobber (~dobber@89.190.197.77) joined #ltsp.
08:19	staffencasa (~staffenca@128-193-151-251.oregonstate.edu) joined #ltsp.
08:32	befrenchy (8e2e1f1e@gateway/web/freenode/ip.142.46.31.30) joined #ltsp.
08:34	<befrenchy> good day, does anyone have experience setting LTS clients as diskless clients? Just installed LTS server with default config and client starts with GUI login. I would like insteas to have the client boot and start rdesktop or a shell at startup but the lts.conf file doesn't seem to be read by the client
08:35	maybe i missed something??
08:40	anybody done this before?
08:41	would just like to know how to change the client so that it doesn't give me the GUI login but instead launch an application such as rdesktop or a shell as defined in the lts.conf file
08:41	<markit> befrenchy: I've a sort of ltsp server that is used by thin clients to rdesktop against a win server
08:41	befrenchy: what distro are you using? are you sure you are editing the right lts.conf?
08:41	<befrenchy> markit: ok, cool
08:42	markit: using debian 6
08:43	markit: file path is /opt/ltsp/i386/etc/lts.conf
08:44	markit: got this to work with ubuntu 10.10 but /proc/bus/usb is no longer available which my application depends on, so i tried Debian instead
08:44	<markit> SCREEN_07 = ldm
08:44	SCREEN_08 = rdesktop -f -k it 192.168.1.5
08:44	in the [default] section
08:44	of course, you must have rdesktop installed on the server
08:45	LTSP_CONFIG=True
08:45	is also a parameter I've set
08:45	in debian 5
08:45	<befrenchy> markit: is that the only thing you modified from the default install?
08:45	<markit> in that file, is the only content is not remarked
08:46	btw, rdesktop must be installed in CHROOT
08:46	not in the server, I was wrong
08:46	<befrenchy> markit: ok, i gathered that
08:47	markit: is the gui login, the normal client behavior?
08:47	<markit> this way the user has the thin client boot and then is directly on the Win(EVILEMPIRE) login screen of server 192.168.1.5
08:48	<befrenchy> markit: ok, i'll verify theat rdesktop is indeed installed in chroot and will make modifications to the lts.conf file and see what happens, thanks
08:48	<markit> you are welcome
08:56	<befrenchy> markit: ok, checked that rdesktop is installed. made the changes to the lts.conf file to connect to my server. Rebooted the client but it still comes up with the gui login screen with blue screen background with LTSP.org in yellow writing
08:56	i must have missed a step
09:01	<markit> befrenchy: just for curiosity
09:02	try find / -iname lts.conf
09:02	<befrenchy> markit: ok
09:02	<markit> the /opt/ltsp/i386/etc/lts.conf should be the right one to modify for debian
09:03	<befrenchy> markit: that's the only one
09:03	<markit> in debian there should still be nfs and not NBD, so no rebuild of the image is necessary
09:03	could please pastebin the file?
09:04	<befrenchy> markit: sorry, did that once but forget how to do it again
09:05	<markit> befrenchy: go to http://pastebin.com/ and paste the content of lts.conf
09:05	select a reasonable "paste expiration"
09:05	and press "submit", then come here and paste the URL only
09:05	so I can go there and see
09:06	befrenchy: of course you are editing lts.conf and not ltsp.conf (common mistake of tired people ;))
09:06	<befrenchy> markit: correct
09:07	<markit> btw, if you press ctrl+alt+F8 on the client, does it change screen to the rdesktop login?
09:07	my notes are a bit obscure on this regard, don't know if my setup works only with debian and debian fixed it
09:07	<befrenchy> markit: http://pastebin.com/ypj9ExUA
09:08	Da-Geek (~Da-Geek@nat/redhat/x-ucnsbjkyokishjeu) left irc: Quit: Leaving
09:08	<befrenchy> markit: ctrl+alt+F8 does nothing
09:09	<markit> vdi-it1 maybe is not resolved by the client... try to put the IP
09:09	<befrenchy> markit: tried that
09:09	<markit> other than this, I've no idea :(
09:09	<befrenchy> markit: weird, with ubuntu, i just had to modify the lts.conf file and it worked right away
09:10	markit: i even tried to SCREEN_03=shell and that didn't even work
09:11	markit: was just trying to start a shell
09:12	klausade (~klaus@cm-84.215.171.127.getinternet.no) joined #ltsp.
09:12	<markit> seems that the file is ignored... are permissions ok?
09:13	I've: -rw-r--r-- 1 root root 803 1 apr 2010 /opt/ltsp/i386/etc/lts.conf
09:13	<befrenchy> markit: exact same here
09:14	<markit> reboot the server? :)
09:14	<abeehc> :(
09:14	<markit> lol, I know...
09:14	<befrenchy> markit: exactly what i thought about the file being ignored but not sure why. Could it have something to so with the thin client vs diskless client configuration?
09:14	<markit> urgh, I've no idea about this stuff
09:14	I was thinking about only thin client
09:15	<befrenchy> markit: ok here goes a reboot....
09:15	<markit> a "thin client only", if you also have fat client i've no idea
09:15	I think they have 2 separate lts.conf, but never used it
09:15	<befrenchy> markit: i would like the processing to happen on the client instead of the server
09:15	<markit> befrenchy: I think is called "fat client" setup
09:16	<befrenchy> markit: for that to happen i read that it needs to be setup as a diskless client
09:16	<markit> I'm going to test it in a near future (1 month), never do so far
09:16	<befrenchy> markit: but anyway, doesn't explain why the conf file it being ignored
09:16	<Gadi> befrenchy: your rdesktop line should have doublequotes around it
09:16	"rdesktop .... "
09:16	<befrenchy> gadi: oh
09:17	<Gadi> any value that has spaces needs to be dublequoted
09:17	<befrenchy> Gadi: is that the case for any command? ie "shell"
09:17	<Gadi> no - just any value with spaces
09:17	also, I don't think debian can run anything on a higher vt than 7
09:17	<befrenchy> Gadi: i thought if i put in a line like SCREEN_03=shell that it should start a shell at startup
09:18	<Gadi> or maybe it only likes higher than 7
09:18	I forget
09:18	<markit> Gadi: mine is not double quoted but works
09:18	<befrenchy> Gadi: lol, ok. Which vt are u using?
09:18	<Gadi> I do not use debian
09:19	but, I know debian has an issue like that
09:19	<markit> btw, I have debian 4
09:19	<Gadi> because it runs a getty on the first 6 vts
09:20	<befrenchy> Gadi: any way around not to load the gui login?
09:20	<Gadi> if you set rdesktop, ldm won't run
09:20	ldm is just the default
09:21	<Roasted_> gadi
09:21	I love you
09:21	<Gadi> dude, Im married
09:21	<abeehc> dodged
09:21	<Roasted_> :(
09:22	<befrenchy> Gadi: any sort of logging on the client side to see what's happening?
09:23	<Gadi> befrenchy: sure - can you get to a shell on the client?
09:23	<befrenchy> Gadi: that's also a problem :(, it won't let me open a terminal window once on the desktop
09:23	<Gadi> why not?
09:24	<befrenchy> Gadi: there is a "Root Terminal" launcher on the desktop but it doesn't seem to work when i click on it?
09:25	<Gadi> how about just a regular terminal?
09:25	<befrenchy> Gadi: what would be the syntax to launch a regular terminal?
09:25	<Gadi> are you ingnome?
09:25	gnome
09:25	?
09:25	<befrenchy> Gadi: yes
09:26	<Gadi> wait - syntax? So you have a terminal window open?
09:26	Or are you going to alt-f2 to get a run command thingy
09:26	<befrenchy> Gadi: was going to create a launcher or shortcut
09:26	<Gadi> ah
09:26	try: gnome-terminal
09:27	that will get you a terminal running on the server. If you lave ltsp-localapps on there, you can then type: ltsp-localapps xterm
09:27	to get a local xterm
09:27	but, Im not sure how debian is set up
09:27	vagrantc is our resident Debian guy
09:27	at least he's the packager
09:27	<befrenchy> Gadi: failed to execute child process (no suh file or directory)
09:28	<Roasted_> Is it normal when an LTSP server is on the windows domain to HAVE to type two backslashes when logging in? Example - DOMAIN\\Steve_Jobs.
09:28	On the server itself it works as DOMAIN\Steve_Jobs. But on the clients I need 2 \\
09:28	<Gadi> Roasted_: yeah, that's a likewise qwirk -> set likewise to "use default domain" and you will only need username
09:29	<Roasted_> Gadi, oh, no kidding?
09:29	trying to remember how to open the GUI
09:29	<Gadi> yeah, its because ldm runs ssh user@server
09:29	<Roasted_> I installed version 6 which didnt install a GUI entry in my menu
09:29	<Gadi> and if user has a backslash, it needs to be escaped
09:29	in all the likewise docs, they use single quotes around user
09:29	we dont
09:29	:)
09:30	<Roasted_> hm
09:30	I wonder how I can open that dang gui
09:30	I totally forget
09:30	<Gadi> Roasted_: open the likewise administrators docs
09:30	<Roasted_> I joined this box via terminal
09:30	<Gadi> they give you the command to do it
09:30	(the command changed between versions)
09:31	<Roasted_> lol
09:31	thsi PDF is 178 pages
09:31	<Gadi> search for defaultdomain
09:32	<Roasted_> yeah Im finding a few entries here
09:32	its an lwconfig command?
09:32	I figured it was a GUI setting in the little menu gizmo they have.
09:32	<Gadi> yeah, whatever it says
09:33	dunno never used the gui myself
09:33	<Roasted_> so if I set this but I need to log in as local admin..............
09:33	<Gadi> it will see local accounts and domain accounts
09:34	and favor the local ones, I think, if there is a name conflict
09:34	<Roasted_> k good
09:34	cause we have local admin and network admin
09:34	but we dont use network admin
09:34	it exists, but its disabled I think
09:34	however I use local admin quite a lot
09:34	<Gadi> you should be fine
09:34	but, do this
09:34	do: sudo -i
09:34	<Roasted_> looks like I have some reading to do though. Im getting no file or directory found when I run these commands
09:34	<Gadi> become root
09:35	make your changes
09:35	and then try logging in in another terminal
09:35	so you can revert as needed
09:35	you need the full path
09:35	to the command
09:35	because LW6 is in /opt somewhere
09:35	markit (~marco@adsl-156-149.38-151.net24.it) left irc: Remote host closed the connection
09:35	<Gadi> not in the default PATH (/usr/bin)
09:36	<Roasted_> be nice if it said that
09:36	:P
09:37	annnnnnnd same thing
09:37	fk
09:37	<Gadi> then it would be 180 pages long!
09:37	;)
09:37	<Roasted_> so be it
09:39	<Gadi> Roasted_: after you become root, do: export PATH=$PATH:/opt/likewise/bin
09:39	then, you can just type the command
09:39	<Roasted_> already in that dir
09:39	yeah
09:39	I got it but Im not sure where to put in our domain
09:39	wait..
09:39	dobber (~dobber@89.190.197.77) left irc: Remote host closed the connection
09:39	<Roasted_> yeah
09:39	failed
09:40	<Gadi> it is a boolean
09:40	<Roasted_> I just don't know where to put in our actual domain name
09:40	<Gadi> true/false
09:40	<Roasted_> yeah
09:40	I see that part
09:40	don't I have to put in our domain name though?
09:40	or does it somehow auto-assume?
09:40	<Gadi> so, you never put in your domain
09:40	<Roasted_> oh
09:40	well damn
09:40	<Gadi> it uses the one you are joined to
09:40	<Roasted_> gotcha
09:40	<Gadi> and assumes that is the default
09:40	<Roasted_> so I just run ./lwconfig --detail AssumeDefaultDomain and then again with true
09:40	and that's it
09:41	<Gadi> if you want to login to that domain as a user from another domain in the forest, you would need the domain as part of the username
09:41	right - lwconfig AssumeDefaultDomain true
09:41	something like that
09:42	<abeehc> i ahven't had time to look
09:42	<Gadi> -- detail is to check the value
09:42	<abeehc> anyone have thoughts on how lw works with fat clients?
09:42	<Roasted_> k
09:42	trying it now
09:42	<abeehc> seems like it could be a trick
09:42	<Gadi> abeehc: ltsp fat clients use ssh auth, so you simply join the server to the domain and done
09:42	<abeehc> awesome
09:43	<Roasted_> is a reboot needed?
09:43	<Gadi> Roasted_: no
09:43	<Roasted_> well
09:43	its failing
09:43	<Gadi> does --detail confirm that the value is set to true?
09:44	<Roasted_> its false
09:44	wonder why
09:44	I ran true
09:45	<Gadi> /opt/likewise/bin/lwconfig AssumeDefaultDomain true
09:45	just like that
09:45	as root
09:45	<Roasted_> I need ./ in front of lwconfig
09:45	right
09:45	alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
09:46	<Roasted_> if I run without, it errors out
09:46	it says to run with as part of the documentation
09:46	yeah. keeps bombing out.
09:46	whether under sudo -i or just regular sudo ./lwconfig etc
09:47	<Gadi> bombing out means?
09:47	<Roasted_> it keeps returning as false
09:47	even if I use true in the first command
09:47	<Gadi> no errors when you run it, tho?
09:47	<Roasted_> if I run ./lwconfig
09:47	no
09:47	if I run lwconfig
09:47	yes
09:47	<Gadi> and when you:
09:47	sudo -i
09:47	/opt/likewise/bin/lwconfig AssumeDefaultDomain true
09:48	/opt/likewise/bin/lwconfig --detail AssumeDefaultDomain
09:48	<alkisg> Gadi: vagrantc wanted to contact you about rev 1802 breaking run_parts_list..
09:48	<Roasted_> gadi
09:48	bingo
09:48	this documentation sucks
09:48	It says to use ./lwconfig
09:48	it says NOTHING like what you just told me
09:49	<Gadi> well, they should be equivalent if you did a : cd /opt/likewise/bin
09:49	<Roasted_> I ran sudo -i and then CD'd to /opt/likewise/bin
09:49	and ran ./lwconfig --detail AssumeDefaultDomain true
09:50	and it kept returning false, but no errors
09:50	thats what the documentation said to do
09:50	but what YOU told me to do worked
09:50	oh well, I'm taking it down in my own notes to keep handy
09:50	<Gadi> :)
09:50	we'll fight the man together!
09:50	<Roasted_> <3
09:51	<Gadi> alkisg: good to know, because his that asterisk was breaking on me
09:51	alkisg: I think we need to do something else then for our find
09:52	<alkisg> Gadi, in which cases was it broken for you?
09:52	(and one way would be to actually call run-parts, no?)
09:52	<Gadi> good questions
09:53	<alkisg> run-parts -L --regex or something
09:53	<Gadi> :)
09:53	<alkisg> :D
09:53	<Gadi> I think this waas one of those efforts to make it distro-independent
09:53	bec not all distros had run-parts
09:53	<alkisg> Really? Man these distros are strange beasts :P
09:54	<Gadi> all I know is it was driving me crazy until I tracked down the * as being the problem
09:54	and as soon as I dereferenced it, it worked well everywhere
09:54	<alkisg> run-parts ==> Copyright (C) 1994 Ian Jackson, how long does it take to spread to all distros? :D
09:54	It did?
09:54	<Gadi> yeah
09:54	I specifically tested it everywhere
09:54	(on Ubuntu)
09:55	<alkisg> For me, run-parts-list XS on Lucid returns empty
09:55	<Gadi> and it didnt adversely affect anything
09:55	<highvoltage> in 1994 I was still using Windows 3.1 and MS-DOS 6.0 :(
09:55	<alkisg> run_parts_list /opt/ltsp/i386/usr/share/ltsp/screen-session.d/ XS
09:55	==> empty, with rev 1802
09:55	==> normal list, without it
09:55	<Gadi> huh
09:56	I know I tested it
09:56	specifically on Lucid
09:56	and I believe I have it working here
09:56	can you test actually in a chroot?
09:57	or from a shell on a client?
09:57	<alkisg> Not right now, not enough time, but I could test later on
09:57	<Gadi> ok, me too
09:57	<alkisg> But vagrantc tested it on a (debian) chroot and it was broken for him
09:57	That's what raised the subject
09:58	<Gadi> k
10:03	<befrenchy> has anyone tested LTSP5 with debian 6?
10:03	Gadi: could my problem be that I'm using version 6?
10:07	Gadi: got the terminal window to start, what did you want me to do?
10:07	<Gadi> befrenchy: does: ltsp-localapps xterm
10:07	bring up an xterm?
10:08	<befrenchy> Gadi: that's how i opened it
10:08	<Gadi> ah
10:08	ok, so you have a local xterm
10:08	<befrenchy> Gadi: looks like it
10:08	<Gadi> great, type: getltscfg -a
10:09	vagrantc (~vagrant@c-24-21-191-93.hsd1.or.comcast.net) joined #ltsp.
10:10	<befrenchy> Gadi: I get LTSP_CONFIG="True" and export LTSP_CONFIG
10:10	<Gadi> thats all?
10:10	<befrenchy> Gadi: yep
10:11	<Gadi> cat /etc/lts.conf
10:11	does that look like the one you created?
10:11	<befrenchy> Gadi: no its's not
10:11	<Gadi> aha!
10:11	<befrenchy> Gadi: so what does that tell you?
10:12	<Gadi> is the one you created in /opt/ltsp/i386/etc/lts.conf ro /var/lib/tftpboot/ltsp/i386/lts.conf?
10:12	*or
10:12	<befrenchy> Gadi: /opt/ltsp/i386/etc/lts.conf
10:12	<vagrantc> Gadi: your recent commit to ltsp-common-function borked LTSP, at least on debian... what were you trying to fix?
10:12	Gadi: commit 1802
10:13	<Gadi> vagrantc: yeah, I heard I have some 'slainin to do
10:13	1 sec
10:13	<befrenchy> Gadi: There isn't one under/ var/lib/tfpboot/ltsp/i386 like ubuntu
10:13	* vagrantc hopes 'slainin isn't too awful
10:13	<Gadi> befrenchy: ok, and this is NFS, right?
10:14	vagrantc: meet befrenchy btw
10:14	<befrenchy> Gadi: yes
10:14	<Gadi> vagrantc: happy new debian user
10:14	:)
10:14	* vagrantc waves to befrenchy
10:14	<vagrantc> ah good, happy. that's the way it ought to be
10:14	<befrenchy> vagrantc: greetings
10:14	<Gadi> vagrantc: seems his changes to lts.conf are not being picked up on the client
10:14	<befrenchy> wouldn't say happy, frustrated maybe :)
10:14	<Gadi> quite bizarre for NFS, no?
10:15	<vagrantc> yes, quite bizarre indeed
10:15	* Gadi kicks befrenchy under the table
10:15	<vagrantc> after a reboot?
10:15	<befrenchy> several
10:15	debian 6 make a difference?
10:16	<Gadi> befrenchy: you only have one chroot, right?
10:16	<vagrantc> befrenchy: squeeze should be good. it's been a while since i've worked with lenny without using ltsp backports
10:16	<Gadi> not like you have an amd64 and an i386 or some such
10:16	<befrenchy> Gadi: yep as far as i know
10:16	<vagrantc> befrenchy: fatclients, or regular thin clients?
10:17	<Gadi> regular
10:17	<befrenchy> vagrantc: well was looking to do diskless
10:17	<vagrantc> i did run into some issues with using FAT_RAM_THRESHOLD (fixed in ltsp 5.2.6)
10:17	befrenchy: they're all diskless, for the most part :)
10:18	<befrenchy> vagrantc: ok
10:18	<vagrantc> befrenchy: got a paste of your lts.conf?
10:18	<Gadi> vagrantc: his lts.conf doesn't show up
10:18	<vagrantc> and the output of ltsp-innfo ?
10:18	<Gadi> he has an ltsp-localapps xterm open
10:18	<vagrantc> it's just not there?
10:18	<Gadi> and a cat/etc/lts.conf is the default one
10:18	<befrenchy> vagrantc: http://pastebin.com/ypj9ExUA
10:18	<Gadi> correct, befrenchy?
10:19	<befrenchy> Gadi: /etc/lts.conf doesn't show my config
10:19	<vagrantc> that's most unusual...
10:19	befrenchy: if you mount the NFS volume on the server, does it?
10:20	befrenchy: mount 127.0.0.1:/opt/ltsp /mnt/or/somewhere
10:20	cat /mnt/or/somewhere/i386/etc/lts.conf
10:20	<befrenchy> vagrantc: exportfs shows /opt/ltsp <world>
10:21	vagrantc: you want me to mount it from the client?
10:21	<vagrantc> it should have some particular mount flags
10:21	befrenchy: no, from the server
10:22	your server's /etc/exports should contain:
10:22	.. /opt/ltsp/ *(ro,no_root_squash,async,no_subtree_check)
10:22	<befrenchy> vagrantc: yes it does mount
10:22	<vagrantc> befrenchy: and does it include your changes?
10:23	<befrenchy> vagrantc: under /etc/lts.conf?
10:23	<vagrantc> befrenchy: under /whereever/you/mounted/it/i386/etc/lts.conf
10:24	<befrenchy> vagrantc: i meant which changes are we talking about?
10:24	mikkel (~mikkel@80.71.132.15) joined #ltsp.
10:24	<Gadi> befrenchy: that file should be your modified lts.conf file
10:24	<vagrantc> befrenchy: you said the changes weren't reflected on the thin client ... so i'm testing if they work if you mount NFS manually
10:24	<befrenchy> vagrantc: ok , sorry changes are there
10:25	<vagrantc> befrenchy: diff /opt/ltsp/i386/etc/lts.conf /whereever/you/mounted/it/i386/etc/lts.conf
10:25	do they match?
10:25	they should not have any differences, unless something's really messed up
10:25	<befrenchy> vagrantc: same
10:26	<vagrantc> befrenchy: do you have an /opt/ltsp/images/i386.img ?
10:26	<befrenchy> vagrantc: yes
10:27	<vagrantc> befrenchy: could you paste /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default ?
10:27	<befrenchy> vagrantc: ok
10:28	<vagrantc> befrenchy: "have you now, or have you ever, run ltsp-update-image" ? :)
10:28	alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
10:28	<befrenchy> vagrantc: http://pastebin.com/wrkD8zx0
10:29	vagrantc: i thought i did
10:29	vagrantc: run it again?
10:29	<vagrantc> befrenchy: looks like you've configured your system to use NBD root ... which is possible on Debian, but not the default.
10:30	does ltsp-update-image mangle a bunch of configuration files whenever it gets run? if so, that behavior is really causing problems on debian...
10:30	<befrenchy> vagrantc: all default
10:31	<vagrantc> befrenchy: you didn't use any ltsp-build-client arguments, or follow ubuntu howtos or anything?
10:31	<befrenchy> vagrantc: no i didn't
10:31	<vagrantc> befrenchy: you should never need to run ltsp-update-image on debian, unless you know you want NBD
10:32	and i need to get it fixed upstream so it doesn't mangle everything whenever a user runs it... :(
10:32	<befrenchy> vagrantc: is that the problem then?
10:32	<vagrantc> befrenchy: run ltsp-update-image again, and your lts.conf options should be updated
10:32	<befrenchy> vagrantc: ok
10:33	<vagrantc> befrenchy: though if you continue to use NBD, then you'll want to put your lts.conf in /var/lib/tftpboot/ltsp/i386/lts.conf
10:33	befrenchy: alternately, we could explore switching you back to NFS
10:33	<befrenchy> vagrantc: what's prefered?
10:33	vagrantc: i don't really care as long as it works :)
10:34	vagrantc: but nfs would be nice if you don't have to run ltsp-update-image
10:34	<vagrantc> NBD requires running ltsp-update-image after most any changes to the chroot, though is faster than NFS. if you change things in the chroot, NFS is much easier, though a bit slower.
10:34	<befrenchy> vagrantc: how do we switch back?
10:34	<vagrantc> let's see what the damage is...
10:34	<befrenchy> vagrantc: ok currently updating
10:34	<vagrantc> befrenchy: any files in /opt/ltsp/i386/etc/ltsp/ ?
10:35	before we get too deep, could you run ltsp-info
10:35	and paste the results
10:35	<befrenchy> vagrantc: yes, update-kernels.conf
10:36	vagrantc: on the server?
10:36	<vagrantc> befrenchy: ok, what's in it?
10:36	befrenchy: yes, run ltsp-info on the server
10:36	befrenchy: i'll explicitly tell you to run in the chroot or from a thin client
10:37	if needed
10:37	<befrenchy> vagrantc: http://pastebin.com/S0PrujuA
10:37	vagrantc: ok
10:38	<vagrantc> befrenchy: ok... delete update-kernels.conf
10:38	<befrenchy> vagrantc: http://pastebin.com/wvFtdkCn
10:38	vagrantc: ok
10:39	<vagrantc> ah, ok. so you're running squeeze all around. good. :)
10:39	<befrenchy> vagrantc: yep
10:40	<vagrantc> befrenchy: ok, now we'll update the boot menu (as root) run ... ltsp-chroot /usr/share/ltsp/update-kernels ; ltsp-update-kernels
10:41	bobby_C (~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) left irc: Ping timeout: 248 seconds
10:41	<vagrantc> befrenchy: then, look at whats in /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default
10:43	<befrenchy> vagrantc: just to clarify, chroot then run ltsp-update-kernels?
10:43	vmassuchetto (~vmassuche@187.52.241.174) joined #ltsp.
10:44	<vagrantc> befrenchy: run the command exactly that i have there
10:44	befrenchy: two commands, really.
10:44	<vmassuchetto> im choosing the configuration for legacy desktop to act as ltsp clients... how far does it matter the processor power and ram memory size?
10:44	<vagrantc> befrenchy: ltsp-chroot /usr/share/ltsp/update-kernels ; ltsp-update-kernels
10:45	<befrenchy> vagrantc: done
10:45	<vagrantc> befrenchy: and what's in /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default ?
10:45	befrenchy: should have boot=nfs, amoung other things
10:46	<befrenchy> vagrantc: http://pastebin.com/0XKxtp24
10:46	<vagrantc> befrenchy: reboot your thin client ... should be good to go.
10:46	<befrenchy> vagrantc: ok
10:47	<vagrantc> bah. the check ltsp-update-image does is not in a configuration file, but in a package-shipped file.
10:47	<befrenchy> vagrantc: You've made my day :)
10:47	vagrantc: so where did i go wrong?
10:48	<vagrantc> befrenchy: ltsp-update-image pretty much blindly assumes you want to mangle all your configuration files just by virtue of running it
10:48	and a lot of non-debian documentation says to run it
10:48	and a lot of people assume you need to run it
10:48	gah.
10:48	<befrenchy> vagrantc: so in the future if i have to install anything in chroot, i don't have to update the image?
10:48	<vagrantc> it needs to be less stupid.
10:49	befrenchy: correct.
10:49	befrenchy: in fact, you should delete the image... you don't need the image at all.
10:50	<befrenchy> vagrantc: which image is that? the i386.img?
10:50	<vagrantc> befrenchy: yes.
10:50	<befrenchy> vagrantc: ok , will do.Thank you so much for your help!!
10:51	vagrantc: that's awsome
10:53	<vagrantc> wow. ltsp-update-image does a lot of ugly things ... it manually regenerates the pxelinux.cfg rather than simply regenerating it ... it doesn't have any checks for assigning ports of mangling the pxelinux.cfg ...
10:54	it needs a good code refactor or rewrite
10:54	<befrenchy> vagrantc: i'll staty away from it in the future :)
10:55	<vagrantc> befrenchy: though NBD root is faster, and does have some advantages...
10:55	<befrenchy> vagrantc: faster to boot?
10:56	vagrantc: fast is good but i'll see how it goes with nfs and determine if it's satisfactory
10:56	<vagrantc> the ltsp-update-image creates an NBD root with an essentially writeable filesystem layered on top (using aufs) ... whereas NFS has to manually list all the writeable directories
10:56	although alkisg said you can use aufs with NFS these days
10:56	<befrenchy> vagrantc: I'll start with nfs and see how it goes.
10:56	<vagrantc> sounds good.
10:56	<befrenchy> vagrantc: thanks again
10:57	<vagrantc> and if ever anyone tells you to run ltsp-update-image, you stare them in the eyes and just say no :)
10:57	(at least, if you're running debian)
10:58	i wondered why people mysteriously end up running NBD on debian... now i know.
10:59	<befrenchy> vagrantc: got it... :)
11:07	<vagrantc> sigh
11:07	hope to upload 5.2.6 to debian today...
11:09	Nick change: zz_evil_root -> evil_root
11:09	<komunista> vagrantc: hi
11:09	vagrantc: the pot will be updated?
11:13	vmassuchetto (~vmassuche@187.52.241.174) left irc: Quit: Saindo
11:16	<Roasted_> What's the common issue when you're on an LTSP box logged in as a domain user when it just magically stops responding to mouse/keyboard clicks, however the mouse continues to scroll around.
11:16	and of course it responds 10 mins later when I finally ask in here
11:16	wow
11:19	<abeehc> i'd guess network
11:19	could only guess
11:19	<Roasted_> I find that hard to believe, as my server and my test client are on the same switch.
11:19	<abeehc> short of actually posting some detail it's only a guess.
11:19	<Roasted_> what detail. as in logs?
11:20	<abeehc> that's where I'd start looking
11:20	dmesg on the client etc
11:20	<Roasted_> whats the path again?
11:20	<abeehc> same as any desktop machine i guess. there are many logs
11:21	<Roasted_> I also noticed my domain account on linux doesnt default to the bash terminal
11:21	I have $ instead
11:25	drdata (~drdata@tw2.udallas.edu) joined #ltsp.
11:27	<abeehc> that's kinda wierd maybe your skel is different or /etc/profile?
11:27	<vagrantc> komunista: today!
11:27	komunista: now!
11:27	:)
11:27	<abeehc> or maybe a symptom of fat clients i'm more familiar with ubuntu and thinclients
11:28	<vagrantc> Roasted_: what's a domain account?
11:29	<Roasted_> vagrantc, the box is part of a windows domain
11:29	domain accounts... etc
11:32	that way the users on the thin client end don't work off of accounts on the LTSP box. Instead, LTSP connects tot he domain, so I guess it acts as a pass through to active directory
11:33	<vagrantc> ah
11:33	<Roasted_> makes me a little scurred to deploy this but so far its worked great
11:33	no errors
11:34	<vagrantc> komunista: ok, pushed the updates for ltsp-trunk ... most languages still in sync
11:35	<Gadi> Roasted_: /opt/likewise/bin/lwconfig LoginShellTemplate "/bin/bash"
11:36	<Roasted_> gadi why are you such a genius
11:36	this is with sudo -i right
11:36	<Gadi> y
11:37	<Roasted_> testing now
11:41	seems as if I'm having some network issues now
11:42	it hung at pxe boot with boot: so I ran an update image command
11:42	now I get the splash screen but it wont give me the login screen
11:44	nevermind. gadi youre a genius.
11:45	Gadi, what was th ename of the shell I had before? It was a $ prompt.
11:45	<Gadi> /bin/sh
11:45	<vagrantc> probably implemented using dash
11:48	komunista: https://code.launchpad.net/~ltsp-upstream/ltsp/ldm-trunk and https://code.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/ are both updated
11:48	komunista: very few changes
11:50	Trixboxer (~Trixboxer@office.supportdepartment.net) left irc: Quit: "Achievement is not the end, its the beginning of new journey !!!"
11:53	<Gadi> vagrantc: I think I remember!
11:53	I think I remember what broke with that asterisk
11:53	I believe I had tried to create an S* file in screen-session.d/
11:54	and run_parts_list was never calling it
11:59	komunista (~slavko@adsl-195-098-015-248.dynamic.nextra.sk) left irc: Ping timeout: 250 seconds
12:00	Roasted_ (~jason@206.82.22.190) left irc: Changing host
12:00	Roasted_ (~jason@unaffiliated/roasted) joined #ltsp.
12:02	befrenchy (8e2e1f1e@gateway/web/freenode/ip.142.46.31.30) got netsplit.
12:02	<vagrantc> Gadi: it was missing almost everything with your patch :(
12:02	at least for me
12:04	<Gadi> which is weird, bec I tested it
12:04	ad nauseum
12:04	and I do see a difference from command line
12:04	when run on command line, yeah, it breaks
12:06	vagrantc: if you have a sec to check if an S* script in screen-session.d works, thatd be great
12:07	and by works, I mean on boot - not from c/l
12:08	rcc_ (~rcc@fw.acurrus.com) joined #ltsp.
12:09	<vagrantc> sure
12:09	Gadi: i only tested on boot
12:11	rcc_ (~rcc@fw.acurrus.com) left irc: Client Quit
12:12	GodFather (~rcc@fw.acurrus.com) joined #ltsp.
12:13	befrenchy (8e2e1f1e@gateway/web/freenode/ip.142.46.31.30) got lost in the net-split.
12:28	GodFather (~rcc@fw.acurrus.com) left irc: Quit: Ex-Chat
12:29	komunista (~slavko@adsl-195-098-015-248.dynamic.nextra.sk) joined #ltsp.
12:32	<vagrantc> komunista: if you were the previous translator, you'll get an email from me soonish.
12:32	<komunista> yes I am
12:36	only one message was changed from all 3 POTs...
12:40	<vagrantc> some of it's because not much has changed, and some of it is because we're not making new bits translateable, i think
12:56	LoveStorm (~Storm@203.78.122.56) joined #ltsp.
12:59	Nick change: evil_root -> zz_evil_root
13:00	<komunista> vagrantc: I get mail about update ldm translation now, IMHO some date/time (timeout?) information is missing in it...
13:03	Gadi (romm@ool-18bbe47a.static.optonline.net) left #ltsp.
13:05	<vagrantc> komunista: do you know which file it comes from? it's either not a translateable string or not on the list of files to check for translations
13:05	alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
13:07	<komunista> vagrantc: which file do you mean?
13:08	<vagrantc> komunista: yes... how do you know there's missing information?
13:09	<komunista> I meaan in mail, not in attached file :-)
13:09	*mean
13:09	<vagrantc> oh
13:09	komunista: ah, you mean a deadline?
13:10	<Roasted_> Question. Im on a 64 bit server, but 32 bit clients. I'm about to download google earth. Which deb do I get?32 or 64?
13:10	<vagrantc> komunista: i'd be picking a deadline out of the air ...
13:11	Roasted_: typically, you install all applications on the server
13:11	<Roasted_> that's what I thought
13:11	I just wasn't sure if I'd have to use 32b for the clients sake
13:11	<vagrantc> Roasted_: only if you're using localapps or fatclients would you ever install anything in the client environment
13:11	Roasted_: thin clients are effectively extra monitor/keyboard/mouse for the server.
13:12	<komunista> vagrantc: yes - my english is poor :-)
13:12	<Roasted_> vagrantc, I know, but I specially did a build image --arch i386 for the clients when I set up ltsp, so I just wanted to make sure.
13:12	<vagrantc>
13:13	<alkisg> Roasted_: 3d apps over the network work very poorly though. What are your client specs, ram and vga card?
13:13	<Roasted_> vagrantc, also, do you know of a way I can monitor whos doing what? I'm curious to know what processing power the thin clients are actually utilizing?
13:13	alkisg, I know they're poor, and I don't expect this to work that great. I just want to test it to see what works/doesnt work.
13:13	<vagrantc> Roasted_: top?
13:13	<Roasted_> vagrantc, top shows me the server only
13:14	<vagrantc> Roasted_: since all the processes are running on the server, you just use standard utilities to monitor who's taking up resources ... top on the comandline, there are plenty of GUI tools that work similarly
13:14	mistik1 (mistik1@unaffiliated/mistik1) left irc: Ping timeout: 248 seconds
13:14	<Roasted_> vagrantc, do other utilities show me what the thin client is utilizing?
13:14	<vagrantc> Roasted_: what are you trying to determine?
13:14	<Roasted_> I just want to see who's doing the legwork. I wnat to see how much the local resources on the thin clients are being utilized.
13:14	<vagrantc> Roasted_: how overworked the thin client is?
13:15	<Roasted_> I just want to see WHAT the thin client is doing.
13:15	WHAT its processor is doing, ram, etc.
13:15	<vagrantc> Roasted_: ltsp-localapps xterm ... and then run your commands on the thin client itself
13:15	<Roasted_> that command will show me?
13:15	<abeehc> a terminal
13:15	<vagrantc> that will open an xterm running on the actual client hardware
13:15	<Roasted_> okay
13:15	<vagrantc> from there, you run whatever commands you want
13:16	<Roasted_> I just got a little confused because I hvae a dual core/2gb ram server, and a single core 1gb ram client
13:16	and when I ran top on the thin client... I saw 2 gb ram and 2 cores
13:16	so I kenw I wasnt seeing the local hardware
13:16	<vagrantc> but when running localapps, you do need to install the commands you want to run on the thin client
13:16	things like top and such are already installed, most likely
13:16	<Roasted_> I havent set up localapps or anything.
13:17	<alkisg> vagrantc: once you had packaged gpxe, did you also happen to package ipxe?
13:17	<vagrantc> alkisg: seems like gPXE is dead...
13:17	alkisg: i gave iPXE a whirl... basically same thing
13:18	i mean, the code is essentially the same, only getting updates and such
13:18	<alkisg> Got any link, to save me the trouble of updating your older package?
13:18	(for your ipxe package)
13:18	<vagrantc> alkisg: ah. haven't really messed around with it much
13:18	<alkisg> Yes, I'm not sure what will happen with that fork though, people in IRC are still in #gpxe, not in ipxe
13:18	Yet the gpxe git is dead
13:19	<Roasted_> hm
13:19	google earth isnt even launching
13:19	on server or client
13:19	its like its a dead link
13:19	<alkisg> It needs 3d acceleration
13:19	<vagrantc> alkisg: daniel baumann decided to switch to iPXE ... and i haven't put any more work into it
13:19	<alkisg> Roasted_: Run it from a console to see the error messages
13:19	<vagrantc> alkisg: so i don't think we'll see gPXE in debian
13:20	<alkisg> Ah there's a branch attached to some ITP?
13:20	<Roasted_> googleearth and google-earth are doing nothing in terminal.
13:20	not sure what else it would be to launch
13:20	<vagrantc> alkisg: i've got it in a branch somewhere...
13:20	<abeehc> Roasted_: be aware what terminal you are running it in
13:21	* alkisg reads http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474034
13:21	<abeehc> wouldn't make sense to exectute on the server i'd guess
13:21	<vagrantc> alkisg: haven't touched it since early december
13:21	<Roasted_> shrug I thought it made sense. lol.
13:21	mistik1 (mistik1@unaffiliated/mistik1) joined #ltsp.
13:21	<Roasted_> the server SHOULD have the hardware to run it. its a 2 year old desktop.
13:21	<alkisg> The graphics card matters
13:21	<Roasted_> exactly
13:21	<alkisg> E.g. if it's nvidia, you'll need the proprietary driver
13:21	<Roasted_> we have google earth on these machines
13:22	<alkisg> So if you didn't install it, don't expect 3d
13:22	<Roasted_> I thought I did. let me check.
13:22	It's an ATI card I believe.
13:22	<alkisg> `sudo apt-get install mesa-utils && glxgears` will show you if you can run 3d apps
13:22	<Roasted_> dangit, alkisg.
13:22	stop being right all the time
13:22	<alkisg> I try hard, but I can't :P :D
13:23	<Roasted_> do you think this would allow the client to run it then, even if its poor?
13:24	<alkisg> Yes, but you'll see about 1-2 fps
13:24	So poor that it isn't worth it at all
13:24	<Roasted_> yeah, I might end up uninstalling it.
13:24	<alkisg> If you install it on the chroot though, it will run just fine
13:24	<Roasted_> but it runs on our other thin client setup, which sucks horribly in performance compared to LTSP. So I'm curious to see.
13:24	<alkisg> (with nvidia + 1 gb ram)
13:24	<Roasted_> okay, dumb question
13:25	what is the definition of chroot
13:25	I've heard it referenced several times.
13:25	<vagrantc> Roasted_: the files in /opt/ltsp/i386 are a chroot
13:25	<alkisg> It's the virtual disk for your thin clients, in /opt/ltsp/i386
13:25	Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) joined #ltsp.
13:25	<Roasted_> so when I update-image --arch i386, its hitting chroot
13:25	<vagrantc> it's taking the chroot environment, and turning it into an image in /opt/ltsp/images/*.img
13:25	<Roasted_> gotcha
13:26	so installing an app to chroot means, you're making it a local app
13:26	local to the thin client
13:26	<vagrantc> you're making it available as a local app, you're not necessarily configuring it to run as a local app
13:27	<Roasted_> how would I go about installing it as a local app
13:28	driver in, server rebooted. still aint launching g-earth. odd.
13:29	ogra_ (~ogra@ubuntu/member/ogra) left irc: Ping timeout: 250 seconds
13:30	ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
13:50	Roasted_ (~jason@unaffiliated/roasted) left irc: Ping timeout: 255 seconds
13:51	<vagrantc> hrm. apparently S scripts are borked.
13:54	aha.
13:58	seems to depend on what directory you run it from, and if any files in that directory begin with that letter
14:01	<alkisg> Why not switch to calling run-parts -L --regex? Isn't that available to all distros?
14:01	And with that, gn all :)
14:01	alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
14:05	Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) left irc: Quit: KVIrc Insomnia 4.0.2, revision: 4740, sources date: 20100627, built on: 2010-08-08 18:29:00 UTC http://www.kvirc.net/
14:50	bobby_C (~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) joined #ltsp.
14:52	drdata (~drdata@tw2.udallas.edu) left irc: Ping timeout: 255 seconds
14:55	Nick change: zz_evil_root -> evil_root
15:02	Nick change: evil_root -> zz_evil_root
15:05	Nick change: zz_evil_root -> evil_root
15:06	Nick change: evil_root -> zz_evil_root
15:10	alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
15:16	<vagrantc> hmmm... well, i've got a patch that seems to work
15:21	Nick change: ogra_ -> ogra
15:21	ogra (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Changing host
15:21	ogra (~ogra@ubuntu/member/ogra) joined #ltsp.
15:30	<vagrantc> hrm. i thought i confirmed gadi's problem ... but turns out i didn't ... just have no idea where screen-session.d/S* scripts send stderr/stdout/stdin goes
15:34	<alkisg> vagrantc: what was Gadi's problem?
15:34	<vagrantc> alkisg: screen-session.d/S* scripts weren't getting run
15:35	<alkisg> Due to run_parts_list?!
15:35	<vagrantc> yes
15:35	at least, that was the claim
15:35	he introduced a bug that caused it to fail in nearly all cases
15:39	<alkisg> This works for me (old revision): run_parts_list /usr/share/ltsp/screen-session.d/ S
15:40	<vagrantc> there is a bug in that find_opts doesn't get reset ... that might occasionally cause issues.
15:41	<alkisg> Ah I see
15:42	Well ok an unset there sounds logical, but why the
15:42	\* escaping?
15:42	or better yet, a local declaration for find_opts
15:44	Btw checking for [ -d "$1" ] after the `exit 1` above doesn't seem useful
15:46	<vagrantc> alkisg: yeah, the \* escape breaks it for me
15:47	i was getting some weird results depending on where i ran it from ... i.e. the * would match some things during the find_opts="-name $2*" bit
15:47	but the \ broke everything
15:48	<alkisg> Aaaah ok I got it
15:48	<vagrantc> i think the simplest thing is to revert it ... the one thing he asked me to test still worked
15:48	<alkisg> Gimme 2 mins to test
15:49	OK reproduced the problem
15:49	(that Gadi experienced)
15:49	....checking for a working solution...
15:50	<vagrantc> alkisg: how did you reproduce the problem?
15:50	<alkisg> cd /tmp
15:50	touch XShi
15:51	run_parts_list somedir XS
15:51	The * matches XShi so then find doesn't find anything
15:51	msignor (~msignor@24.115.67.19.res-cmts.sesp.ptd.net) joined #ltsp.
15:52	<msignor> evening everyone - could I pick some of your brains? I would like to recap some of my understanding about LTSP on debian
15:53	<vagrantc> alkisg: right
15:54	<alkisg> vagrantc: so one solution is to use an if:
15:54	if [ -n "$2" ]; then
15:54	find -L "$1" -mindepth 1 -maxdepth 1 -type f -name "$2" \| sed -n '/.\/[0-9a-zA-Z_\-]\{1,\}$/p' \| sort -n
15:54	else
15:54	find without the -name
15:54	fi
15:54	<vagrantc> alkisg: yeah, that's what i did
15:54	<alkisg> ...maybe there's also a nice way to quote it, but can't think of it currently
15:54	<vagrantc> msignor: have you seen http://wiki.debian.org/LTSP/Howto ?
15:54	<alkisg> msignor: don't ask to ask, just ask and see if anyone knows the answer :)
15:55	Nick change: zz_evil_root -> evil_root
15:55	<vagrantc> alkisg: maybe even using "$2"'*'
15:56	<alkisg> no, that's not necessary
15:56	when quoted, * doesn't expand
15:56	<vagrantc> alkisg: then why does it expand in the original case?
15:56	alkisg: because it's later called unquoted?
15:56	<alkisg> Because it's not quoted, the variable doesn't contain the quotes
15:56	Right
15:57	<vagrantc> alkisg: so having two different cases seems like the most reliable way
15:57	<alkisg> There should be a proper way to quote it, it's just too late for me to think about it :D
15:57	I bet in #bash we'd get an answer in 1 min :D
15:57	<msignor> hah, well i have followed a bunch of guides - long story short is I am running a distro called Voyage linux, based on debian squeeze...I just bought a house and I would like to be able to set up workstations not only as media players (no cable... nnned to download) but so I can have workstations all over... cool - ltsp w/ fat client seems to be the answer ---- instaled ltsp-server on debian, ldm, all the other stuff and got a login scre
15:57	en. on login i went right to terminal... installed xfce4 on my host, no change... installed xfce4 inchroot and boom. i got a login. so next was home directories.. installed nfs-common in the chroot. rebooted and now i get a hang at "setting up ltsp client" and then nothing mounts
15:58	prior to installing nfs-common it would just error and login.. and now i am stuck
15:58	i run ddwrt as my main router and have all that set. but so far my server infrastructure is less than 100watts across 3 devices
15:58	running reaaaally lean.
16:00	wasted a few hours by RTFM and not understanding... and started over.. from what I can tell /tftpboot (or whatever) is for only the booting... and the /opt/ltsp is the actual chroot.. im confusing myself about the whole NFS vs NBD and do i really need to rebuild the image etc..
16:00	when i did that.. it broke everything
16:00	mikkel (~mikkel@80.71.132.15) left irc: Quit: Leaving
16:00	<alkisg> vagrantc: we can also just use -name "$2" even if $2 is not defined, it just uses -name "", which again matches anything
16:00	<vagrantc> msignor: don't run ltsp-update-image ... it will switch you over to NBD
16:00	alkisg: oooh.
16:01	alkisg: clever.
16:01	msignor: debian doesn't usb NBD by default
16:01	msignor: so with fatclients, you run all the software essentially from within the ltsp chroot ... with thin clients, you'd install all your applications on the server.
16:01	<msignor> vagrantc: understood. I wanted NFS since I agree it seems to be easier / more flexible for what I want to do
16:02	<vagrantc> msignor: fat clients also mount the home directories with sshfs ... although there's an option to use NFS based homedirs
16:02	alkisg knows more about the NFS homedir stuff
16:03	<msignor> i was reluctant to use the ltsp-server-standalone since I already have DHCP / DNS on my DDWRT appliance.. i liked the control but its been a bear.
16:03	<alkisg> "i got a login. so next was home directories.. installed nfs-common in the chroot" ==> doesn't debian have nfs-common in the chroot by default?
16:03	<msignor> vagrantc: would you suggest an alternate distro geared for "out of the box" rather than attempt to install ontop of a stock install?
16:04	<alkisg> Ah no it uses nfsmount
16:04	<msignor> alksig -- thats what I thought.. but I tried to mount and was not able to, then chrooted into the /opt/ltsp and was able to apt-get install it
16:04	<alkisg> No ok nfsmount is in the initramfs, ok
16:05	<vagrantc> gah. i really wanted to upload ltsp 5.2.6 today...
16:06	<msignor> perhaps I am approaching this wrong.. I mean, I was able to get a few Aopen mini-pc's with core duo's in it.. and DVI.. i figured that LTSP fat client would be best for the multimedia aspect of things. at this point I am trying to see where to look so I can actually mount the home folders and actually finish this last step
16:06	<alkisg> msignor: grep NFS_HOME /opt/ltsp/i386/usr/share/ltsp/ltsp-init-common
16:06	Does this return some lines?
16:07	<msignor> yes, sent via PM
16:07	<alkisg> vagrantc: and the run_parts_list bug is stopping you? I think that -name "$2*" is an acceptable method...
16:08	<vagrantc> alkisg: that sounds good, yes.
16:08	<alkisg> msignor: ok, try exporting /home to your /etc/exports, and setting NFS_HOME=/home in your lts.conf
16:08	<vagrantc> i'm just running out of time to test
16:08	<alkisg> vagrantc: so no need for any of the 2 last "ifs"
16:08	<msignor> hah, well i stubled on that too and no dice.. i edited the lts.conf in /opt/ltsp....
16:08	i can mount /home from my desktop so I know the export does work
16:09	should I edit another file? There was no lts in /tftpboot
16:09	<alkisg> vagrantc: just this, with no if -d / if -n: find -L "$1" -mindepth 1 -maxdepth 1 -type f -name "$2" \| sed -n '/.\/[0-9a-zA-Z_\-]\{1,\}$/p' \| sort -n
16:09	<msignor> (I should mentioned I symlinked everything to a separate SSD -- I boot from a CF)
16:10	<alkisg> msignor: no, this is the correct file for debian
16:10	It's too late here, good night all
16:10	<vagrantc> msignor: though if you've at any point ran ltsp-update-image, you'll need to keep running it...
16:10	msignor: is there a file in /opt/ltsp/images
16:10	alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
16:10	<msignor> vagrantc - I had run it once, then deleted the chroot and started over
16:11	no, there is no longer a /opt/ltsp/images
16:12	<vagrantc> ok, regenerating the chroot should've fixed it
16:12	ltsp-update-images is a little hungry
16:12	<msignor> yeah - so I have seen :-) running on a 500mhz geode would of taken forever
16:13	so it looks like I followed everything properly... One thing to note is that ltsp-server didn't install ldm or anything else needed.. i had to install all of that manually
16:13	just cant get past this nfs home folder thing :-/
16:18	<vagrantc> huh?
16:18	ldm is installed in the thin-client ... are you saying that didn't get installed?
16:18	ldm-server is installed on the server-side...
16:19	it's only suggested by ltsp-server, since it pulls in an entire graphical environment on the server
16:19	ltsp-server-standalone depends on it, of course.
16:19	but if you're doing fatclients, you don't need ldm-server at all...
16:19	<msignor> yes - let me clarify the server was virgin - installed ltsp-server
16:20	got nowhere.. so assumed it was LDM since I read that LDM was the LTSP version of GDM
16:20	(yes / no??)
16:20	this was a few days ago and I started installing anything I could to try and get it to work
16:21	I am totally open to doing whatever process you suggest / recommend - you are a main guy afterall.. heh
16:21	Yes - I am after fatclient morso than thin client. actually thin-client in my case is the opposite of what I want to do
16:22	<vagrantc> just plain ltsp-server should be fine then
16:22	but i gotta run soon ...
16:22	<msignor> np - figured I would try here before I went searching on my own again
16:24	Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) left irc: Quit: I Leave
16:25	bobby_C (~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) left irc: Ping timeout: 248 seconds
16:31	komunista (~slavko@adsl-195-098-015-248.dynamic.nextra.sk) left irc: Quit: Leaving.
16:37	staffencasa (~staffenca@128-193-151-251.oregonstate.edu) left irc: Quit: Leaving
16:52	knipwim (~wim@ip4da83870.direct-adsl.nl) left irc: Ping timeout: 276 seconds
16:52	Nick change: evil_root -> zz_evil_root
17:09	bobberty (~martian_l@124-197-42-208.callplus.net.nz) joined #ltsp.
17:20	vagrantc (~vagrant@c-24-21-191-93.hsd1.or.comcast.net) left irc: Quit: leaving
17:23	bobberty (~martian_l@124-197-42-208.callplus.net.nz) left irc: Ping timeout: 255 seconds
20:11	GodFather (~rcc@d47-69-227-53.col.wideopenwest.com) joined #ltsp.
21:44	roasted__ (ae36d930@gateway/web/freenode/ip.174.54.217.48) joined #ltsp.
21:44	<roasted__> anybody active at the moment?
21:58	alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
22:01	roasted__ (ae36d930@gateway/web/freenode/ip.174.54.217.48) left irc: Quit: Page closed
22:21	alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
23:04	MorningSon (~MorningSo@cpe-70-114-21-95.satx.res.rr.com) left irc: Quit: WeeChat 0.3.0
23:39	otavio (~otavio@debian/developer/otavio) left irc: Ping timeout: 252 seconds
23:42	otavio (~otavio@189.114.111.55) joined #ltsp.
23:42	otavio (~otavio@189.114.111.55) left irc: Changing host
23:42	otavio (~otavio@debian/developer/otavio) joined #ltsp.
23:53	alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
00:00	--- Tue Mar 15 2011