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


Channel log from 1 September 2017   (all times are UTC)

00:19kjackal has left IRC (kjackal!~quassel@2a02:587:311f:4f00:c525:be71:d53e:3387, Ping timeout: 255 seconds)
00:19kjackal has joined IRC (kjackal!~quassel@2a02:587:310e:e00:99a4:c630:31d4:d08f)
00:24kjackal has left IRC (kjackal!~quassel@2a02:587:310e:e00:99a4:c630:31d4:d08f, Ping timeout: 255 seconds)
00:24kjackal has joined IRC (kjackal!~quassel@2a02:587:310a:7f00:99a4:c630:31d4:d08f)
00:45billlong has left IRC (billlong!~user@61.170.176.23, Ping timeout: 260 seconds)
01:15lucascastro has left IRC (lucascastro!~lucas@138.68.106.79, Remote host closed the connection)
01:49adrianor1 has joined IRC (adrianor1!~adrianorg@177.156.230.137)
01:52adrianorg has left IRC (adrianorg!~adrianorg@189.58.229.145.dynamic.adsl.gvt.net.br, Ping timeout: 240 seconds)
05:04cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
05:04achyut has joined IRC (achyut!75f75622@gateway/web/freenode/ip.117.247.86.34)
05:05
<achyut>
Hi
05:05
Good Morning
05:07
we are planning to use LTSP
05:08alkisg_web has joined IRC (alkisg_web!51ba1402@gateway/web/freenode/ip.81.186.20.2)
05:08
<achyut>
hello
05:08
<alkisg_web>
hello
05:09
<achyut>
if we want to user 50 client in LTSP server, then what type of configuriton we need
05:10
<alkisg_web>
What kind of clients? CPU/RAM?
05:11
<achyut>
we have 50 users want to connect LTSP server through pxe boot
05:11
<alkisg_web>
How much RAM do the clients have
05:11
1 GB? 256 MB?
05:11
<achyut>
2 Gb
05:12
each one have atleast 2gb and max 4 gb RAM
05:12
<alkisg_web>
With fat clients you don't need a good server
05:12
!ltsp-manager
05:12
<ltsp>
ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager
05:13
<alkisg_web>
So, a normal server with 4 or 8 gb ram, a recent cpu, and a gigabit nic, is fine
05:13
<achyut>
ik
05:13
ok
05:13
i'm using above url to install ltsp server..https://help.ubuntu.com/community/UbuntuLTSP/LTSPQuickInstall
05:14
after installing i'm not able to boot from client through pxe..getting DHCP not found error
05:14
<alkisg_web>
That's a very very old tutorial, it might have issues
05:14
Don't use it
05:14
Use either ltsp-manager or ltsp-pnp:
05:14
!ltsp-pnp
05:14
<ltsp>
ltsp-pnp: ltsp-pnp is the recommented method to install and maintain LTSP for "usual" setups. Since it doesn't involve chroots, it requires little to no command line to maintain it. It automatically supports both thin and fat ltsp clients. https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
05:14
<alkisg_web>
Best, use ltsp-manager
05:16
<achyut>
which one easy to install as i have not enough knowledge on linux
05:16
<alkisg_web>
This one:
05:16
!ltsp-manager
05:16
<ltsp>
ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager
05:17
<achyut>
also let me know whcih is the best desktop to install LTSP
05:17Statler has joined IRC (Statler!~Georg@p579FE37C.dip0.t-ipconnect.de)
05:19
<achyut>
also let me know whcih is the best desktop to install LTSP
05:19
<alkisg_web>
It says that in the page, read the page. It's best to use MATE. It also has a link to download the cd.
05:20
<achyut>
ok
05:21
Thank you
05:28
<alkisg_web>
You're welcome
05:42ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:24alkisg_web is now known as alkisg
06:24alkisg has left IRC (alkisg!51ba1402@gateway/web/freenode/ip.81.186.20.2, Changing host)
06:24alkisg has joined IRC (alkisg!51ba1402@ubuntu/member/alkisg)
06:28mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
06:36jgee has left IRC (jgee!~jgee@dynamic-ip-cr2001187375.cable.net.co, Ping timeout: 240 seconds)
06:49alkisg has left IRC (alkisg!51ba1402@ubuntu/member/alkisg, Quit: Page closed)
06:50alkisg has joined IRC (alkisg!51ba1401@ubuntu/member/alkisg)
07:29Statler has left IRC (Statler!~Georg@p579FE37C.dip0.t-ipconnect.de, Remote host closed the connection)
07:59wim1 has joined IRC (wim1!~Thunderbi@WEGC203033.UNI-GRAZ.AT)
08:20wim1 has left IRC (wim1!~Thunderbi@WEGC203033.UNI-GRAZ.AT, Quit: wim1)
08:22Statler has joined IRC (Statler!~Georg@p579FE46F.dip0.t-ipconnect.de)
09:02Eric5 has left IRC (Eric5!~eric@sdi.iut-valence.fr, Ping timeout: 240 seconds)
09:17Eric5 has joined IRC (Eric5!~eric@sdi.iut-valence.fr)
09:24kjackal has left IRC (kjackal!~quassel@2a02:587:310a:7f00:99a4:c630:31d4:d08f, Ping timeout: 255 seconds)
09:25kjackal__ has joined IRC (kjackal__!~quassel@2a02:587:3101:ce00:99a4:c630:31d4:d08f)
09:33kjackal has joined IRC (kjackal!~quassel@2a02:587:310e:4900:99a4:c630:31d4:d08f)
09:36kjackal__ has left IRC (kjackal__!~quassel@2a02:587:3101:ce00:99a4:c630:31d4:d08f, Ping timeout: 255 seconds)
09:47fzimper has joined IRC (fzimper!4e2b136d@gateway/web/freenode/ip.78.43.19.109)
10:19Eric5 has left IRC (Eric5!~eric@sdi.iut-valence.fr, Ping timeout: 240 seconds)
12:19Eric5 has joined IRC (Eric5!~eric@sdi.iut-valence.fr)
12:32cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Remote host closed the connection)
13:40mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
14:23markit has joined IRC (markit!~marco@88-149-177-66.v4.ngi.it)
14:26
<markit>
hi, is not strictly ltsp related but I need for a script to modify /etc/cups/cups-browsed.conf. Is there in GNU/Linux a command to modify config files that are key=value or key value? And if the key is not found, add the "key value" pair automatically?
14:26
btw, cupsd.conf has 'key=value' while cups-browsed.conf is 'key value' (space)!
14:43
<||cw>
markit: of hand I don't know, one usually does those things with awk and/or sed though
14:43
a more general and active linux-focused channel would probably be a better place to ask
14:48vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
14:49
<alkisg>
markit: afaik, the cupsctl command that I told you yesterday parses and modifies that file
14:53
<vagrantc>
alkisg: so, ltsp-manager is now waiting in NEW: https://ftp-master.debian.org/new.html
14:54
<alkisg>
I saw it! Cool!
14:55
<vagrantc>
some things are waiting a few months, hopefully we'll be luckier than that :)
14:55
<alkisg>
Haha
15:11
<fzimper>
Hi! Any tips on how to run ltsp-manager from a fat-client? ltsp-remoteapps doesn't work
15:12
<vagrantc>
interesting use-case :)
15:13
<fzimper>
Well, should be a pretty common one, don't you think so?
15:13
<alkisg>
fzimper: did you enable ltsp-remoteapps in lts.conf?
15:13
!epoptes
15:13
<ltsp>
epoptes: Epoptes is a computer lab administration and monitoring tool. It works on Ubuntu and Debian based labs with LTSP or non-LTSP servers, thin and fat clients, standalone workstations, NX clients etc. More info: http://www.epoptes.org
15:13
<alkisg>
epoptes.org/doc/fats or something, there's documentation on how to run remoteapps there
15:13
<fzimper>
Yes. I can run e.g. firefox using remoteapps
15:13
Or Chromium, Thunar
15:14
<alkisg>
Ah
15:14
Run remoteapps xterm then
15:14
And launch ltsp-manager from there
15:14
And see if you get any errors
15:14
<fzimper>
Mousepad seems to be tricky. Understandibly it's always the complex ones that cause trouble ;-)
15:14
let me try
15:18
<alkisg>
(documentation for epoptes is in http://www.epoptes.org/documentation/fat-clients)
15:18
<fzimper>
https://pastebin.com/r4fQH2Cv
15:19
<alkisg>
fzimper: sudo nano/usr/share/polkit-1/actions/*ltsp-manager*.policy
15:20
And play with the "allow_admin_keep" etc entries; put them to "yes" if you have to,
15:20
save file and retry, no reboots necessary
15:20* alkisg waves for now, will read irclogs later
15:20
<fzimper>
ok. Epoptes works fine by just executing 'ltsp-remoteapps epoptes'
15:22
Interesting, the server almost came to a halt now. Memory usage increasing. Mousepad (s. above) consuming all of it
15:28
I'll look into the policy stuff later on. For now I tried to run "sudo ltsp-manager" in xterm. That seems to work.
15:30
<vagrantc>
huh
15:34
<markit>
alkisg: cupsctl works fine, but not for /etc/cups/cups-browsed.conf only for cupsd.conf, that is the one to modify with "BrowseRemoteProtocols none"
15:35
alkisg: but in general, with my setup scripts I often have the need of modify some .conf file, since now I've used sed, but seems strange that no one has created a "general purpouse" tool
16:00vsuojanen has joined IRC (vsuojanen!~valtteri@83-136-248-31.uk-lon1.host.upcloud.com)
16:01
<vsuojanen>
http://wiki.ltsp.org/wiki/Locating_Speedy_Solutions_In_Finance
16:03
<sutula>
Trying to set up a new LTSP server (old one is ancient). Started down the Ubuntu 17.04 server path and eventually got that working by hand (ltsp-build-server and manual install of packages).
16:03
Was guided by this channel to use 16.04 and ltsp-manager, per the bot instructions.
16:03
I've been all over the pages starting here http://wiki.ltsp.org/wiki/Ltsp-manager and here https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
16:03
<vsuojanen>
i was given this in search results and it didn't work ^^^
16:03
<sutula>
I must be missing something very basic, maybe in the network hardware layout? I can't get my thin client to mount the NBD filesystems.
16:03
The mount command is:
16:03
/sbin/nbd-client [server IP] -N /ltsp/adm64 /dev/nbd0 -swap -persist -systemd-mark
16:03
Yet the server exports only swap and /opt/ltsp/amd64
16:04* sutula thought he saw a bug report by vagrantc some time ago related to NBD, but was hoping the channel had some better solutions.
16:05
<sutula>
Also, I have not seen any instructions on how to configure my DHCP server, so have adapted from what I used to use ages ago. Maybe this is the issue?
16:08
<vsuojanen>
sutula: are you first time asking this here after starting you adventure to setup a new LTSP server?
16:09
<sutula>
vsuojanen: A few weeks ago I was given the guidance to try 16.04 and ltsp-manager here
16:10
<vsuojanen>
did you ask the bot or someone here?
16:10
<sutula>
Asked the channel, someone in the channel answered thru the bot
16:13
That was on 8/28
16:18
<vsuojanen>
I have been very long away from this channel. I don't know where to continue guiding. the DHCP server should not need anymore LTSP specific configurations as it should not be initially setup on the LTSP server
16:22
the ltsp-pnp instructions guide you to a setup which uses dnsmasq and external dhcp server.
16:25
<sutula>
Maybe I am struggling because the old ltsp server/clients are coexisting on the same network. I am trying to take one client and boot from the new server until I have it working, and not take down the old clients yet.
16:26
I have been able to do that by changes in my DHCP server's config file, but maybe I am messing up the stuff dnsmasq would have done?
16:26* sutula will study dnsmasq
16:27
<vsuojanen>
if you have enough resources on some machine setup a quick virtual environment and start with http://wiki.ltsp.org/wiki/Ltsp-manager
16:29
<sutula>
Thanks for the repointer...when I checked about a week ago, steps 5 and 6 pointed to empty pages. They have content now.
16:32
<vsuojanen>
yeah. it may be the issue. np
16:32
<sutula>
This makes me think I should re-update my server and try again...perhaps things have been fixed last few days.
16:36
<vsuojanen>
from wiki that the services on LTSP server itself would not have changed that much from ltsp-pnp instructions. http://wiki.ltsp.org/wiki/Ltsp-manager/Initial_setup
16:37
but Ltsp-manager, it should be well tested if it is published and recommended here
16:39
<sutula>
So far, my symptoms point to confusion between my main DHCP server and dnsmasq that ltsp-manager configures. Your comments have at least given me somewhere to look. Thanks!
16:40
<vsuojanen>
sutula: one thing with the setup is almost every time boot the LTSP server after the client image is updated
16:44
I mean after the client image is first time created. The purpose of course is that LTSP server should not have to be rebooted after image updates. but that time is when you setup your server or change the server ip
16:47
<sutula>
OK, thanks! Looking at what ltsp-manager has done with dnsmasq config file, I can see that my old/main DHCP server is stepping on values. Starting there and will try again.
16:57Eric5 has left IRC (Eric5!~eric@sdi.iut-valence.fr, Ping timeout: 240 seconds)
17:56markit has left IRC (markit!~marco@88-149-177-66.v4.ngi.it, )
17:56mmarconm has joined IRC (mmarconm!~Marcelo@200-163-110-237.dial.brasiltelecom.net.br)
18:02
<alkisg>
sutula: don't use non-lts ubuntu versions with ltsp, I don't support them
18:02
E.g. 17.04 has broken a nbd package
18:02
To fix it you'd need to remove the initial / in the nbd server configuration file
18:03
<sutula>
alkisg: OK, saw that in a bug report, but dropping back to 16.04 anyway.
18:03
<alkisg>
Use 16.04.3. MATE is prefered, but lubuntu should work fine too.
18:03
<sutula>
alkisg: Current problem is that existing DHCP server seems to conflict with what you're trying to do with dnsmasq
18:03
<alkisg>
If they both send the same settings, how can they conflict?
18:04
If your existing dhcp is broken, dnsmasq can't override it
18:04
So it's broken setup, not broken method...
18:04
<sutula>
Ahhh...so copy the dnsmasq settings into main DHCP server's config file?
18:04
<alkisg>
No
18:04
3 dhcp servers:
18:04
(1) dhcp that doesn't send boot filename, e.g. router
18:05
(2) real dhcp, e.g. isc-dhcp, that sends a boot filename
18:05
(3) proxydhcp, that doesn't send lease, but ONLY boot filename
18:05* sutula has case 2
18:05
<alkisg>
(1) and (3) mix fine
18:05
<sutula>
:(
18:05
<alkisg>
(2) doesn't need (3), it works fine alone
18:05
<mmarconm>
alkisg: i asked bedore, but i had to go, so 'what is ltsp-manager for ?'
18:05
<alkisg>
If you have (2) and (3), then (2) is the one that sends the settings
18:05
<mmarconm>
before*
18:06
<alkisg>
So (3) is ignored
18:06
So, if you have 2+3 and it's not working, the problem is in the (2) settings, they're wrong
18:06
I.e. not related to dnsmasq at all;they just need to be fixed
18:06
mmarconm: it's the easiest method to install ltsp; did you read the docs?
18:07* mmarconm didnt read the docs, shame on you mmarconm =(
18:07
<alkisg>
!ltsp-manager
18:07
<ltsp>
ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager
18:07
<alkisg>
Be glad that devs took the time to document things. It's rare! Honor that by reading them! :P :D
18:07
<mmarconm>
i always install from terminal
18:08
<alkisg>
You can install ltsp-manager by apt install ltsp-manager, from the terminal
18:08
<mmarconm>
aahahhah Ok i want to make a video teaching how to install ltsp, from new guys, portugues of course
18:08
<alkisg>
That then will solve a lot of issues so that you don't need to search/apply the fixes yourself
18:08
<mmarconm>
here almost nobody knows ltsp
18:10
<sutula>
alkisg: Still a little confused...if I have isc dhcp server running, seems I have to copy settings into there, e.g.:
18:10
# The next-server setting decides which machine is the ltsp server
18:10
next-server 192.168.1.109;
18:10
# Copied from alfred2: dnsmasq conf file (should not be necessary):
18:10
filename "/ltsp/amd64/pxelinux.0";
18:10
option root-path "/var/lib/tftpboot/";
18:10
Is there also a "dhcp-option" setting necessary?
18:11
<alkisg>
sutula: I'm not using isc-dhcp so I don't know its settings
18:11
next-server usually points to the tftp server, which should be the ltsp server
18:11
root path is /opt/ltsp/amd64
18:11
Not /var/lib/tftpboot, that's wrong there
18:12
There's an example dhcpd.conf in the ltsp package...
18:12
<sutula>
alkisg: I am seeing the above settings in dnsmasq's config file written by lts-manager
18:12
<mmarconm>
on my configuration, i delete this line next-server 192.168.1.109; and
18:13
<alkisg>
sutula: dnsmasq is a tftp server there
18:13
isc-dhcp isn't a tftp server
18:13
Since you're using (2), why are you reading dnsmasq config which is ignored?
18:13
Read isc-dhcp docs, not dnsmasq docs...
18:14
ltsp-manager configures dnsmasq for tftp, dns and proxydhcp and sometimes dhcp too
18:14
Don't just blindly try to copy settings...
18:14
Read the dhcpd.conf that is shipped by ltsp for isc-dhcp
18:14
<sutula>
alkisg: Right, just looking there to see what directories should be used in the isc dhcp server
18:15
<alkisg>
look at the dhcpd.conf example, not at the dnsmasq.conf example
18:15
for the directories to use
18:15
<sutula>
ok
18:17
<mmarconm>
alkisg: just for purpose of testing, i build ltsp on docker machine and works pretty well
18:20
<sutula>
alkisg: I'm afraid I'm even more confused...sorry. I have installed ltsp-manager per your web pages. There is no /opt/ltsp/amd64 subdirectory on the LTSP server, only an /opt/ltsp/images/
18:21Statler has left IRC (Statler!~Georg@p579FE46F.dip0.t-ipconnect.de, Quit: Leaving)
18:22
<mmarconm>
sutula: u must to create one
18:23
when on create a ltsp image this subdirectory ll be create
18:24
<fzimper>
alkisg: feedback on the policy settings for ltsp-manager which you recommended to change. If I set them to 'yes' all works fine, though obviously that's a bit insecure. Any other setting doesn't work.
18:27kjackal has left IRC (kjackal!~quassel@2a02:587:310e:4900:99a4:c630:31d4:d08f, Ping timeout: 264 seconds)
18:29
<sutula>
mmarconm: Oh good grief, I hadn't considered use of magic. I should have known alkisg was a wizard.
18:29
Works perfectly with root path of /opt/ltsp/amd64
18:31* mmarconm ll stay quite
18:36
<alkisg>
sutula: dhdpc.conf example comes with ltsp-server-standalone, not with ltsp-manager, but glad you solved it ;)
18:36
fzimper: it's not insecure, please file a bug report so that I update them
18:36
!ltsp-bug
18:36
<ltsp>
ltsp-bug: To file a bug report for upstream LTSP, go to https://bugs.launchpad.net/ltsp
18:39
<alkisg>
sutula: /opt/ltsp/amd64 is mentioned in /etc/nbd-server/conf.d/ltsp_amd64.conf, the header line there
18:39
That's what root-path is, when we're talking about nbd
18:39
And we put it that way so that it's the same dhcp configuration as nfs
18:43vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 255 seconds)
18:44
<sutula>
alkisg: OK, by the way, this is the first time I've tried fat client (old server was too much trouble to configure); ltsp-manager is making it waaaaay easy. Awesome work!
18:58Statler has joined IRC (Statler!~Georg@p579FE46F.dip0.t-ipconnect.de)
19:05Statler has left IRC (Statler!~Georg@p579FE46F.dip0.t-ipconnect.de, Remote host closed the connection)
19:09
<alkisg>
Cool! :)
19:46
<mmarconm>
alkisg: how i install ltsp-manager ?
19:46
is avaliable on repo ?
19:46
!ltsp-manager
19:46
<ltsp>
ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager
19:48
<mmarconm>
i get it xD
20:00mmarconm has left IRC (mmarconm!~Marcelo@200-163-110-237.dial.brasiltelecom.net.br, Quit: Leaving)
20:01jgee has joined IRC (jgee!~jgee@dynamic-ip-cr2001187375.cable.net.co)
20:06ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
20:11
<sutula>
alkisg: Should you have time for a last question, I'd really like to stick with ltsp-manager but do have a few older i386 clients. Is there some manual steps I can take to build i386 images while the server and most clients are amd64, or is it an all-or-nothing?
20:27
<alkisg>
sutula: if you read the docs, you'll see that it says "use i386 if you have both amd64 and i386 clients"
20:27
If you don't have any machines with 16+ GB RAM, there's no reason to use amd64
20:27
(with 16+ GB RAM there's a bug where i386 gets too slow)
20:28
Now, if for some reason you don't want that, yes you can build an i386 chroot, but it's not a very well documented feature of ltsp
20:29
ifcpu64 of pxelinux allows you to automatically select the correct chroot, and ltsp has some code for that somewhere
20:29
<sutula>
alkisg: I did see it in the docs, but wondered whether it was reasonable to supplement i386 by hand
20:29
I'm guessing it's dicey given fat client support?
20:29
<alkisg>
Do you have machines with 16+ GB RAM?
20:29
<sutula>
I don't, so i386 can work
20:29
<alkisg>
Right
20:30
You only get 5% less speed, and gain some free RAM, so it's not a significant difference
20:30
So just install the server with i386 live cd
20:30
<sutula>
It's a "start install all over", but should go faster now that I've been through it 3 times :)
20:30
<alkisg>
Hehe
20:30
<sutula>
thanks much for the consulting!
20:30
<alkisg>
np; i should start charging for that :P
20:30* alkisg waves
20:31* sutula would be glad to send beer money
20:32
<||cw>
you also only have the speed penalty if the clients have more than 4GB ram
20:32
<alkisg>
The 5% speed is 64bit processing vs 32bit processing, faster math... not related to ram
20:33
The 16+ GB RAM slowness issue is because of bad highmem managing in the kernel
20:33
(5% is very rough approximation; in real math apps it can be much more, in office apps less, etc)
20:33* alkisg waves for real now :)
20:35
<||cw>
5% is the 0.0001% of apps that actually take advantage of it, which is maybe gaming and CAD and scientific processing
20:36
PAE is the main performance penalty in 32bit
22:40fzimper has left IRC (fzimper!4e2b136d@gateway/web/freenode/ip.78.43.19.109, Ping timeout: 260 seconds)
23:31gehidore is now known as alad2
23:31alad2 is now known as gehidore
23:51dgroos has joined IRC (dgroos!~dagro001@205.215.175.117)
23:52
<dgroos>
hello!
23:53
I’m working to get my fat 16.04 clients to authenticate to AD and I think I’m most of the way there.
23:55
The server is running on a 2 NIC setup. I can ssh into the server from a computer on the WAN (ssh ADuser@server.ip.address) and it works!
23:58
When I login via ssh, it creates the user on the server, but with none of the folders e.g. ~/Desktop. However, then when I log in sitting directly at the server, it logs in and creates that home directory structure. Nice!