|01:16||GodFather has joined IRC (GodFatheremail@example.com)|
|01:35||GodFather has left IRC (GodFatherfirstname.lastname@example.org, Ping timeout: 260 seconds)|
|05:14||Statler has joined IRC (Statler!~Georg@p579FE689.dip0.t-ipconnect.de)|
|06:20||markus_e92 has left IRC (email@example.com, Ping timeout: 240 seconds)|
|06:22||markus_e92 has joined IRC (firstname.lastname@example.org)|
|06:31||Eric4 has joined IRC (Eric4email@example.com)|
|06:56||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|07:02||bobptz has joined IRC (bobptz!c23feff3@gateway/web/freenode/ip.188.8.131.52)|
|07:23||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
|07:42||wim1 has joined IRC (wim1!~Thunderbi@WEGC203033.UNI-GRAZ.AT)|
|07:43||Leolo_2 has left IRC (Leolo_2firstname.lastname@example.org, Ping timeout: 240 seconds)|
|07:45||wim1 has left IRC (wim1!~Thunderbi@WEGC203033.UNI-GRAZ.AT, Client Quit)|
|08:21||Statler has left IRC (Statler!~Georg@p579FE689.dip0.t-ipconnect.de, Remote host closed the connection)|
|08:41||gvy has joined IRC (gvy!~mike@altlinux/developer/mike)|
|09:09||lucascastro has left IRC (email@example.com, Remote host closed the connection)|
|09:12||Statler has joined IRC (Statler!~Georg@mail.lohn24.de)|
|09:14||Statler has joined IRC (Statler!~Georg@mail.lohn24.de)|
|10:13||markus_e92 has left IRC (firstname.lastname@example.org, Ping timeout: 260 seconds)|
|10:15||markus_e92 has joined IRC (email@example.com)|
|10:48||wim1 has joined IRC (wim1!~Thunderbi@WEGC203033.UNI-GRAZ.AT)|
|11:04||gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)|
|11:28||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|11:41||roseco has joined IRC (roseco!2955b816@gateway/web/freenode/ip.184.108.40.206)|
|11:45||wim1 has left IRC (wim1!~Thunderbi@WEGC203033.UNI-GRAZ.AT, Quit: wim1)|
|11:47||Eric4 has left IRC (Eric4firstname.lastname@example.org, Ping timeout: 240 seconds)|
on LTSP, I notice that all thing clients have the same address IP that the LTSP server. How can we identify only each thing client ? regards.
|12:07||ZAJDAN has joined IRC (ZAJDAN!4d30954b@gateway/web/freenode/ip.220.127.116.11)|
|12:17||Eric4 has joined IRC (Eric4email@example.com)|
|12:27||gvy has joined IRC (gvy!~mike@altlinux/developer/mike)|
Any idea how i can on my fat clients set hostname from dns on boot ? I guess on a regular debian/ubuntu it's set by dhclient, and on ltsp ip parameters are set by pxe + ltsp script right ? Is there a simple way or shall i write a script ?
roseco: you mean as detected by a web server or whatever? the thin client user session run on the server itself, so that's why. what do you need to know the client for?
Eric4: pretty sure it still uses dhclient.
normal dhcp/dns works here anyway
Thx. Still discovering how it works under the hood.
|13:30||manilse has joined IRC (manilse!c362e40a@gateway/web/freenode/ip.18.104.22.168)|
sur un serveur eole-eclair, les applications non-embarquéees ne se chargent pas sur le client
|13:38||manilse has left IRC (manilse!c362e40a@gateway/web/freenode/ip.22.214.171.124, Quit: Page closed)|
|13:56||quinox has left IRC (firstname.lastname@example.org, Quit: WeeChat 1.7)|
|13:57||quinox has joined IRC (email@example.com)|
|14:12||professor^Servid has joined IRC (professor^Servid!bd4826dd@gateway/web/freenode/ip.126.96.36.199)|
good morning. I'm teacher and i'm using epoptes on lab info
but a i can't broadcast my screen to my students
anyone can help me?
|14:15||professor^Servid has left IRC (professor^Servid!bd4826dd@gateway/web/freenode/ip.188.8.131.52)|
!localxterm | echo roseco:
roseco: localxterm: Any applications that you launch on a thin client actually runs on the server, not on the client itself. If you want to open a program on the client locally, you can type 'ltsp-localapps <program>' in a run dialog or in a terminal. For example, 'ltsp-localapps xterm' to open a terminal running on the client.
Eric4: ltsp in ubuntu/debian use ipconfig or udhcpc, and normally set dns from dhcp. But if you're using ipappend 3, which is the default in ltsp-pnp, then there's no second dns request, so you have to use lts.conf HOSTNAME
|14:42||ben_roose has joined IRC (firstname.lastname@example.org)|
|14:58||roseco has left IRC (roseco!2955b816@gateway/web/freenode/ip.184.108.40.206, Ping timeout: 260 seconds)|
|15:05||adrianorg has left IRC (email@example.com, Ping timeout: 240 seconds)|
|15:54||gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)|
|16:06||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|16:42||Leolo_2 has joined IRC (Leolo_2firstname.lastname@example.org)|
|17:13||JR_ has joined IRC (JR_!ad858910@gateway/web/freenode/ip.220.127.116.11)|
Hey, running 4 LTSP servers on a VM box...plenty of mem and cpu...no swapping. Load balance with simple dns round-robin. All thin clients are diskless workstation terminals...last generation..
cannot get firefox to be performant
compression of SSH seems faster, as turning it off seems to make FF almost unusable
15 users or so per ltsp instance
i'd strongly recommend exploring LTSP fat clients
how much RAM on the thin clients?
is there any big ticket areas to consider...it seems that the VM environment really is a killer
!fat-client | echo JR_
JR_ I do not know about 'fat-client', but I do know about these similar topics: 'epoptes-fat-clients'
because firefox loves RAM
also, have you tested running firefox at off-peak hours, when nobody but you are using LTSP?
given that firefox is essentially a massive multimedia platform these days, and the network bandwidth required for that on a thin client is *huge*
I do not know about 'fat', but I do know about these similar topics: 'fatclient-printers', 'epoptes-fat-clients', 'fat-internal-disks', 'fat-passwd', 'fat-sudo', 'fatclients'
!fatclients | echo JR_
JR_ fatclients: Nowadays LTSP supports thin and fat clients. They are both diskless and netbooted from the same LTSP chroot, but while thin clients run the session on the server and transfer the screen, fat clients run the session locally with their own CPU/RAM, thus performing amazingly better. See also !ltsp-pnp and https://help.ubuntu.com/community/UbuntuLTSP/FatClients
this is great info
i have been running LTSP for well over a decade
ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
and struggling to keep it going athough I really want to
unfortunately, the thin client model isn't really viable with modern software
at least, most software isn't written with thin clients in mind
|17:21||Statler has left IRC (Statler!~Georg@mail.lohn24.de, Remote host closed the connection)|
what vagrantc said.
any time a user needs firefox or openoffice, I switch them to a fat client or a full desktop
and so, we're mostly pushing fat clients these days ... still get the benefits of central management and network booting
it also means the servers don't have to be nearly as powerful
of course, you need more powerful clients, but even fairly old clients still can function well as fat clients
main limitation is ram
|17:32||markus_e92 has left IRC (email@example.com, Ping timeout: 255 seconds)|
|17:33||markus_e92 has joined IRC (firstname.lastname@example.org)|
|17:34||lucascastro has joined IRC (email@example.com)|
vagrantc: Hi there... I asked about the ldm/ltspfs project move, and translations won't be lost. Do we want to do it?
I also committed a readme that documents how we're managing translations, because it can be a bit confusing...
|17:43||JR_ has left IRC (JR_!ad858910@gateway/web/freenode/ip.18.104.22.168, Quit: Page closed)|
|17:59||kjackal_ has joined IRC (kjackal_!~quassel@2a02:587:3109:6d00:445:f469:3791:efba)|
|18:24||Eric4 has left IRC (Eric4firstname.lastname@example.org, Ping timeout: 260 seconds)|
|18:24||lucascastro has left IRC (email@example.com, Remote host closed the connection)|
alkisg: kind of depends on how subprojects go ... e.g. can i get a list of bugs related to all subprojects? how hard is it to find?
|18:41||lucascastro has joined IRC (firstname.lastname@example.org)|
|18:47||lucascastro has left IRC (email@example.com, Remote host closed the connection)|
vagrantc: launchpad doesn't support subprojects. It supports "series", which are versions of the same repository, and "project groups", to declare common security settings
To get a list of ltsp bugs, you go to:
ltsp-bug: To file a bug report for upstream LTSP, go to https://bugs.launchpad.net/ltsp
For LDM, it would be: https://bugs.launchpad.net/ldm
And for LTSPFS, it would be: https://bugs.launchpad.net/ltspfs
Since it's different code trees with different releases and with different packages, I'm not sure what a "subproject" would mean in that context
And of course it's possible to move bug reports to other projects, if they're filed against the wrong project
wasn't ltspfs originally it's own project?
alkisg: i guess, what is the harm in having "series" that are unrelated?
ltspfs doesn't have a project in https://launchpad.net/ltspfs
alkisg: i think it used to
vagrantc: do you have subprojects in bugs.debian.org?
Deleting a project requires a launchpad admin to do it
alkisg: no, but i have ways at looking at all my bugs
I don't know who would have filed such a bug report for that
Same in launchpad too, there are ways to look at one's bugs in all projects
e.g. all bugs related to ~/ltsp-upstream ?
alkisg: it was a long time ago, maybe before you were even involved
alkisg: with ltspfs
https://bugs.launchpad.net/~ltsp-upstream lists bugs that are assigned to the team
Not all the bugs of all the projects of the team
but that requires someone to actually assign them to the team?
Yes but we don't want that
for the most part, i use launchpad as a storage for revision control, and only nominally deal with bugs... but this sounds like it would make it harder to deal with bugs
I can't see why
I did have trouble in the past when I was confused with all the bugs under ltsp
it's just not clear to me what we really gain by splitting them into separate projects ...
But if each package has its own bugs, I can't see why it would be more confusing
Well, we did a mistake and we're correcting it
Isn't that reason enough?
i recall this mistake being intentionally implemented to avoid fragmenting all the various projects in ltsp...
but honestly, i don't follow launchpad's organizational structure well at all...
mostly, i just don't want to have to keep changing VCS URLs
But those are broken since we moved to git
So those need to be fixed anyway
And, projects have static URLs, unlike series
Compare https://code.launchpad.net/ltsp (=project) with https://code.launchpad.net/~ltsp-upstream/ltsp/+git/ldm (series)
ok, that's a much simpler URL, as long as it stays that way, that's preferrable.
Yes projects have a single / in their urls
No long paths, for bugs, code, questions, etc etc
if it makes it simpler and not prone to change, i'm all for it. :)
I thought it would take at least 30 more minutes to convince you :P :D
i remember when we switched to git, the previous git repository URLs changed, which seemed pointless
but hopefully we won't have to go through all that again
more than this one time....
I think so. Unless we move to github :D
and then back again!
We'll have some small changes when launchpad supports git in translations
may as well switch to gitlab along the way
i'll welcome the fixes to translations
oh, and there's pagure, i guess
If github starts providing full integration with a specific translations service, and translators move away from launchpad, I'll consider move there... other than that... I'll stick with launchpad, I like that it has a lot of services integrated
i struggle with launchpad, but luckily alkisg usually points me to things i should be aware of :)
|20:03||kjackal_ has left IRC (kjackal_!~quassel@2a02:587:3109:6d00:445:f469:3791:efba, Ping timeout: 255 seconds)|
|20:59||bennabiy has left IRC (bennabiy!~bennabiy@unaffiliated/bennabiy, Remote host closed the connection)|
|21:08||ben_roose has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|21:44||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|