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


Channel log from 20 September 2018   (all times are UTC)

00:05adrianorg has joined IRC (adrianorg!~adrianorg@179.187.25.127.dynamic.adsl.gvt.net.br)
00:13adrianorg has left IRC (adrianorg!~adrianorg@179.187.25.127.dynamic.adsl.gvt.net.br, Read error: Connection reset by peer)
00:31adrianorg has joined IRC (adrianorg!~adrianorg@179.187.25.127.dynamic.adsl.gvt.net.br)
00:46vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
01:04ltsp has joined IRC (ltsp!bot@ltsp.org)
05:23ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
05:44
<alkisg>
vagrantc: I forgot to delete debian/epoptes-client.if-up. How should we manage me pushing to debian branch now?
05:45
I propose that I directly push there but only in the debian/ dir, i.e. never sync the upstream source code, leave that up to you,
05:46
and, in cases where the result won't be buildable, I'd use another branch and do a pull request to you, so that you first rebase to the new upstream code, and then pull my changes
05:46
And of course you can have *-backports branches that I won't touch at all
05:46
Does that work for you?
06:00lucascastro has left IRC (lucascastro!~lucascast@177-185-139-186.isotelco.net.br, Remote host closed the connection)
10:09gdi2k has joined IRC (gdi2k!~gdi2k@host109-151-4-123.range109-151.btcentralplus.com)
11:11lucascastro has joined IRC (lucascastro!~lucascast@177-185-139-186.isotelco.net.br)
11:16pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, Ping timeout: 252 seconds)
11:35pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme)
11:40pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, Ping timeout: 252 seconds)
12:16
<mwalters>
oops, I got another wild hair... How is LTSP with being virtualized? "Why am I gonna goof around with all this nonsense when I could just build a vm, then move it over"
12:17pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme)
12:17
<highvoltage>
yeah no reason you can't goof around with it in a vm
12:18
<mwalters>
Well, I want to move it to production as a vm
12:19
History: I have 4 production installs, 3 of them on (what was) massive hardware (16 cores, 128gb memory, all thin clients). They're all 14.04, though... with April 2019 fast approaching, we need to do something
12:19
I really don't care to try in-place upgrades from 14.04->16.04->18.04
12:40Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
13:14
<alkisg>
mwalters: sure, you can deploy ltsp as a vm
13:44
<mwalters>
Cool, I didn't think there'd be any weirdness, but that's usually when there is ;)
13:50
alkisg et al: this is a great project. Really appreciate all you have put into it, and your responsiveness in here. I've been messing around with linux on and off for about 15 years, but this is probably the first time I've seen an implementation that "just works" in an office environment.
13:50
<alkisg>
Great :)
13:52
<mwalters>
I haven't done much desktop development, but maybe when the dust of starting this new job settles, I can carve out some time in my week to contribute.
14:08
<alkisg>
That would be great as well, ltsp is low on development power
14:10
<mwalters>
Our agency has definitely benefited greatly from ltsp, I imagine convincing my boss to set aside a couple of hours wouldn't be too difficult
16:06
<alkisg>
!nbd-client
16:06
<ltsp>
nbd-client: To try mounting the NBD image from the client initramfs: nbd-client 192.168.67.1 -N /opt/ltsp/i386 /dev/nbd0
17:25elaurencio has joined IRC (elaurencio!c837bdac@gateway/web/freenode/ip.200.55.189.172)
17:25
<elaurencio>
Hi people
17:25
Anybody is online now???
17:26
<alkisg>
elaurencio: 27 people online :)
17:26
!ask
17:26
<ltsp>
ask: Don't ask to ask a question, simply ask it, and if someone knows the answer, they'll respond. Please hang around for at least a full hour after asking a question, as not everybody constantly monitors the channel.
17:27
<elaurencio>
I ask because yesterday I lauch a question and nonody reply to me
17:28
<alkisg>
Just ask it again and wait in case anyone can answer it :)
17:28
!printer
17:28
<ltsp>
printer: Quick how-to: RCFILE_01="/usr/sbin/jetpipe /dev/usb/lp0 9100 &" in lts.conf, reboot client, then go to server's add printer dialog, and specify network printer → jetdirect → ltsp123.local
17:28
<alkisg>
!fat
17:28
<ltsp>
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'
17:28
<alkisg>
!fatclient-printers
17:28
<ltsp>
fatclient-printers: You can publish printers on your network so that fat clients see them, by launching "system-config-printer" and selecting Server → Settings → Publish shared printers connected to this system
17:28
<alkisg>
This one ^
17:29
<elaurencio>
alkisg sorry for my bad english, i am a spanish user
17:30
well this is my situation
17:30
<alkisg>
Don't worry I'm greek. Go on. :)
17:30
<elaurencio>
i have 10 fat client with 5 diferent printers
17:30
<alkisg>
The printers are connected to the clients?
17:30
And the clients are netbooted, ltsp fat clients?
17:30
<elaurencio>
yes
17:31
the model of those printer is diferent betwen then
17:31
when i conect usb port in fat client
17:31
the printer no add to default printer in fat client
17:32
but is detected by sistem in lsusb
17:32
<alkisg>
Do you want to share the printers to the network, or do you want each client to print only to its own printer?
17:32
<elaurencio>
the second way
17:32
<alkisg>
Put this in lts.conf: CUPS_SERVER=localhost
17:32
And reboot the clients
17:33
<elaurencio>
in default section or in the space of particular fat client
17:33
???
17:33
<alkisg>
Better in the space of those fat clients
17:33
So that other clients can see the server printers, if you ever have a printer on the server
17:34
<elaurencio>
that's the situation: the server is virtualice in proxmox server
17:34
<alkisg>
That doesn't matter, it can still have printers with usb passthrough
17:34
Or it can have printers that come from fat clients, to be shared on the server
17:36
<elaurencio>
the server is in the node, and not accesible for all personal
17:36
for that
17:36
the printer is located in fat client by usb
17:36
<alkisg>
Yes I understood
17:37
(08:32:42 μμ) alkisg: Put this in lts.conf: CUPS_SERVER=localhost
17:37
<elaurencio>
i was use Ardence Citrix for the solution of thing client
17:37
but for orientation of boss i have to migrate to gnu/linux solution
17:38
i choose ltsp and that's is the only problem to fix
17:38
<alkisg>
Isn't Citrix from 2006 or so?
17:38
<elaurencio>
Ardence Citrix 4.5
17:39
<alkisg>
Yeah, ancient. :)
17:39
Throw it away!
17:39
<elaurencio>
by the way, i use ubuntu 18.04 lts
17:44vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
18:04
<alkisg>
elaurencio: ok, did you solve the problem with my advice?
18:04
vagrantc: heya!
18:05
vagrantc: we need to remove debian/epoptes-client.if-up, it's even harmful now that we have a systemd unit
18:05
It pkills the systemd-spawned epoptes-client and causes some chaos, either delayed connections or in lubuntu no connection at all
18:17lucascastro has left IRC (lucascastro!~lucascast@177-185-139-186.isotelco.net.br, Quit: Leaving)
18:19
<vagrantc>
alkisg: ok
18:20
<elaurencio>
alkisg: no, no solution of the problems
18:20
i send you by pv the lts.conf
18:22
<vagrantc>
alkisg: and now epoptes only works with systemd? so we should also probably add an explicit dependency...
18:24
<elaurencio>
alkisg: you read my recived my private msg ???
18:25
sorry
18:25
alkisg: are you read the msg that i send you???
18:25
<vagrantc>
elaurencio: patience...
18:25
<elaurencio>
the sorry was for my way of write the question ;)
18:27
<alkisg>
vagrantc: I think we removed both the sysvinit and upstart units, so yeah epoptes only starts from systemd now
18:28
elaurencio: you rebooted the client and it doesn't show the printer in cups?
18:28
elaurencio: does it show up if you try to add the printer from the fat client "add printers" dialog?
18:29
vagrantc: can I push things (like the if-up removal) directly to the debian branch/dir, or do you want me to have a debian-alkis branch instead?
18:29
<vagrantc>
alkisg: you can push directly ... can always fix up any issues :)
18:29
<elaurencio>
alkisg: i reboot the fat client, and in the dialog of add printter not show the usb printer
18:30
<alkisg>
elaurencio: do you have epoptes installed, so that I could take a look/
18:30
?
18:30
!epoptes
18:30
<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
18:30
<elaurencio>
alkisg: sorry for ask, what is epoptes???
18:37
<mwalters>
tangent: How do you pronounce epoptes? e-pop-tees?
18:38
<alkisg>
Who is tangent?
18:38
There's an mp3 in epoptes.org with the pronunciation
18:39
<mwalters>
tangent is likely lost in translation, a thought originating from the current conversation, but with out actually having anything to add to it
18:39lucascastro has joined IRC (lucascastro!~lucascast@189.90.38.210.jupiter.com.br)
18:40
<mwalters>
also, that helped ;)
18:41
<vagrantc>
alkisg: there are also mentions of if-up.d in epoptes-client/epoptes-client comments
18:44
<elaurencio>
alkisg: my repositorie server not allow now, but in web manager cups when i try to add a printer, the usb printer is showed
19:01
<alkisg>
vagrantc: yeah I should remove those as well
19:08
<elaurencio>
alkisg: the epoptes is install in the ltsp server and in the fat client image
19:08
<alkisg>
The documentation for epoptes installation is at epoptes.org/installation
19:08* alkisg waves for now, later...
19:21ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
19:25lucascastro has left IRC (lucascastro!~lucascast@189.90.38.210.jupiter.com.br, Remote host closed the connection)
19:32
<elaurencio>
!printer
19:32
<ltsp>
printer: Quick how-to: RCFILE_01="/usr/sbin/jetpipe /dev/usb/lp0 9100 &" in lts.conf, reboot client, then go to server's add printer dialog, and specify network printer → jetdirect → ltsp123.local
19:59lucascastro has joined IRC (lucascastro!~lucascast@186.193.178.113.jupiter.com.br)
20:09elaurencio has left IRC (elaurencio!c837bdac@gateway/web/freenode/ip.200.55.189.172, Ping timeout: 256 seconds)
20:11elaurencio has joined IRC (elaurencio!c837bdac@gateway/web/freenode/ip.200.55.189.172)
20:31Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
20:35lucascastro has left IRC (lucascastro!~lucascast@186.193.178.113.jupiter.com.br, Ping timeout: 252 seconds)
21:01
<vagrantc>
alkisg: should i wait a couple days to see if you find any more issues with epoptes before uploading the fix?
21:02lucascastro has joined IRC (lucascastro!~lucascast@189.90.45.62.jupiter.com.br)
21:09
<alkisg>
vagrantc: I've a known issue with how I handle automatic restarts when epoptes aborts... I'm not sure if I'll find the patience to solve it soonish... but yeah wait a couple of days, it might come to me :D
21:25
<elaurencio>
alkisg: look that, i created the file printers.conf by cups in web managger and copy in the fat-clients image in /etc/cups folder, update the image, add in lts.conf CUPS_SERVER=127.0.0.1 and reboot the fat-client, and yes, the printer is showed in the printers panel configuration
21:30
alkisg: I ws guide by the https://help.ubuntu.com/community/UbuntuLTSP/localprinter
21:32
alkisg: but in this post sugest that if copy the printers.conf in cups user profile only this user can use the printers declared, but not working with me
21:35lucascastro has left IRC (lucascastro!~lucascast@189.90.45.62.jupiter.com.br, Remote host closed the connection)
21:38
<vagrantc>
alkisg: ok, i'll wait a bit on the upload
21:53vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
22:27elaurencio has left IRC (elaurencio!c837bdac@gateway/web/freenode/ip.200.55.189.172, Quit: Page closed)
23:09fiesh has left IRC (fiesh!~fiesh@hq.wsoptics.de, Ping timeout: 240 seconds)