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


Channel log from 13 March 2012   (all times are UTC)

01:03jamil has left IRC (jamil!~jamil@189.229.120.29)
01:21andygraybeal has left IRC (andygraybeal!~andy@h21.206.130.174.dynamic.ip.windstream.net, Ping timeout: 252 seconds)
02:07[GuS] has joined IRC ([GuS]!~gustavo@190.55.139.179)
02:07[GuS] has joined IRC ([GuS]!~gustavo@unaffiliated/gus/x-663402)
03:11adrianorg__ has left IRC (adrianorg__!~adrianorg@177.18.50.101, Ping timeout: 244 seconds)
03:11risca has joined IRC (risca!~risca@wnpgmb0903w-ds01-249-233.dynamic.mtsallstream.net)
03:11adrianorg__ has joined IRC (adrianorg__!~adrianorg@177.18.50.101)
03:32[GuS] has left IRC ([GuS]!~gustavo@unaffiliated/gus/x-663402, Remote host closed the connection)
03:34adrianorg__ has left IRC (adrianorg__!~adrianorg@177.18.50.101, Ping timeout: 265 seconds)
04:27leio_ has joined IRC (leio_!~leio@gentoo/developer/leio)
04:29leio has left IRC (leio!~leio@gentoo/developer/leio, Ping timeout: 245 seconds)
05:47monteslu has left IRC (monteslu!~monteslu@ip68-109-174-213.ph.ph.cox.net, Read error: Operation timed out)
06:00monteslu has joined IRC (monteslu!~monteslu@ip68-109-174-213.ph.ph.cox.net)
06:08alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
06:13epoptes_user7 has joined IRC (epoptes_user7!3e48f54a@gateway/web/freenode/ip.62.72.245.74)
06:27bauerski has joined IRC (bauerski!~witekb@frodo.psp.opole.pl)
06:35alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
06:36klausade has left IRC (klausade!~klaus@cm-84.215.157.180.getinternet.no, Ping timeout: 244 seconds)
06:36sndwrx has left IRC (sndwrx!~sndwrx@unaffiliated/sndwrx, Ping timeout: 240 seconds)
06:37zoobab has left IRC (zoobab!zoobab@vic.ffii.org, Ping timeout: 244 seconds)
06:37sep has left IRC (sep!~sep@40.211.jostedal.no, Ping timeout: 244 seconds)
06:37sutula has left IRC (sutula!sutula@nat/hp/x-ficyrhegrxvmfakb, Ping timeout: 244 seconds)
06:37alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
06:39zoobab has joined IRC (zoobab!zoobab@vic.ffii.org)
06:39Billy_Way has left IRC (Billy_Way!billy@nat/redhat/x-sgtrqdlkrlbqrzfs, Ping timeout: 240 seconds)
06:49sep has joined IRC (sep!~sep@40.211.jostedal.no)
06:50sutula has joined IRC (sutula!sutula@nat/hp/x-ypbfvlxsjdqwmvnu)
06:51sndwrx has joined IRC (sndwrx!~sndwrx@unaffiliated/sndwrx)
06:51Billy_Way has joined IRC (Billy_Way!billy@nat/redhat/x-yocamkbgjlfelryg)
06:53bmonkj has joined IRC (bmonkj!~skumlesen@46.32.130.15)
06:55risca has left IRC (risca!~risca@wnpgmb0903w-ds01-249-233.dynamic.mtsallstream.net, Quit: Lämnar)
06:56vagrantc has left IRC (vagrantc!~vagrant@c-76-115-60-19.hsd1.or.comcast.net, Quit: leaving)
06:56loather has left IRC (loather!~khudson@wsip-98-175-250-115.sd.sd.cox.net, Quit: This computer has gone to sleep)
07:04
<bauerski>
Hello, can anybody help me about local printer? OS Debian (testing) 64 bit, LTSP 5.3 (i386). I have got entry in /opt/i386/etc/lts.conf [172.16.0.27] PRINTER_1_DEVICE=/dev/lp0 PRINTER_1_TYPE = P but terminal not starting anymore. Then, when I nmap'ing this machine (during start), port 9100 is open and in few seconds no port 9100 open. Sorry for my english.
07:05
Without this entry terminal starting normally.
07:14
Sorry: PRINTER_0_DEVICE=/dev/lp0 PRINTER_0_TYPE = P port 9100
07:18alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
07:37gk4 has left IRC (gk4!~gk4@32.97.110.58, Ping timeout: 244 seconds)
07:38gk4 has joined IRC (gk4!~gk4@32.97.110.58)
07:42epoptes_user6 has joined IRC (epoptes_user6!3e48f54a@gateway/web/freenode/ip.62.72.245.74)
07:42
<epoptes_user6>
gethostbyname failure connect:errno=110 epoptes-client ERROR: Failed to fetch certificate from server:789
07:43epoptes_user6 has left IRC (epoptes_user6!3e48f54a@gateway/web/freenode/ip.62.72.245.74, Client Quit)
08:20khildin has joined IRC (khildin!~khildin@ip-80-236-227-85.dsl.scarlet.be)
08:32
<Hyperbyte>
bauerski, put your entire lts.conf on pastebin please
08:32
!pastebin
08:32
<ltsp>
Hyperbyte: pastebin: the LTSP pastebin is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebin, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here.
08:34Llama_be has left IRC (Llama_be!~Llama@94-226-90-169.access.telenet.be, )
08:50
<Hyperbyte>
eh... I just subscribed to the ltsp-discuss mailing list, the first e-mail I received has the subject "OMGZORS!! WTF!! nsfsmount: need a path"
08:51
Have I just picked a wrong time to join the mailing list, or is this representative for the usual communication in the list? :-)
08:52
<bauerski>
Hyperbyte: wait a moment.
08:53
<knipwim>
perhaps the same dude as yesterday?
08:53
the unfriendly one?
08:54
<Hyperbyte>
knipwim, hehe, you mean the one who said I'm a useless cunt? :-D
08:54
<bauerski>
http://pastebin.com/LGFn8Ke4
08:54
<knipwim>
yeah
08:55
<Hyperbyte>
That's what I thought. :-)
08:55
bauerski, between the []'s you specify the mac address, not the IP address
08:56
<bauerski>
OK. I'll try in the moment.
08:56
<Hyperbyte>
Something like [00:e0:c5:45:46:16], rather than [172.16.0.27]
09:04
<bauerski>
Still the same. Retrieves the address from dhcp and freezes after: filename: ltsp/i386/pxelinux.0
09:08
<Hyperbyte>
And if you comment out the last three lines, the client does boot?
09:08
<bauerski>
Yes
09:14
But when nmap'ing host, client boot. http://pastebin.com/VMFRtBPf
09:23bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
09:28Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com)
09:30Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com, Client Quit)
09:30Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com)
09:38Trixboxer has joined IRC (Trixboxer!~Trixboxer@115.124.115.71)
09:46alkisg has joined IRC (alkisg!554bb9ed@gateway/web/freenode/ip.85.75.185.237)
09:52alkisg has left IRC (alkisg!554bb9ed@gateway/web/freenode/ip.85.75.185.237, Ping timeout: 245 seconds)
10:03Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com)
10:20andygraybeal has joined IRC (andygraybeal!~andy.gray@obsidian.casanueva.com)
10:20andygraybeal_ has joined IRC (andygraybeal_!~andy.gray@obsidian.casanueva.com)
10:21
<andygraybeal>
mornining
10:25
<elias_a>
Good afternoon!
10:29
<andygraybeal>
:)
10:36alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
10:37Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com, Quit: Leaving)
10:45alexqwesa has left IRC (alexqwesa!~alex@alexo-veto.broker.freenet6.net, Quit: Хана X'ам !!!)
10:54ogra_ has left IRC (ogra_!~ogra@p5098ed03.dip0.t-ipconnect.de, Excess Flood)
10:56ogra_ has joined IRC (ogra_!~ogra@p5098ed03.dip0.t-ipconnect.de)
11:00fix has joined IRC (fix!~qweqeerwe@pool-68-238-65-159.lax.dsl-w.verizon.net)
11:00fix is now known as AssBurgers
11:00AssBurgers is now known as IAssBurgers
11:05andy_ has joined IRC (andy_!~andy@obsidian.casanueva.com)
11:06andy_ is now known as Guest79226
11:07adrianorg__ has joined IRC (adrianorg__!~adrianorg@177.18.50.101)
11:11
<IAssBurgers>
how do u get ltsp clients to save when they shutdown?
11:12
<andygraybeal>
.
11:12
sorry
11:12
<IAssBurgers>
?
11:12
<andygraybeal>
i didn't mean to hit the period.
11:12
<IAssBurgers>
sorry for what
11:13
<andygraybeal>
sorry, i didn't mean to interrupt yoru question with my period - i accidentally hit the keyboard while arranging my desk.
11:13
<IAssBurgers>
right then
11:17andygraybeal has left IRC (andygraybeal!~andy.gray@obsidian.casanueva.com, Read error: Connection reset by peer)
11:22andygraybeal has joined IRC (andygraybeal!~andy.gray@obsidian.casanueva.com)
11:32xsl has joined IRC (xsl!~silence@unaffiliated/xsl)
11:54
<Hyperbyte>
IAssBurgers, what do you want them to save, specifically? And which distro/version are you using?
11:55
Oh - wait a second
11:55
I forgot
11:56
You're the guy who called me a useless cunt yesterday. Guess you're on your own. :-)
11:56
andygraybeal, what's up! :-)
11:57
<andygraybeal>
heya Hyperbyte. i'm working on using 'liferay' cms .. how about you?
11:58
<Hyperbyte>
Working on the CMS/automation system they have here... my "todo"-list for that system insanely huge... 1st of april I'll be getting a new colleague though, so it'll become managable then.
11:58
Should've said CRM instead of CMS by the way
11:58
<andygraybeal>
that's bad ass, i hope you two get along.
11:58
aah CRM.. *run away* *run away* *run away!!!!*
11:58
<Hyperbyte>
Heh - we will... he's one of my best buddies, we know eachother from ICT college.
11:58
:-)
11:59
Run away? Why?
11:59
<andygraybeal>
omg, crms?!!?!!?
11:59
<Hyperbyte>
Customer database/relation management?
11:59
<andygraybeal>
yes yes, i wouldn't go near them!!
11:59
i'm having a hard enough time with plain regular apps.
12:00
but, i mean, congrats on doing it! i support you.
12:00
which one have you chosen to use?
12:01
<IAssBurgers>
well hyperbyte you are pretty damn useless, this channel is here for people seeking knowledge
12:01
<Hyperbyte>
Well, I'm calling it CRM because I don't know the proper term for it
12:01
<IAssBurgers>
I came and asked you and all you did was act like an elitist jerk
12:01
I figured out on my own
12:01
with some help from the email list
12:02
I have thick clients booting again
12:02
Just havent figured out how to get them to save or sync when I shut down
12:02
<Hyperbyte>
IAssBurgers, check the IRC logs. You'll find I'm very helpful & willing to help. Too bad you won't get any first-hand experience with that from me anymore. Also - this is the last thing I'm gonna say to you.
12:02
<IAssBurgers>
But I did get swap file working
12:02
Sir I dont keep irc logs, only fgts log irc conversations
12:02
<Hyperbyte>
andygraybeal, basically, it's an application I've made myself... it manages lots of work processes here, clients, travels, bookings, travel managers, etc....
12:03
!irclogs
12:03
<ltsp>
Hyperbyte: Error: "irclogs" is not a valid command.
12:03
<alkisg>
!logs
12:03
<ltsp>
alkisg: logs: http://irclogs.ltsp.org/
12:03
<IAssBurgers>
der[
12:03
herp derp
12:03
<alkisg>
The cunt etc stuff will always be online for everyone to see
12:03
<andygraybeal>
Hyperbyte, aah cool, yea, i good luck :)
12:03
<Hyperbyte>
andygraybeal, it's my long-term project here. Been building it for five years or so.
12:04
And people constantly want extra features, and stuff... ;-)
12:05
<andygraybeal>
i've had a look at tigercrm and others, just to keep them in my peripheral, nothing more.
12:06
IAssBurgers, when you say 'sync' do you mean ... like saving files? on my fat clients, i mount a share from the server.. and save the data to it like that. i wonder though, your probably way more advanced than me and already know this and you actually mean something else.
12:06
<Hyperbyte>
Well, years back we made concious decision that we wanted a system that facilitated and automated communication with customers, volunteer travel guides and external relations, without losing the personal touch. With those goals, you really need something custom-made.
12:07
<IAssBurgers>
well yeah like say, I change my home page in the browser, set some shortcuts on a box, w/e when I reboot, the thick client comes up ok, but none of those changes are saved
12:07
<andygraybeal>
ah that is all inside of your image that you build
12:08
<IAssBurgers>
no it should have autosave option
12:08
it doesnt, so derp
12:08* Hyperbyte grins madly. :-D
12:08
<IAssBurgers>
dont go there bro
12:08
<andygraybeal>
hm.. lltsp-update-image .. i think is what you'll need to do to work like this.
12:09
errrr too many ll's.
12:09
everytiime you want to make a change to your image, you have to run that command.
12:09
<IAssBurgers>
anyway to make that happen when the ltsp fat client shutsdown?
12:09
<andygraybeal>
you have to do that inside a chroot, not on the client.
12:10
<IAssBurgers>
fuck that
12:10
it should have option to do that
12:10
<andygraybeal>
well, why? chroot works fine.
12:10
<IAssBurgers>
why the hell would o chroot from the fat client every time I shut down?
12:10
lol
12:10
use your brains, your the smart ones here
12:10
figure it out
12:11
<andygraybeal>
you wouldn't, you'd build your chroot the way you want it.. then update your image. easy.
12:11
<IAssBurgers>
lord
12:11
ok so yeah thats a great idea in fact, why do computers save data at all? maybe they should all reboot and come up as a static image
12:11
<andygraybeal>
you wouldn't chroot from the fat client at all, i don't think you understand.
12:12
i don't think you understand how to implement the environment
12:12
<IAssBurgers>
no you dont get what Im saying
12:12
derp, I know how to chroot and make changes and update the image
12:12
what I asked, and let me ask it again so you understand
12:12
I want any changes I make ON the fat client, to save to the image automatically when I shut down
12:12
<andygraybeal>
well, i don't know if it works like that.
12:13
<IAssBurgers>
I know, thats what Im sayin
12:13
would be nice feature to ad
12:13
<andygraybeal>
i think all the changes need to be made on the chroot, then update t he image.
12:13
ah then, there you have it. feature request :)
12:13
but i don't see a need for it.
12:13
<IAssBurgers>
look, hyperbyte are you a developer of ltsp?
12:13
<andygraybeal>
i think using chroot to update the image is just fine.
12:13
<Hyperbyte>
IAssBurgers, no.
12:14
Oh, I forgot. I'm not talking to you. :-D
12:14
<andygraybeal>
i wouldn't want people updatnig their own image from within the image itself. that gets haphazard.
12:14
<Hyperbyte>
I can tell you this: http://www.middelkoop.cc/yrdiw.jpg
12:14
<IAssBurgers>
sure Im not complaining about chroot procedure
12:14
mmhmm..
12:14
there is a way to do it
12:15
<andygraybeal>
well, i think the idea is central control of the image... done with the chroot.
12:15
<IAssBurgers>
well thats a great feature too
12:15
but Ive got multiple machines here that I personally use, its not a classroom
12:15
<Hyperbyte>
Great thing is: LTSP has the best of both worlds combined.
12:16
Too bad I'm so useless... :(
12:16
<IAssBurgers>
well, thinclient loads the os off the main system which is nice, but it also sucks balls using the cpu, ram, sound on the server
12:17
<andygraybeal>
i guess, i figure it's just something i've gotten used to IAssBurgers. I think that i'm still getting used to it.
12:17
I just recently starting using fatclients.
12:17
<IAssBurgers>
would be nice to load the os the way thinclient does, AND use local cpu, ram gpu the way thin client images do
12:18
thick client images, sorry my bad
12:18
thick/fat w/e same thing
12:18
<andygraybeal>
i think the devs are planning what you are saying to the feature set.
12:18
<IAssBurgers>
ltsp 6?
12:18
<andygraybeal>
i can't say.
12:19
<IAssBurgers>
hey hyperbyte, sorry for being a douchebag, I was up for 50+ hours
12:19
<alkisg>
Wow, I thought I wouldn't speak to IAssBurgers until he apologized to Hyperbyte, not sure if I should help him now that he did
12:19
<andygraybeal>
wow 50 hours :)
12:20
<Hyperbyte>
IAssBurgers, sometimes I have horrible days as well. I still don't go around on the internet calling random people who are trying to help me "useless cunts".
12:20
<andygraybeal>
he said sorry, take it. don't keep arguing
12:20
<Hyperbyte>
Apology accepted, but being up 50+ is no reason to be a douche.
12:20
<andygraybeal>
lets get over it, i hate to see drama in this channel.
12:20
no buts! :P
12:21
i need more coffee guys :)
12:21
<Mava>
mm.. coffee <3
12:21
<IAssBurgers>
i know....
12:22
I was raging coz I couldnt figure out how to thick client
12:22
but I know now,
12:22artista_frustrad has joined IRC (artista_frustrad!~fernando@200.247.43.2)
12:22
<IAssBurgers>
In debian squeeze you ltsp-chroot --mount-proc
12:22
then apt-get install and make w/e changes you want, create users etc
12:22
THEN you ltsp-update-image
12:23
voila, generates the image
12:23
<andygraybeal>
yea, i can't remember what dev was talking about an interface to make changes to chroot, or even if i remember correctly that being what they said.
12:23
<IAssBurgers>
also u can set the swap file enabled and setup a conf for that
12:23
<Hyperbyte>
IAssBurgers, I know where you're going wrong.
12:23
<IAssBurgers>
?
12:23
<Hyperbyte>
And I will tell you.
12:24
<andygraybeal>
Mava, :) mmm mmm
12:24
<IAssBurgers>
well I dont know where I could be going wrong, its working
12:24
<Hyperbyte>
Before I do that, I would ask you to please think about that everyone in this channel is here to help you, voluntary... we like sharing knowledge. I would love for you to participate in this, but please - start being a little more laid back. :-)
12:25
<IAssBurgers>
ah, yes
12:25
<Hyperbyte>
Have some coffee, relax... like Andy. ;-)00000000
12:25
Now here's where you're going wrong:
12:25
Even though fat clients don't run any software on the server, they're still using the user database from the server, and storing user files on the server.
12:26
You have to create the fat clients users on the server, not inside the chroot.
12:26
<IAssBurgers>
also had some trouble getting sound to work, but that had nothing to do with ltsp, had to manually install the modules for this ESScrapware soundchip
12:26
orly
12:26
<andygraybeal>
i have to install extra modules for my asus eeebook
12:26
too
12:26
<IAssBurgers>
yeah I noticed that
12:27
only one of my user accounts was automatically in the fatclient image
12:27
but I have the same user account on my thick client that I login with as my server
12:27
and its not saving anything when I shut down
12:27
<Hyperbyte>
You shouldn't have any users in the fatclient image. You should have them on the server. When you login with LDM, the user on the server is created on the client, and their home is mounted from the server.
12:27[GuS] has joined IRC ([GuS]!~MysT@213-117-16-190.fibertel.com.ar)
12:27[GuS] has joined IRC ([GuS]!~MysT@unaffiliated/gus/x-663402)
12:27
<IAssBurgers>
um
12:28
no it doesnt work like that, for me, im confused, let me clarify...
12:28
<andygraybeal>
yes, home is auto mounted, you can mount other things manually also (like i do /srv)
12:28
<IAssBurgers>
I cannot login to the image unless I chroot and create users
12:28
<alkisg>
That's because you're using gdm instead of ldm
12:28
<IAssBurgers>
ahhh
12:29
<alkisg>
Anyway, I can't read more of orly wut etc, bb
12:29
<andygraybeal>
ldm is awesome it's orange and it looks bad ass!
12:29
<IAssBurgers>
well ldm is installed on both the image and the server
12:29
I guess Im just not using it atm
12:29alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
12:30
<IAssBurgers>
so would I have to make ldm the default on the server to achieve this?
12:30
<Hyperbyte>
IAssBurgers, LDM is installed on the server? If that's the case, then you have screwed up your installation badly. You flipped yesterday when I said this, but I'm gonna say it again: reinstall.
12:30
You shouldn't have LDM on the server, just on the client.
12:30
<IAssBurgers>
lemme check, one sec
12:30
deviant:/opt/ltsp/i386# aptitude search ldm
12:30
i ldm - LTSP display manager
12:30
i A ldm-server - server components for LTSP display manager
12:31
yup its installed on the server
12:31
<Hyperbyte>
I'm gonna get back to work here, lots to do... but let me give you some real good advice (and I know you don't like it, but please take it): install Ubuntu, configure fat clients and see how they work - experiment with them.
12:31
<andygraybeal>
ot: grr one of my vm's isn't coming up.. i hate this.
12:31
<IAssBurgers>
well it sort of installed it automatically when I install ltsp-server-standalone
12:31
<Hyperbyte>
Once you learn how it works with Ubuntu, you'll have an easier time understanding how it should work on Debian.
12:31
<IAssBurgers>
I refuse to use ubuntu
12:32
ubuntu server is fine, but I wont use ubuntu-desktop
12:32
<andygraybeal>
i don't t hnk you need to use ubuntu-desktop you can use somethign else.
12:32
<IAssBurgers>
besides, I have an established debian server
12:32
<andygraybeal>
i know people in here use lxde and others.
12:32
<IAssBurgers>
runs my squid and webserver, sql stuff
12:32
<Hyperbyte>
It won't kill you to try it, just to see how it works. I frequently install all kinds of distros to see how things work. My LTSP server was RedHat before I settled on Ubuntu.
12:32
Either way, back to work. --->
12:33
<IAssBurgers>
k
12:33
thanks
12:33
<Hyperbyte>
You're welcome.
12:33
:)
12:34
<andygraybeal>
don't be mean to me, but i'm an idiot and i got it to work on ubuntu no probs.. just followed the docs on ubuntu.com: https://help.ubuntu.com/community/UbuntuLTSP
12:34
i install it on ubuntu server, then run with the fatclient install.
12:34
i do use ubuntu-desktop inside my image, but that is because i don't mind the 10.04 way of doing things.
12:35
soon, i won't be able to do that though :(
12:35
hopefully i can use the failback-gnome.
12:35
i haven't tested that stuff yet, i've been waiting to hear what others report back.
12:37
<IAssBurgers>
yeah in debian-squeeze the only issue I had actually booting the fatclient was that shitty network-manager garbage breaking my connection during boot
12:40
<andygraybeal>
ot: omg, rebooting my vm server.. i can hear my heartbeating...
12:40
<IAssBurgers>
lol
12:40
<andygraybeal>
i have too much anxiety for this.
12:41
<IAssBurgers>
well ltsp-server-standalone and fatclient is not the same in debian as it is in ubuntu
12:41
there is no ltsp-build-image --fatclient option
12:41
you just build the image
12:41
but set fatclient=true in the lts conf before u build
12:42
other than that It looks the same
12:51bengoa has joined IRC (bengoa!~bengoa@2001:1291:229:2:216:cbff:feab:6cc9)
12:55khildin has left IRC (khildin!~khildin@ip-80-236-227-85.dsl.scarlet.be, Ping timeout: 246 seconds)
13:16IAssBurgers has left IRC (IAssBurgers!~qweqeerwe@pool-68-238-65-159.lax.dsl-w.verizon.net, Quit: Leaving)
13:17||cw has left IRC (||cw!~chris@phpgroupware/cw, Ping timeout: 246 seconds)
13:26jammcq has joined IRC (jammcq!~jam@70-91-230-209-BusName-Michigan.hfc.comcastbusiness.net)
13:26
<jammcq>
Hey all
13:26
happy 11th birthday to the #ltsp IRC channel !!!!!
13:26* highvoltage presses the fireworks button
13:28
<jammcq>
wow, quiet here
13:28
!seen gadi
13:28
<ltsp>
jammcq: gadi was last seen in #ltsp 9 weeks, 6 days, 21 hours, 49 minutes, and 16 seconds ago: <Gadi> :)
13:28
<jammcq>
whoa
13:28
<highvoltage>
.''.
13:28
.''. *''* :_\/_: .
13:28
:_\/_: . .:.*_\/_* : /\ : .'.:.'.
13:28
<jammcq>
hahahaha
13:28
<highvoltage>
.''.: /\ : _\(/_ ':'* /\ * : '..'. -=:o:=-
13:28
:_\/_:'.:::. /)\*''* .|.* '.\'/.'_\(/_'.':'.'
13:28
: /\ : ::::: '*_\/_* | | -= o =- /)\ ' *
13:28
'..' ':::' * /\ * |'| .'/.\'. '._____
13:28
* __*..* | | : |. |' .---"|
13:28
_* .-' '-. | | .--'| || | _| |
13:28
.-'| _.| | || '-__ | | | || |
13:28
|' | |. | || | | | | || |
13:29
___| '-' ' "" '-' '-.' '` |____
13:29
jgs~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
13:29
<jammcq>
is that a program?
13:29
<highvoltage>
nope, I shameless stole it from some website
13:29
<jammcq>
nice steal
13:30
<highvoltage>
http://www.chris.com/ascii/index.php?art=holiday%2F4th%20of%20july
13:32
<Hyperbyte>
-ChanServ(ChanServ@services.)- Registered : Mar 13 06:27:47 2001 (11 years, 0 weeks, 3 days, 07:04:21 ago)
13:32
:o!
13:32
According to Chanserv it's 11 years and 3 days ago
13:32
<jammcq>
hmm
13:33
<Hyperbyte>
I think someone isn't taking leap days into account!
13:33* Hyperbyte kicks Chanserv
13:33
<Hyperbyte>
Either way, yeah - congrats everyone! :-D
13:34* jammcq remembers his first venture into #ltsp
13:34
<Hyperbyte>
:-D
13:34
<jammcq>
I didn't know anything about irc at the time
13:34
I was just busy making thin clients boot
13:35alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
13:35
<jammcq>
and Mistik1 told me I had to get online, there was a bunch of ltsp people here
13:39
<Hyperbyte>
How old is 11 years in Freenode terms anyways?
13:40
<jammcq>
I think the formula is: Multiply by 9, divide by 5, add 32
13:41
<Hyperbyte>
51,8, wow!
13:41
<andygraybeal>
wow 11 years, for real?
13:41
<jammcq>
yeah, that's about right
13:41
<alkisg>
Wow, I'm 100 years old in freenode terms :P
13:41
<Hyperbyte>
Haha
13:41
<alkisg>
Happy birthday LTSP, thanks jammcq :)
13:41
<jammcq>
alkisg: you don't look a day over 90
13:41
<Hyperbyte>
alkisg, Freenode itself isn't even that old in Freenode terms! ;-)
13:41
<jammcq>
we were using freenode since before it was called freenode
13:42
<Hyperbyte>
This channel is only one year younger than Freenode and it's predecessors itself, according to Wikipedia.
13:43* Hyperbyte high fives jammcq :-D
13:43
<Hyperbyte>
Wait - no - I'm counting completely wrong here
13:44
About five years younger.
13:47
jammcq, 11 years ago, did you ever dream secretly that LTSP would power hundreds and thousands of thin clients around the world? ;-)
13:50epoptes_user5 has joined IRC (epoptes_user5!968c0b30@gateway/web/freenode/ip.150.140.11.48)
13:51epoptes_user5 is now known as yannis-siahos
14:03yannis-siahos has left IRC (yannis-siahos!968c0b30@gateway/web/freenode/ip.150.140.11.48, Quit: Page closed)
14:06IAssBurger has joined IRC (IAssBurger!~qweqeerwe@pool-68-238-65-159.lax.dsl-w.verizon.net)
14:06
<IAssBurger>
fuuuu
14:06
Time is wrong on the lstp fat client
14:06
when I change the time the box locks up
14:06
<jammcq>
Hyperbyte: had no clue
14:06
<IAssBurger>
time is correct on system bios
14:06
anyone know how to correct this?
14:06
<jammcq>
Hyperbyte: it was actually Aug 4th 1999 that we started this
14:07
<IAssBurger>
u know I thinkim going to take hyperbytes advice and just reinstall and make sure I have ldm setup properly
14:07
afk
14:09||cw has joined IRC (||cw!~chris@gateway.wilsonmfg.com)
14:09
<andygraybeal>
IAssBurger, there is a timeserver configuration in the lts.conf
14:09||cw has left IRC (||cw!~chris@gateway.wilsonmfg.com, Changing host)
14:09||cw has joined IRC (||cw!~chris@phpgroupware/cw)
14:10
<andygraybeal>
mine says: TIMESERVER = 192.168.2.1
14:13
<Hyperbyte>
jammcq, are there actually usage statistics of LTSP around the world?
14:13
How many organisations, clients?
14:15
<jammcq>
Hyperbyte: not really. we used to keep a wiki page where people would post there success stories. but like other free software, it's impossible to know how many people are using it
14:16
<stgraber>
alkisg: and one more epoptes bug for you ;)
14:16
<alkisg>
stgraber: thanks, looking... :)
14:17
<stgraber>
alkisg: this one should be easy to fix at least ;)
14:17
<alkisg>
stgraber: my initial implementation was 10 years, but vagrantc asked me to lower it to 5
14:17neyder_ has joined IRC (neyder_!c9f03578@gateway/web/freenode/ip.201.240.53.120)
14:17
<alkisg>
Since the system certificate is also for 10 years, I think I'll go for that
14:18
<neyder_>
Hi!
14:18
<alkisg>
(maybe reusing the system certificate itself, instead of generating ours...)
14:18
<neyder_>
how can i restart epoptes client?
14:18
<alkisg>
neyder_: you just run /usr/sbin/epoptes-client
14:18
It'll automatically kill the other instances of the same user
14:18
<stgraber>
alkisg: well, the snakeoil certificate is actually a problem with an expiry of 10 years, that's why we usually recommend generating a new one instead of using it
14:19
<alkisg>
stgraber: is that an advice towards system administrators, or towards packages?
14:20
I mean, if epoptes uses the snakeoil certificate, and the system administrator generates another for 40 years, we wouldn't mind,
14:20
...anyway
14:20
<stgraber>
alkisg: administrators usually. The snakeoil is usually used by apache where the client (a web browser) will clearly show that the certificate expired making it easy for the administrator to go and re-generate it.
14:21
<alkisg>
It'll be much quicker to just increase the certificate life
14:21
And we can consider on another release if we want to use the system snakeoil instead of generating our own
14:21
I wonder if we could use the ssh keys as certificates... since the chroot already has the server keys
14:21
<neyder_>
gracias!
14:21
<stgraber>
I kind of like having a separate CA for epoptes especially if we eventually want to have the central server stuff with the admin authentication using SSL client certificates
14:22
like I demoed at the hackfest
14:22
<alkisg>
neyder_: you're welcome
14:22
<stgraber>
so yeah, I think the easiest is to bump the expiry to something big enough that we won't ever have to care about it :)
14:23
(sadly SSL doesn't support certificates without expiry)
14:23
<alkisg>
stgraber: about the "cannot find an appropriate pixmap format" problem, what's your color depth? 24?
14:23
Ah just saw your answer
14:23
<stgraber>
alkisg: I replied in the bug, yeah it's 24bit at 1024x768 with a cirrus video card
14:23
<alkisg>
OK, it seems like I finally have to try out KVM :)
14:24
It's an xvnc4viewer bug though... and x11vnc -24to32 was supposed to work around it
14:24
<neyder_>
to make epoptes work (no ltsp) with mixed distros (lucid, maverick, oneiric) you should first install the server, after on clients put the ip on /etc/default/epoptes-client and las copy the certificate "sudo /usr/sbin/epoptes-client -c" ;) Thanks!
14:25
<alkisg>
neyder_: or you could put "server" in /etc/hosts
14:25
Instead of modifying /etc/default/epoptes-client
14:25
<neyder_>
my teacher machine is not server :)
14:25
<alkisg>
Even if your server is not named server
14:25
It doesn't matter
14:26
<neyder_>
like: "ip.ip.ip.ip server" in /etc/hosts ?
14:26
<alkisg>
Yup
14:26
(or in your DNS server, if you're using one)
14:26
<neyder_>
sure ill do it in the installation methods i'm doing (a personalized ubuntu for my school) ? but for now i'm just tryin,
14:27* neyder_ sorry for the english
14:27
<alkisg>
No problem at all :) Is epoptes translated to your language?
14:27
<neyder_>
yes!
14:28
<alkisg>
Nice
14:28
<neyder_>
it is, but i'll check on the way. if anything is wrong, and to work for another local languages (aymara and quechua)
14:28
alkisg: i'm working on this project http://escuelabpuno.org (in spanish sorry)
14:28
<alkisg>
Cool, more info in http://www.epoptes.org/translations
14:29
Sugar desktop?
14:29
<neyder_>
yup
14:29* alkisg has never tried it, but wishes to
14:30
<neyder_>
in Peru it is a long tale (a scary tale) xD
14:30* neyder_ has to go for his students, is time to teach!!!
14:30
<alkisg>
Bye! :)
14:31
I'm a teacher myself, if you need assistance feel free to ping me
14:31LuizAngioletti has joined IRC (LuizAngioletti!c8ef4083@gateway/web/freenode/ip.200.239.64.131)
14:31
<LuizAngioletti>
Howdy!
14:31
Who here know TCOS?
14:32
I read their wiki but I couldn't point out how it was different from LTSP...
14:32
http://wiki.tcosproject.org/TCOS/Introduction
14:33
<andygraybeal>
hi LuizAngioletti :)
14:33
<LuizAngioletti>
andygraybeal: Hi! =D
14:39fgth has joined IRC (fgth!~fsoyer@cha86-1-82-247-200-251.fbx.proxad.net)
14:39fgth has left IRC (fgth!~fsoyer@cha86-1-82-247-200-251.fbx.proxad.net)
14:40
<ogra_>
tcos still exists ?
14:40
its using a very weird way of abusing an initramfs as a rootfs
14:41neyder_ has left IRC (neyder_!c9f03578@gateway/web/freenode/ip.201.240.53.120, Ping timeout: 245 seconds)
14:41
<alkisg>
Requirements: At least Pentium 100-133 with 32-64 Mb RAM ==> I wonder if that's still true...
14:41
LTSP 4.2 supported clients with 16 RAM, but Precise will need 128 :(
14:42
<ogra_>
well, last time i looked at it i wouldnt have used it in production, the code quality was rather uhmmm ...
14:42
but that might have improved... my last look was years ago
14:42
back then it was a big collection of hacks
14:44
iirc it was sponsored by some local government school project
14:44
i really wonder if its still alive
14:48* ogra_ looks at the recent git changes ... fun
14:48
<ogra_>
they deliberately break multiarch by enforcing links for libs
14:48bmonkj has left IRC (bmonkj!~skumlesen@46.32.130.15, Ping timeout: 248 seconds)
14:57
<LuizAngioletti>
ogra_: =P I need to learn to do that. =)
14:57risca has joined IRC (risca!~risca@wi-secure-3639.cc.umanitoba.ca)
14:58
<LuizAngioletti>
ogra_: Not enforce links, but to get information that way.
14:58
<ogra_>
it still breaks the linker path
14:58
there is a reason the arch triplet is in the path ;)
14:59
if any SW *needs* such a hack, the SW needs to be fixed
15:03
<andygraybeal>
alkisg, i wonder if you've had a chance to work on the script that ends users tasks on the fatclient from the server for me?
15:03
alkisg, it's no rush if you haven't, i'm just wondering.
15:04
<alkisg>
andygraybeal: thanks for reminding me, no, I completely forgot about it after the initial implementation
15:04
<andygraybeal>
alkisg, maybe you've forgotten too :) i'll have to remind myslf of the details as well!
15:04
ah thank you! :)
15:05
<alkisg>
So, when user u1 logs in client c1, and he's already logged in client c2, you want that c2 processes forcibly terminated, right?
15:05
(even if that's really bad and should be prohibited etc etc?)
15:11Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com)
15:13
<andygraybeal>
okay, let me read, i was talking to the building maint guy.
15:13
yes, that is correct. - but with a prohibitive prompt, letting him know he's on his own :P
15:13
i guess i can edit the prompts if it is regular text, myself.
15:13
i think the prompt that you hvae given me, works well.
15:13
*already given me
15:14
and i keep reminding them at our weekly meeting, so the people that it matters to understand the consequences.
15:15
<alkisg>
The difficult part is that fat clients are involved, which cannot be easily informed about the server ssh process getting killed
15:15
I'll put it (again) in my todo list :)
15:15
But we're trying to solve some bugs in ltsp and epoptes these days, so it might take a while...
15:16
<andygraybeal>
alkisg, thank you. take your time. I understand.
15:17shogunx has left IRC (shogunx!~shogunx@rrcs-67-79-182-232.se.biz.rr.com, Ping timeout: 252 seconds)
15:17
<alkisg>
andygraybeal: better yet... could you file a bug about this? :
15:17
...saying that you request this new feature,
15:17
<andygraybeal>
alkisg, for sure!
15:17
<alkisg>
where when the ssh connection of a fat client login is killed,
15:17
<andygraybeal>
the prob is it's confusing to explain :)
15:17
<alkisg>
that user processes in the fat client die too
15:17
<andygraybeal>
but yes, i will do my best.
15:18
rock on, you just explained it!
15:18
<alkisg>
No need to involve autologins in the explanations
15:18
It would be a separate option
15:18
And you'd just combine the two options to get what you want
15:18
LDM_LIMIT_ONE_SESSION_PROMPT=True,
15:18
LDM_LIMIT_ONE_SESSION=True,
15:19
KILL_FAT_SESSIONS_WHEN_SSH_DIES_OR_SOMETHING=True
15:19
!ltsp-bug
15:19
<ltsp>
alkisg: ltsp-bug: To file a bug report for upstream LTSP, go to https://bugs.launchpad.net/ltsp
15:19
<andygraybeal>
rock, logging in now
15:20
<Hyperbyte>
Doesn't LDM already have a limit one session configuration option?
15:20
<andygraybeal>
Hyperbyte, yes, it does
15:20
<alkisg>
It does, and it can kill processes of the same user in the ltsp server,
15:20
but of course that doesn't include processes running on other fat clients
15:20
<Hyperbyte>
Ah, not on fat clients
15:20
Right. :)
15:20
<andygraybeal>
yes, that'c correct Hyperbyte
15:21* Hyperbyte commits to memory
15:21* alkisg wonders what it would be like to have a human's memory formatted :P
15:21
<andygraybeal>
alzehimers?
15:21
er, atleast close
15:22
<alkisg>
Nah, that's roughly equivalent to bad ram
15:22
<andygraybeal>
maybe that's like having an ltsp image loaded everyday and losing anythign recent.
15:22
aah ok
15:28
https://bugs.launchpad.net/ltsp/+bug/954143
15:28
okay have a look at it, let me now if i should edit it to make more sense.
15:32khildin has joined IRC (khildin!~khildin@ip-80-236-227-85.dsl.scarlet.be)
15:42Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com, Quit: Leaving)
15:59alexqwesa has joined IRC (alexqwesa!~alex@alexo-veto.broker.freenet6.net)
16:07
<alkisg>
andygraybeal: no worries it's fine, thanks
16:07
<andygraybeal>
good, thank you :)
16:14srdjo has joined IRC (srdjo!~srdjo@109.228.93.179)
16:14
<srdjo>
hi all
16:16risca has left IRC (risca!~risca@wi-secure-3639.cc.umanitoba.ca, Quit: Lämnar)
16:18
<alkisg>
Hello
16:20
<LuizAngioletti>
hello
16:24rthomson has joined IRC (rthomson!~rthomson@mars.pet.ubc.ca)
16:26adrianorg_ has joined IRC (adrianorg_!~adrianorg@186.215.17.47)
16:28
<srdjo>
did anyone have problem with flash plugin on firefox in FAT client ?
16:29adrianorg__ has left IRC (adrianorg__!~adrianorg@177.18.50.101, Ping timeout: 252 seconds)
16:29
<alkisg>
No, what problem?
16:30
<srdjo>
As soon as firefox is started in 3 or 4 minutes flash crashes and after that firefox disappears
16:30
<alkisg>
No, I didn't see that... it sounds graphics-driver related
16:32
<srdjo>
it might be - it is happening on two same clients
16:34
i tested memory but since graphics is integrated, I might try to insert some cheep graphics card just to see will it happen again
16:36
<alkisg>
Also check ~/.xsession-errors and dmesg
16:37LuizAngioletti has left IRC (LuizAngioletti!c8ef4083@gateway/web/freenode/ip.200.239.64.131, Ping timeout: 245 seconds)
16:55risca has joined IRC (risca!~risca@wi-secure-3639.cc.umanitoba.ca)
16:58komunista has joined IRC (komunista!~slavko@adsl-195-168-242-217.dynamic.nextra.sk)
16:59shogunx has joined IRC (shogunx!~shogunx@rrcs-67-79-182-232.se.biz.rr.com)
17:20alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
17:20[GuS] has left IRC ([GuS]!~MysT@unaffiliated/gus/x-663402, Remote host closed the connection)
17:33shawnp0wers has left IRC (shawnp0wers!~spowers@linuxjournal/staff/shawnp0wers, Quit: leaving)
17:33shawnp0wers has joined IRC (shawnp0wers!~spowers@linuxjournal/staff/shawnp0wers)
17:34bengoa has left IRC (bengoa!~bengoa@2001:1291:229:2:216:cbff:feab:6cc9, Remote host closed the connection)
17:47monteslu has left IRC (monteslu!~monteslu@ip68-109-174-213.ph.ph.cox.net, Read error: Operation timed out)
18:00vagrantc has joined IRC (vagrantc!~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net)
18:00monteslu has joined IRC (monteslu!~monteslu@ip68-109-174-213.ph.ph.cox.net)
18:16Trixboxer has left IRC (Trixboxer!~Trixboxer@115.124.115.71, Quit: "Achievement is not the end, its the beginning of new journey !!!")
18:18hydruid has joined IRC (hydruid!~hydruid@adsl-67-65-250-63.dsl.okcyok.swbell.net)
18:19
<hydruid>
Hello All, I'm trying to implement the use of NBD Swap (Network swapfiles for thin-clients)
18:19
<vagrantc>
distro? release?
18:19
<hydruid>
lucid
18:19loather has joined IRC (loather!~khudson@wsip-98-175-250-115.sd.sd.cox.net)
18:19khildin has left IRC (khildin!~khildin@ip-80-236-227-85.dsl.scarlet.be, Ping timeout: 246 seconds)
18:20
<hydruid>
it appears to be working, but the Swap size never gets larger than "192836k" according to Top
18:20
Even if I change the size= parameters in lts.conf (tried 256, 512, and 1024)
18:21
<vagrantc>
it's not lts.conf
18:21
<hydruid>
oh lts.conf is not the proper place to setup the swap?
18:25hydruid has left IRC (hydruid!~hydruid@adsl-67-65-250-63.dsl.okcyok.swbell.net, Read error: No route to host)
18:28hydruid has joined IRC (hydruid!~hydruid@adsl-67-65-250-63.dsl.okcyok.swbell.net)
18:28
<hydruid>
vagrantc, My apologies my laptop decided to bluescreen
18:29
I guess the main question I'm asking is, when I run top on the Client should the Swap: # reflect the nbdswap size setting?
18:29sepski has joined IRC (sepski!~sep@79.170.82.107)
18:30sepski is now known as Guest54565
18:36
<vagrantc>
hydruid: i don't recall exactly.
18:36
hydruid: it's been a long time since i looked at it
18:37
<hydruid>
vagrantc, thank you, I think it's working because when i enabled it, the swap size does increase
18:37
it just doesn't get as big, according to top, as it is
18:37
<vagrantc>
hydruid: top on the thin client? or on the server?
18:37
<hydruid>
client
18:37
<knipwim>
hydruid: you have to use /etc/ltsp/nbdswapd.conf to set the size
18:37
on the server
18:38
<hydruid>
knipwim, OMG ty, I completely misread that
18:38
lol wow <-fail
18:38
<knipwim>
like SIZE=128
18:39
<hydruid>
knipwim: ty I completely read that wrong
18:40
knipwim, thank you that did the trick!
18:40
vagrantc, ty again old buddy
18:41hydruid has left IRC (hydruid!~hydruid@adsl-67-65-250-63.dsl.okcyok.swbell.net, Quit: Leaving)
18:49
<vagrantc>
good luck, mysterious random ltsp user :)
18:49
<knipwim>
you don't know him?
18:50
cause he called you "old buddy"
18:50
<vagrantc>
not that i'm aware of
18:50
hence my response :)
18:52alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
18:52* vagrantc waves to alkisg
18:53
<alkisg>
Hi vagrantc, hi all :)
18:53
<vagrantc>
alkisg: i was surprised to find out yesterday that backporting to squeeze was trivial
18:54
<alkisg>
Yey! It seems we're good coders :P :D
18:54
<vagrantc>
in fact, it was a simple rebuild.
18:55
<alkisg>
Is there something against chroot series-upgrading now?
18:55
E.g. can someone upgrade a squeeze chroot to wheezy?
18:55
<vagrantc>
haven't tried, but in theory it should work.
18:56
i usually build a new chroot, just because it's makes it easier to revert if needed.
18:57
<alkisg>
Yeah I also advice teachers here to reinstall newer OS versions in a second partition, so that they can revert to the old one by just selecting it in grub
18:58
Btw stgraber started filing bug reports for epoptes, we'll need a new release soon :D
18:58
<vagrantc>
yes, gave me a heads up last night
18:58
<alkisg>
One of them was about the certificate expire date, he says we would have less troubled users if we used an e.g. 40 years expiry date
18:58
<vagrantc>
in theory, i'll have time friday
18:59
5 years is too short?
18:59
<alkisg>
5 years is the time that LTS releases are supported
18:59
<vagrantc>
people really should do some sort of security audit at least once every 5 years...
18:59
<alkisg>
So if someone upgrades an LTS release...
18:59
The preinstalled snakeoil is valid for 10 years
18:59
<vagrantc>
i'd rather see epoptes give a heads up when the certificate is getting close to expiring
19:00
<alkisg>
But he prefers epoptes not using that
19:00
<vagrantc>
right
19:01
<alkisg>
So anyway now I'm not sure what I should do, put it for 5, 10, 20 or 40 years
19:02
For teachers here 40 would sound fine :P
19:02Mava has left IRC (Mava!~Mava@ip-45-224.dhcp.opintanner.fi, Ping timeout: 246 seconds)
19:02
<stgraber>
vagrantc: the problem here is that the client side downloads the certificate, so we'd also need the client to check the expiry and warn the user somehow (hard when it's a background process)
19:02srdjo has left IRC (srdjo!~srdjo@109.228.93.179, Quit: Leaving)
19:02
<vagrantc>
stgraber: sure...
19:02
<stgraber>
vagrantc: so renewing the certificate means manual action on every client...
19:03
vagrantc: that's quite a bit worse than for example a web server where the client just prints a scary warning and easily lets the user load the new one
19:04* vagrantc considers that even worse...
19:04
<vagrantc>
but that's a larger topic
19:04
<alkisg>
In the far future, sure, epoptes-client could also pop up a dialog and use policykit for a user authentication to accept the certificate, but until then... :)
19:04
<vagrantc>
40 years seems absurdist.
19:05
<alkisg>
Can we settle on 10, the default for snakeoil too?
19:05
I'm sure that epoptes won't be using the same certificate mechanism after 10 years :)
19:05
<vagrantc>
i guess.
19:07
though auto-updating the cert shouldn't be needed, should it?
19:07
i.e. like the last one, which expired after a month?
19:08
<alkisg>
I think that leaving the existing installations to 5 years is fine
19:08
<vagrantc>
on package upgrades, it could warn the admin if the cert is going to expire "soon"
19:08
<alkisg>
No need to force them sooner to transfer the certificate, if they have to do it in 5 years, let them do it then
19:08
<vagrantc>
that would handle LTS -> LTS upgrades fairly reasonably.
19:09
<alkisg>
I think that the epoptes package for the next LTS won't be using the same certificate mechanism :)
19:09
So it's a moot point anyway
19:09
<vagrantc>
but if it is...
19:09
<alkisg>
If it is, sure
19:09
<vagrantc>
should use monkeysphere to verify the certs :)
19:09
http://web.monkeysphere.info
19:10
that provides an update mechanism that could be used.
19:13
<highvoltage>
win 27
19:13
<alkisg>
27 irc windows? wow... :)
19:14
<vagrantc>
win!
19:17
<highvoltage>
(they go much higher ;p)
19:21Guest54565 is now known as sep_
19:28Mava has joined IRC (Mava!~Mava@ip-45-224.dhcp.opintanner.fi)
19:42alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Read error: Connection reset by peer)
19:42alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
19:47alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
19:56Gremble has joined IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com)
20:09Gremble has left IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com, Quit: I Leave)
20:18khildin has joined IRC (khildin!~khildin@ip-80-236-227-85.dsl.scarlet.be)
20:57sep_ has left IRC (sep_!~sep@79.170.82.107, Quit: Forlater kanalen)
20:59epaphus has joined IRC (epaphus!~user@200.122.149.9)
21:06
<epaphus>
I know how LTSP works.. but is there any project out there that I can boot a vnc client... so that i can simply make X sessions on a thin client?
21:06
simplistic.
21:07
<Hyperbyte>
epaphus, why would you want to use VNC rather than remote X?
21:07
<epaphus>
Hyperbyte, whats the difference?
21:14
<vagrantc>
epaphus: you could probably do what you want with LTSP
21:14
<Hyperbyte>
Lots. Remote X uses tons of bandwith, but is very fast. VNC uses little bandwith, but is very slow.
21:15
<vagrantc>
and there's also NX
21:16
<epaphus>
ok how about Remote X? or VNC... is that possible? This way its extremely easy for the user to pick which X server to connect to... its a fast failover solution in case one isnt available or busy or under maintenance
21:16
<vagrantc>
what's your goal? connect to a server on the local network?
21:16jammcq has left IRC (jammcq!~jam@70-91-230-209-BusName-Michigan.hfc.comcastbusiness.net, Quit: leaving)
21:16
<epaphus>
ltsp is dhcp based and... i would have to broadcast a new ltsp server
21:16
vagrantc, yes
21:17
<vagrantc>
epaphus: DHCP is one protocol that ltsp uses, not the only.
21:17
<epaphus>
vagrantc, what other does it use? I just want to know what my options are :)
21:17risca has left IRC (risca!~risca@wi-secure-3639.cc.umanitoba.ca, Ping timeout: 248 seconds)
21:17
<vagrantc>
epaphus: well, you can write hooks to use whatever protocols you want for information dissemination
21:18
LTSP is a collection of services to boot an operating system.
21:18
<epaphus>
vagrantc, in ltsp?
21:19
<vagrantc>
that operating system can be configured to do just about anything you could do with a disk'ed machine.
21:19
the default behavior is to connect to an LTSP server and run applications displayed locally.
21:20
epaphus: yes, LTSP has many places you can write hooks or plugins or configuration options.
21:20risca has joined IRC (risca!~risca@wi-secure-3639.cc.umanitoba.ca)
21:21
<epaphus>
ok.. so on the other hand... what options do I have to simply let the user pick the vnc server.. or x server to connect to.
21:23
<vagrantc>
i don't know that there's support for VNC out of the box, but it probably wouldn't be hard to write.
21:23
there are other similar protocol scripts for RDP
21:23
epaphus: why don't you just try it out and see what's there by default, and start tinkering with it?
21:24
epaphus: i don't feel like we have enough shared vocabulary to make meaningful recommendations.
21:24
<epaphus>
ok. anybody else is welcome to suggest me then ... :)
21:25
<vagrantc>
it just seems like you're stabbing in the dark without understanding what LTSP even is.
21:28
<epaphus>
ok ill read more on ltsp... thank you vagrantc
21:35
<vagrantc>
epaphus: if ii understand what you're saying, i think LTSP's default behavior would get 80-90% of what you're trying to do, but there are some corner cases that might be trickier.
21:37
<epaphus>
vagrantc, ok. In this case any link you can provide me is appreciated.
21:42naptastic has joined IRC (naptastic!~david@c-98-198-253-65.hsd1.tx.comcast.net)
21:43
<naptastic>
This isn't *quite* LTSP but is related. I'm setting up PXE / root over NFS on Debian, and some of my clients, some of the time, stop booting with "nfs: server 192.168.0.1 not responding, still trying"
21:44
Before that, there's a warning that "mount.nfs: remote share not in 'host:dir' format", but the clients that succeed at booting also show this warning.
21:44alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
21:44
<IAssBurger>
check your firewall
21:44
I had to iptables -F to get through to nfs even tho I had the ports open
21:44
iptables -F
21:45
<naptastic>
IAssBurger, yeah, it's not the firewall. Some clients are able to boot, some of the time, and they're all on the same switch and interface.
21:45
<IAssBurger>
k
21:45
<naptastic>
I suspect that it's a race condition between something and something else, like the network not coming up fully before nfs tries to work its magic or something
21:45
but I have no idea how to troubleshoot or even diagnose that
21:45
I figured y'all would be the most likely crowd to know :-)
21:46
<IAssBurger>
yeah I have a pxe client that wont boot to pxe at all, some Intel crap
21:46
<naptastic>
mmm
21:46
<IAssBurger>
Ive read that Intel PXE booting has its own caveats
21:46
<naptastic>
this is all pro/100's on Transmeta Crusoe boards... it's weird.
21:46
<IAssBurger>
yea my pro100 boots with no problem
21:46
<naptastic>
hmm
21:47
the frustrating thing is that they *were* working
21:47
<IAssBurger>
im a total noob in here, I just got fat clients booting
21:47
<naptastic>
ah, ok
21:47
<IAssBurger>
but I am using debian squeeze
21:48
and I assume I must share your frustration that the majority of the documentation or informationals online are geared toward ubuntu
21:49
in regards to ltsp, I mean
21:49
<naptastic>
yeah... I don't really mind that part, though these things are ssh and serial interface only
21:49
yeah
21:49
so there is not, and never will be, GUI on these things
21:49komunista has left IRC (komunista!~slavko@adsl-195-168-242-217.dynamic.nextra.sk, Quit: Leaving.)
21:49
<IAssBurger>
hey
21:49
<naptastic>
almost all of them will never be addressed as individuals
21:49
?
21:49
<IAssBurger>
might be an issue with ssh
21:49
<naptastic>
huh?
21:50
<IAssBurger>
did you tail -f /var/log/auth.log on the server abd watch whats going on with ssh in real time in regards to your issue
21:50
ssh might not be authenticating
21:50
its just a guess
21:50
but worth checking
21:50
<naptastic>
well, I'm not trying to use ssh... it hasn't even had a chance to start on the client before their deaths
21:50
*shrug*
21:50
I mean
21:50
<IAssBurger>
ahh
21:50
cant even load the pxelinux.0
21:50
I see
21:50
<naptastic>
they have to finish booting before I can try sshing in :-)
21:50
oh no, they get past that
21:51
they get the kernel and initrd, set a bunch of stuff up
21:51
and then try to mount / over nfs and hang and die
21:51
<IAssBurger>
so your ltsp server is also the dhcp server?
21:51
<naptastic>
the funny thing is, I've done a tcpdump on the server, and they're actually not requesting anything
21:51
yeah, it's all one box
21:51
dhcp, tftp, nfs...
21:51
<IAssBurger>
hey
21:51
I had a similar issue because network-manager was installed
21:52
it kept breaking the network connection
21:52
are these thick clients or thin
21:52
<naptastic>
totally thin
21:52
there's physically no way to add hard drives :-)
21:52
<IAssBurger>
I had to chroot and apt-get remove network-manager on my client images, but im using fat/thick clients so thats a totally diff issue
21:52
I have no hard disk in mine either
21:52
<naptastic>
well... I wonder if it is
21:53
<IAssBurger>
I like the power I get from using the local resourced on the client
21:53
<naptastic>
I'm not even sure if it's installed.
21:53
<IAssBurger>
doesnt bog out my server
21:53
<naptastic>
yeah
21:53
well, that's the whole point of these. Distributed computing.
21:53
I was about to start on installing distcc, and then this problem started
21:53
<IAssBurger>
what kind of terminals are you usin?
21:54
cpu, ram gpu etc?
21:54
<naptastic>
Transmeta Crusoe's between 400 - 900mhz, 512MB RAM, 3 pro/100 nics, and a serial port.
21:54
That's IT.
21:55
<IAssBurger>
yeah
21:56
wonder if there is a limitation on how many connections your nfs server can have
21:56
or if cpu load has anything to do with it
21:57
also are all the clients loading the same image?
21:57
ive no idea if that can be an issue or not, I would assume not
21:59
<naptastic>
yeah, they're all using the same everything except for one client, which is different hardware, so it's got some different pxe options
21:59
it has the same problem, just more reliably.
22:03
<Hyperbyte>
mhm
22:04artista_frustrad has left IRC (artista_frustrad!~fernando@200.247.43.2, Quit: Leaving)
22:05
<IAssBurger>
have you been monitoring the cpu loads on your server?
22:05
<Hyperbyte>
naptastic, sounds like something wrong with /etc/exports on the server. Wild guess here, before nap time. :-)
22:05
G'night.
22:05
<IAssBurger>
ahhh could be
22:05
whats your /etc/exports look like?
22:06
I just use
22:06
/opt/ltsp/ *(ro,no_root_squash,async,no_subtree_check,fsid=0)
22:10khildin has left IRC (khildin!~khildin@ip-80-236-227-85.dsl.scarlet.be, Ping timeout: 246 seconds)
22:11
<naptastic>
IAssBurger, yeah, mine's exactly the same except it's /srv/nfs but yeah
22:11
<IAssBurger>
hey can u tail -f /var/log/syslog
22:11
you even tail your logs like that?
22:11
basically shows them in real time
22:11
might be something relevant in your syslog
22:13
mount.nfs: remote share not in 'host:dir
22:13
hmm in your dhcp.conf do you have root dir speficied?
22:13
<naptastic>
IAssBurger, okay, so after many failed attempts
22:13
(yeah, and I've tried with and without the ip address)
22:13
I've determined that the "remote share not in 'host:dir' format" is NOT part of the problem
22:14
that warning appears on clients that succeed and fail, both
22:14
<IAssBurger>
option root-path "/opt/ltsp/i386";
22:14
<naptastic>
yep, that's definted
22:14
<IAssBurger>
I also have this entry below mine
22:14
if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
22:14
filename "pxelinux.0";
22:14
} else {
22:14
filename "nbi.img";
22:14
<naptastic>
oh yeah, ok
22:14
<IAssBurger>
read that in a ubuntu tut
22:15
no idea if its doing me any good
22:15
lol
22:15
<naptastic>
you can do the same thing using MAC-specific pxelinux.cfg files
22:15
(which is how I'm discriminating between my RXL cards and my Dell workstation)
22:16
<IAssBurger>
NFS Server Is Not Responding
22:16
If your clients exhibit an error, similar to nfs warning: server not responding, it is possible that the kernel is using too large a block size for the NFS packets
22:16
<alkisg>
naptastic: I've seen 2 problems with nfs, not sure if any of those helps. In the first one, I needed to use "nolock" on the clients because statd sometimes wasn't starting due to race conditions. On the other, I had to change the window size on atheros nics, otherwise they had problems (i.e. hanged) specifically with nfs.
22:16
Both in Ubuntu
22:16
<IAssBurger>
In essence the kernel uses a 32K block size, which must be broken down into 1,500 byte datagrams. Since this results in a large number of small datagrams being sent, the client can time out before receiving all the data. Fortunately, the fix is simple enough.
22:17
You must load the file /var/lib/tftpboot/ltsp/pxelinux.cfg/default so that it can be edited. To do this you can use any of the methods previously described in this chapter. Once the file is open, there is a line beginning with APPEND; to the end of this line, you must add one of the following:
22:17
<naptastic>
alkisg, that sounds likely--since some clients work and some clients don't, a race condition seems most likely
22:17
<alkisg>
naptastic: you're using nfsroot=xxx, so that initramfs is mounting root?
22:17
<naptastic>
alkisg, yeah. Does nolock go on the append line too?
22:17
<IAssBurger>
NFSOPTS="-o nolock,ro,wsize=2048,rsize=2048"
22:18
its here
22:18
http://www.informit.com/articles/article.aspx?p=1643921&seqNum=8
22:18
<alkisg>
http://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt
22:18
nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>]
22:19
naptastic: also, since you said they had 3 nics, did you take measures to have the correct one used for the nfs mounting?
22:19* naptastic reads, parses, groks...
22:19
<alkisg>
E.g. ipappend 2?
22:20
<naptastic>
alkisg, yeah, they're on the right nic. That's one nice thing about these: they're set up so ethx *ALWAYS* stays the same
22:20
I actually had to turn the persistent device names off to get it working right
22:21
<alkisg>
IPAPPEND 2 passes BOOTIF in the kernel command line so that you don't have to care about that
22:22
<naptastic>
The parameter in mine is ip=:::::eth2:
22:22
which I find hilarious
22:23
"Use eth2, you're on your own for the rest!!!"
22:23
<alkisg>
Yes, it is, BOOTIF uses mac address and it's much better
22:23
<naptastic>
oh yeah but then I'd need a file for every client, and in the near future there will be hundreds
22:23
no quiero
22:23
<alkisg>
You just put IPAPPEND 2 at the end of pxelinux.cfg/default
22:23
The BOOTIF is passed by pxelinux.0 itself, not by your configuration files
22:24
So you don't need to know the clients mac addresses
22:25
<naptastic>
...interesting...
22:25
it's this whole freaking world of options... who can understand it all?????
22:25
<IAssBurger>
I have an issue gentlement, the time is correct on my server, it is correct in the bios on my client, but when my fat client boots, the time is HOURS off, and if I try to set the time on the client the box freezed
22:26
<alkisg>
Anyway, it's later here, 'night all
22:26alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
22:26
<naptastic>
hmm...
22:26
well, after adding nolock, *none* of the clients boot...
22:26
...I think I need a drink...
22:29bengoa has joined IRC (bengoa!~bengoa@2001:1291:229:2:216:cbff:feab:6cc9)
22:32alexqwesa has left IRC (alexqwesa!~alex@alexo-veto.broker.freenet6.net, Quit: Хана X'ам !!!)
22:35
<IAssBurger>
hey guys
22:36
one thing I noticed . when using thin client, from 1 server to 1 machine I would see upwards of 100mbps traffic when just browsing
22:36
but fat client uses nowhere near that much bandwidth
22:36
running snmp with dude network monitor i can see it
22:37
as well as iptraf from command line on the server
22:40
<naptastic> ...I think I need a drink... <--lol
22:46
NFSOPTS="-o nolock,ro,proto=tcp"
22:53
<naptastic>
IAssBurger, that's because the thin client has to transfer all the pictures of the browser window, where the fat client just needs the actual web data
22:54
<IAssBurger>
yeah I couldnt imagine the demands of a production environment with multiple active thin clients
22:54
would be absurd even on gb
22:54
no wonder your having race conditions
22:54
thats not even considering cpu usage on the server
23:03
<naptastic>
heh
23:03
these are non-graphical, which makes things a lot easier
23:03
but when we get them crunching numbers, we will run into the limits
23:03
anyway, I'm pretty sure at this point that something is really wrong with this server.
23:04
I started suspecting the NIC, so I traded it places with another, re-assigned things, and now none of the networking is, well, working.
23:05
<IAssBurger>
your os will see it as a diff network card
23:05
if your old adapter was eth0
23:05
it will likely see it as eth1
23:05
so edit /etc/network/interfaces
23:05
and change the eth0 lines to eth1 or whatever it happens to now be
23:05
then reboot
23:06
but dont forget to also change it in your dhcp server
23:06
ifconfig and see what it is now
23:06
should be pretty straight forward
23:07
wouldnt hurd to reboot your switches too when you do that, sine your ip will have a new mac adress associated with it, so you avoid any stale arp
23:09
<naptastic>
IAssBurger, yeah, I updated that. You can also change the device names that are being forced by editing /etc/udev/rules.d/70-persistent-net-rules.conf (or equivalent)
23:09
...which apparently I screwed up somehow on this server, because it's empty and my interfaces are getting shuffled...
23:10
...maybe it will regenerate it if I reboot enough times...
23:12
<IAssBurger>
hey, if your devices on your lan are still associating your old nics mac with that ip, packets wont be able to make it to your server
23:12
reboot your stuff, all of it, if you change the nic
23:13vagrantc has left IRC (vagrantc!~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net, Ping timeout: 260 seconds)
23:13
<IAssBurger>
oh nice I didnt know about that net-rules.conf
23:13
thanks
23:20vagrantc has joined IRC (vagrantc!~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net)
23:29bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 240 seconds)
23:31
<IAssBurger>
omgzors
23:35tom____ has joined IRC (tom____!~tom@94-226-90-169.access.telenet.be)
23:36tom____ is now known as Llama_be
23:50Parker955_Away is now known as Parker955