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


Channel log from 30 March 2014   (all times are UTC)

01:11mattcen has left IRC (mattcen!~mattcen@c110-22-201-130.sunsh4.vic.optusnet.com.au, Ping timeout: 240 seconds)
01:52
<Ark74>
hi guys, do you know if this card's flow control can be disabled?
02:11gbaman has left IRC (gbaman!~gbaman@host81-130-114-35.in-addr.btopenworld.com, Remote host closed the connection)
02:23
<Ark74>
http://www.tp-link.com/en/products/details/?model=TG-3468#spec
02:32mattcen has joined IRC (mattcen!~mattcen@c110-22-201-130.sunsh4.vic.optusnet.com.au)
02:42gbaman has joined IRC (gbaman!~gbaman@host81-130-114-35.in-addr.btopenworld.com)
02:47gbaman has left IRC (gbaman!~gbaman@host81-130-114-35.in-addr.btopenworld.com, Ping timeout: 265 seconds)
03:43gbaman has joined IRC (gbaman!~gbaman@host81-130-114-35.in-addr.btopenworld.com)
03:48gbaman has left IRC (gbaman!~gbaman@host81-130-114-35.in-addr.btopenworld.com, Ping timeout: 240 seconds)
03:57Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
04:30Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 240 seconds)
04:44Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
05:45gbaman has joined IRC (gbaman!~gbaman@host81-130-114-35.in-addr.btopenworld.com)
05:49gdi2k has left IRC (gdi2k!~gdi2k@180.190.225.97, Ping timeout: 268 seconds)
05:50gbaman has left IRC (gbaman!~gbaman@host81-130-114-35.in-addr.btopenworld.com, Ping timeout: 264 seconds)
06:01gdi2k has joined IRC (gdi2k!~gdi2k@96.44.183.195)
06:04alkisg has joined IRC (alkisg!~alkisg@ppp089210150101.access.hol.gr)
06:04alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
06:32
<alkisg>
Ark74: it can't be disabled
06:33
Try intel, broadcom, marvell, smc, d-link...
06:46gbaman has joined IRC (gbaman!~gbaman@host81-130-114-35.in-addr.btopenworld.com)
06:50gbaman has left IRC (gbaman!~gbaman@host81-130-114-35.in-addr.btopenworld.com, Ping timeout: 255 seconds)
06:54alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)
07:07
<Ark74>
ethtool -a eth0 would let me know, right?
07:09
or directly with; ethtool -A eth0 autoneg off rx off
07:09
i'll test, thanks
07:23gdi2k has left IRC (gdi2k!~gdi2k@96.44.183.195, Ping timeout: 240 seconds)
07:38Phantomas1 has joined IRC (Phantomas1!~Phantomas@ubuntu/member/phantomas)
07:39Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 265 seconds)
07:40gdi2k has joined IRC (gdi2k!~gdi2k@180.190.225.97)
07:47gbaman has joined IRC (gbaman!~gbaman@host81-130-114-35.in-addr.btopenworld.com)
07:48Ark74 has left IRC (Ark74!~Ark74@189.214.42.128.cable.dyn.cableonline.com.mx, Remote host closed the connection)
07:51gbaman has left IRC (gbaman!~gbaman@host81-130-114-35.in-addr.btopenworld.com, Ping timeout: 264 seconds)
07:58Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
07:59Phantomas1 has left IRC (Phantomas1!~Phantomas@ubuntu/member/phantomas, Ping timeout: 252 seconds)
08:03bennabiy has left IRC (bennabiy!~Thunderbi@24-181-55-79.dhcp.gnvl.sc.charter.com, Ping timeout: 268 seconds)
08:05bennabiy has joined IRC (bennabiy!~Thunderbi@24-181-55-79.dhcp.gnvl.sc.charter.com)
08:12Phantomas1 has joined IRC (Phantomas1!~Phantomas@ubuntu/member/phantomas)
08:14Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 255 seconds)
08:40freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)
08:47gbaman has joined IRC (gbaman!~gbaman@host81-130-114-35.in-addr.btopenworld.com)
09:17andygraybeal has left IRC (andygraybeal!~andy@151.213.206.234, Ping timeout: 240 seconds)
09:31andygraybeal has joined IRC (andygraybeal!~andy@151.213.206.234)
09:42alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
09:49christophe_y2k has joined IRC (christophe_y2k!~christoph@man06-3-78-237-22-85.fbx.proxad.net)
09:50christophe_y2k has left IRC (christophe_y2k!~christoph@man06-3-78-237-22-85.fbx.proxad.net, Client Quit)
09:56mealstrom has left IRC (mealstrom!~Thunderbi@46.63.63.163, Ping timeout: 252 seconds)
09:57mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.63.163)
11:27khildin has joined IRC (khildin!~khildin@ip-80-236-242-245.dsl.scarlet.be)
11:30monkeydiver has joined IRC (monkeydiver!~de3legged@static-108-41-107-210.nycmny.fios.verizon.net)
11:56monkeydiver has left IRC (monkeydiver!~de3legged@static-108-41-107-210.nycmny.fios.verizon.net, Quit: This computer has gone to sleep)
12:06khildin has left IRC (khildin!~khildin@ip-80-236-242-245.dsl.scarlet.be, Remote host closed the connection)
12:07alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
13:59freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Ping timeout: 264 seconds)
14:12freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)
14:49mealstrom has left IRC (mealstrom!~Thunderbi@46.63.63.163, Ping timeout: 264 seconds)
14:50Phantomas1 is now known as Phantomas
14:58mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.63.163)
15:16mealstrom has left IRC (mealstrom!~Thunderbi@46.63.63.163, Ping timeout: 264 seconds)
15:50Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 255 seconds)
15:50Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
16:05Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 264 seconds)
16:07Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
16:15markit has joined IRC (markit!~amministr@dynamic-adsl-78-14-141-108.clienti.tiscali.it)
16:17markit has left IRC (markit!~amministr@dynamic-adsl-78-14-141-108.clienti.tiscali.it, Client Quit)
16:38mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.21.12)
16:53vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
17:09telex has left IRC (telex!~telex@freeshell.de, Remote host closed the connection)
17:10telex has joined IRC (telex!~telex@freeshell.de)
17:22freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Ping timeout: 240 seconds)
17:24markit has joined IRC (markit!~marco@88-149-177-66.v4.ngi.it)
17:36freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)
17:41markit has left IRC (markit!~marco@88-149-177-66.v4.ngi.it, Read error: Connection reset by peer)
18:35mealstrom has left IRC (mealstrom!~Thunderbi@46.63.21.12, Ping timeout: 255 seconds)
18:37khildin has joined IRC (khildin!~khildin@ip-80-236-242-245.dsl.scarlet.be)
18:45Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Quit: Leaving.)
19:28bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
20:36Ltspquestion has joined IRC (Ltspquestion!5adba19a@gateway/web/freenode/ip.90.219.161.154)
20:37
<Ltspquestion>
Yo, if i have 150-200 fat clients, do i need to cluster my ltsp? Or is one server ok?
20:40
<vagrantc>
depends on useage
20:41
<Ltspquestion>
Probably just web browsing, maybe bit of skype etc
20:41
Nice thng about clustering is high availability right..
20:41
<vagrantc>
the fatclients are basically mostly using the server as a fileserver ... so disk i/o becomes important ... and if using the default sshfs homdirs, that eats some cpu.
20:42
<Ltspquestion>
Hmm, have you ever seen ltsp on a cloud?
20:42
<vagrantc>
lag will kill you
20:42
or do you mean a local network cloud?
20:43
<Ltspquestion>
Yeah local
20:43
Im just thinking of creating cluster servers in cloud etc
20:44
Maybe that way it could manage reboots in the case of a crash etc
20:44
<vagrantc>
it just depends on how it's implemented ... if the clients have no idea they're connecting to a cloud vs. a regular computer, then it'd surely work.
20:44
<Ltspquestion>
Just seems complicated..... Cloud on metal, ltsp on cloud
20:44
But i reckon it would be pretty neat
20:44
<vagrantc>
but ip address changes, different processes running on different virtual machines ... that could throw a wrench in things...
20:45
i'm sure something is possible there ... and would be good to explore
20:45
<Ltspquestion>
Ill play with it, report back if people are interested
20:45
<vagrantc>
most of my LTSP networks have been fairly straightforward
20:46
<Ltspquestion>
Do you know what kind of network traffic a thin/fat client generates
20:46
<vagrantc>
server-wise, fanciest thing is just running the LTSP servers on virtual machines
20:46
<Ltspquestion>
Will i be ok with standard switches
20:46
<vagrantc>
alkisg periodically does some numbers on network useage
20:47
main issue with thin clients is multimedia video ... as with modern resolutions and color depth, that eats a ton of bandwidth to stream video over X.
20:48
but with fatclients, it's virtually no different from running from a hard disk
20:48
<Ltspquestion>
Hmm, do fat clients take significantly longer to boot?
20:48
<vagrantc>
not much ... it only loads over the network hat it actually uses.
20:49
<Ltspquestion>
Cool
20:49
So fat clients are good on modern hardware
20:50
Thanks for your help
20:50
<vagrantc>
generally
20:51
there are some quirks with our current implementation, namely anything requiring authenticating with a password (i.e. screensaver)
20:51
or more importantly, screen locker
20:51
we have plans for ltsp6 that will fix that, though it's coming rather slowly
20:52
<Ltspquestion>
So if the screen locks, it sometimes doesnt unlock?
20:53
<vagrantc>
there's no way for it to unlock
20:53
it doesn't have access to the passwords
20:53
or rather the password hashes
20:54
<Ltspquestion>
Hmm so maybe better to stick with thinclients?
20:54
<vagrantc>
though you could run the screenlocker as a remote application, in that case
20:54
i.e. running it on the server
20:54
it really depends on your needs
20:55
<Ltspquestion>
I pretty much just want to run ubuntu
20:55
Let people browse the internet, type docs etc
20:55
<vagrantc>
fatclients take full advantage of modern hardware ... thin clients have limitations based on the technology, but are also more time-tested
20:56
<Ltspquestion>
So screenlock would be better i guess
20:56
<vagrantc>
"browse the internet" doesn't really say much with the modern internet
20:56
i.e. that could mean watching high definition videos :P
20:56gbaman has left IRC (gbaman!~gbaman@host81-130-114-35.in-addr.btopenworld.com, Remote host closed the connection)
20:56
<Ltspquestion>
Hmm maybe :)
20:58
Fat client sounds better
20:59
<vagrantc>
at the last ltsp hackfest, we were talking about shifting the focus of LTSP from thin clients to fat clients... still supporting both, but maye changing defaults
21:00
<Ltspquestion>
Well as long as it works as youd hope, i think its probably the better one?
21:01
<vagrantc>
if you have the hardware to support it, it's definitely a nice option
21:02
<Ltspquestion>
So how do you solve the screensaver thing?
21:02
Can you confogure the screenlock to work with an ldap server?
21:03
<vagrantc>
you can run individual apps on the server or on the local hardware ... so you can run the locker on the server
21:03
<Ltspquestion>
Ah cool
21:03
So its not really an issue
21:04
<vagrantc>
it takes some effort
21:04
but it's possible.
21:05
i think some projects also set up pam-ldap or some such so that the fat clients can authenticate properly ...
21:05
our default setup is kind of a hackish workaround to avoid needing to set up ldap
21:06
i think the debian-edu project has ldap authenticated fat clients
21:07gbaman has joined IRC (gbaman!~gbaman@host81-130-114-35.in-addr.btopenworld.com)
21:14
<Ltspquestion>
I guess if its cloud based
21:14
And you create a beast of an insstance
21:14
You might not need clustering?
21:14
Also if the cloud dealth with high availability etc for you
21:17
Ok gtg thx for your help
21:18Ltspquestion has left IRC (Ltspquestion!5adba19a@gateway/web/freenode/ip.90.219.161.154, )
21:25bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 264 seconds)
21:57khildin has left IRC (khildin!~khildin@ip-80-236-242-245.dsl.scarlet.be, Quit: I'm gone, bye bye)
23:44PhoenixSTF has joined IRC (PhoenixSTF!~rudiservo@78.29.155.245)