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


Channel log from 11 February 2015   (all times are UTC)

00:20
<map7>
Mikhail, I've started multiple VPN connections on my thin clients and I think I have on fat clients also.
00:20
I don't use NetworkManager though I use the pptp scripts
00:21
then turn on & off the VPN's with pon & poff commands, which are just icons for staff members
01:32andygraybeal has left IRC (andygraybeal!~andy@h220.193.213.151.dynamic.ip.windstream.net, Quit: Ex-Chat)
01:51telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
01:52telex has joined IRC (telex!teletype@freeshell.de)
02:28vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
02:46jbermudes has left IRC (jbermudes!~quassel@76.74.178.212, Quit: No Ping reply in 180 seconds.)
02:48jbermudes has joined IRC (jbermudes!~quassel@76.74.178.212)
02:49gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Remote host closed the connection)
02:49cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 245 seconds)
02:55jbermudes has left IRC (jbermudes!~quassel@76.74.178.212, Quit: No Ping reply in 180 seconds.)
02:59jbermudes has joined IRC (jbermudes!~quassel@76.74.178.212)
03:19doctari has left IRC (doctari!~doctari@2602:30a:2ccf:9f00:5cda:b53:7443:cd33, Ping timeout: 245 seconds)
03:20doctari has joined IRC (doctari!~doctari@2602:30a:2ccf:9f00:133:4bb9:7be9:c05a)
03:20vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Ping timeout: 250 seconds)
03:22vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
04:00gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
04:04gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Ping timeout: 240 seconds)
04:28vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Ping timeout: 250 seconds)
04:43alkisg_web has joined IRC (alkisg_web!2ec65b1a@gateway/web/freenode/ip.46.198.91.26)
05:17alkisg_web has left IRC (alkisg_web!2ec65b1a@gateway/web/freenode/ip.46.198.91.26, Ping timeout: 246 seconds)
05:23freedomrun has joined IRC (freedomrun!~quassel@unaffiliated/freedomrun)
06:05eemeli has joined IRC (eemeli!3e94cd0c@gateway/web/freenode/ip.62.148.205.12)
06:15eemeli has left IRC (eemeli!3e94cd0c@gateway/web/freenode/ip.62.148.205.12, Quit: Page closed)
06:25cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
06:29work_alkisg is now known as alkisg
06:40fabzster has joined IRC (fabzster!c4d26e76@gateway/web/freenode/ip.196.210.110.118)
06:40
<fabzster>
Hi Everyone
06:41
<alkisg>
Hello
06:42
<fabzster>
I setup LTSP on a Ubuntu server and have a INTEL DE3815TYKHE ATOM Thin Client tft is setup and running and options from my windows server DHCP have been set my thin client finds the image via PXE and tries to boot
06:42
what arch should I use for the Intel thin client?
06:43
when the thin client boots using amd64 arch i get errors
06:47
<alkisg>
What errors?
06:48
It's possible that you need i386 arch, not amd64.
06:55mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
07:28
<fabzster>
cool just busy creating the client files and will try that
07:28
starts with getaddrinfo failed
07:28
then some mount errors
07:34
<alkisg>
That client is 64bit so it should support amd64 just fine, look elsewhere for the issue, not in the arch
07:34
Upload some screenshot from your mobile phone if you can't type the errors
08:06
<fabzster>
where can I upload it to?
08:10ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)
08:10
<alkisg>
Try https://img.bi/
08:10
Or dropbox, google drive, wherever
08:14
<fabzster>
http://tinypic.com/r/szj5lf/8
08:14
k just added it there
08:14
<alkisg>
!nbd-client
08:14
<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
08:15
<alkisg>
Try that command, but replace the ip with your server's ip
08:15
Which ubuntu version is that?
08:15vmlintu has joined IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi)
08:16
<alkisg>
Trusty, probably...
08:16
Also replace i386 with amd64
08:18
<fabzster>
k so change my dhcp server option back to the amd arch client directory
08:18
where must i run that command, sorry i have very limited linux skills
08:19
<alkisg>
In the client initramfs prompt
08:19
<fabzster>
ahh ok will do now
08:22
k so it returned negotiation: size 323MB
08:23
bs= 1024 , sz = 339689472 bytes
08:24
I have ubuntu server 14.04.1
08:28
is there a log that I could look for an error in
08:32jbermudes has left IRC (jbermudes!~quassel@76.74.178.212, Changing host)
08:32jbermudes has joined IRC (jbermudes!~quassel@unaffiliated/jbermudes)
08:35freedomrun has left IRC (freedomrun!~quassel@unaffiliated/freedomrun, Remote host closed the connection)
08:41
<alkisg>
It might be a problem with your dhcp server, e.g. having both a dhcp server in the ltsp server, and an external one like a router, would produce the symptoms you're seeing
08:41* alkisg needs to go, bb
08:41alkisg is now known as work_alkisg
08:45
<fabzster>
thanks
08:45mugele has joined IRC (mugele!5824c7b9@gateway/web/freenode/ip.88.36.199.185)
08:45
<fabzster>
I have only 1 dhcp server on my network on my Windows server
08:49jay_ has left IRC (jay_!jay@gateway/shell/blinkenshell.org/x-xhwrvbjzmyxnoyjb, Quit: Lost terminal)
08:49mugele has left IRC (mugele!5824c7b9@gateway/web/freenode/ip.88.36.199.185, Ping timeout: 246 seconds)
08:50
<fabzster>
anyone else able to assist?
08:57vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi, Ping timeout: 246 seconds)
08:59
<work_alkisg>
!ipappend
08:59
<ltsp`>
ipappend: o temporarily solve DHCP problems in the initramfs, try putting IPAPPEND 3 after the APPEND line in /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default. More info: http://www.syslinux.org/wiki/index.php/SYSLINUX#IPAPPEND_flag_val_.5BPXELINUX_only.5D
08:59
<work_alkisg>
fabzster: try this ^
09:00
bb
09:01
<fabzster>
thanks alot will try that
09:07
where do i put it
09:07
label ltsp-NBD menu label LTSP, using NBD kernel vmlinuz-3.13.0-45-generic append ro initrd=initrd.img-3.13.0-45-generic init=/sbin/init-ltsp quiet splash root=/dev/nbd0 ipappend 2
09:07
do I replace the ipappend 2 with 3?
09:08
<work_alkisg>
yes
09:09
<fabzster>
k so just change 2 to 3
09:09
done
09:09
<work_alkisg>
reboot client
09:09
<fabzster>
do I ave to reboot the server?
09:09
<work_alkisg>
no
09:09
<fabzster>
or jst the thin client
09:11
that worked!!!!!!!!!!!!!!!
09:12
so what do I have to do in the future and why is it occuring?
09:12vmlintu has joined IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi)
09:13
<work_alkisg>
because you have not configured right your windows dhcp server
09:13
bb later!
09:18fabzster has left IRC (fabzster!c4d26e76@gateway/web/freenode/ip.196.210.110.118, Ping timeout: 246 seconds)
09:46fabzster has joined IRC (fabzster!c4d26e76@gateway/web/freenode/ip.196.210.110.118)
09:46
<fabzster>
my client runs super slow
09:56telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
09:58telex has joined IRC (telex!teletype@freeshell.de)
10:22gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
10:22
<work_alkisg>
!directx
10:22
<ltsp`>
directx: If you want to turn off encryption to the workstation, which will speed up performance at the cost of security, you need to specify LDM_DIRECTX=True in your lts.conf file. Type !docs in IRC to get a link to the current documentation
10:22work_alkisg is now known as alkisg
10:22gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Read error: Connection reset by peer)
10:22
<alkisg>
fabzster: see this ^
10:22
and also see this:
10:23
!ltsp-pnp
10:23
<ltsp`>
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
10:23
<alkisg>
!ltsp-fatclients
10:23
<ltsp`>
Error: "ltsp-fatclients" is not a valid command.
10:23
<alkisg>
!fatclients
10:23
<ltsp`>
fatclients: You may find some info about the Ubuntu/LTSP implementation of fat clients at https://help.ubuntu.com/community/UbuntuLTSP/FatClients
10:23gbaman has joined IRC (gbaman!~gbaman@31.205.109.64)
10:45gbaman_ has joined IRC (gbaman_!~gbaman@31.205.104.150)
10:49Faith has joined IRC (Faith!~paty@unaffiliated/faith)
10:49gbaman has left IRC (gbaman!~gbaman@31.205.109.64, Ping timeout: 245 seconds)
10:49gbaman_ has left IRC (gbaman_!~gbaman@31.205.104.150, Ping timeout: 246 seconds)
11:01vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi, Ping timeout: 250 seconds)
11:25vmlintu has joined IRC (vmlintu!~vmlintu@37-219-3-75.nat.bb.dnainternet.fi)
12:24bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
12:26Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
12:33gbaman has joined IRC (gbaman!~gbaman@104.40.144.249)
12:41vmlintu has left IRC (vmlintu!~vmlintu@37-219-3-75.nat.bb.dnainternet.fi, Ping timeout: 250 seconds)
12:53gbaman has left IRC (gbaman!~gbaman@104.40.144.249, Ping timeout: 245 seconds)
13:20gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
13:24gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Ping timeout: 240 seconds)
13:25vmlintu has joined IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi)
13:25markit has joined IRC (markit!~marco@88-149-177-66.v4.ngi.it)
13:45gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
14:20gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Remote host closed the connection)
14:30cliebow has left IRC (cliebow!~cliebow@gw-rsu24-co.rsu24.org, Quit: Ex-Chat)
14:39
<fabzster>
@alkisg I reinstalled the server now I get to the login prompt enter the details and it just stays there
14:44
circle just keeps turning and goes nowhere
15:13mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
15:17
<fabzster>
anyone?
15:30
<Hyperbyte>
fabzster, why did you reinstall the server?
15:31
<markit>
fabzster: just a shoot in the dark: are you sure username and password are ok? can you login in the server with that account?
15:39zama has left IRC (zama!~zama@unaffiliated/stryx/x-3871776, Ping timeout: 245 seconds)
15:40zama has joined IRC (zama!~zama@unaffiliated/stryx/x-3871776)
16:03markit has left IRC (markit!~marco@88-149-177-66.v4.ngi.it, )
16:03alkisg is now known as work_alkisg
16:11gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
16:36alkisg_web has joined IRC (alkisg_web!c23fefeb@gateway/web/freenode/ip.194.63.239.235)
16:45AlexPortable has joined IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-iameoxkcepbuomfw)
16:47Angel has joined IRC (Angel!5dc4a513@gateway/web/freenode/ip.93.196.165.19)
16:47Angel is now known as Guest60560
16:49
<Guest60560>
Hi. I made a debian-ltsp server withproxy-dhcp in 64 bit. but only 64bit clients can boot. the i mad ltsp-build-client --arch i386. but no help. the 32bit-clients get errormessage. what i do forgett?
16:51
<alkisg_web>
Modify your dhcpd settings
16:51
(or dnsmasq settings)
16:54
<Guest60560>
wherer axactly i have to do this? these are my first steps with ltsp
16:55
1. su 2. apt-get update && apt-get dist-upgrade 3. apt-get install ltsp-server-standalone ltsp-client dnsmasq 4. ltsp-config dnsmasq nano /etc/dnsmasq.d/ltsp-server-dnsmasq.conf # IP ranges to hand out. #dhcp-range=192.168.67.20,192.168.67.250,8h nano /etc/ltsp/update-kernels.conf BOOT_METHODS=NBD #delet NFS IPAPPEND=3 4. uname -r # (3.2.0-4-686-pae) 5.dpkg-reconfigure linux-image-3.2.0-4-686-pae 6. ltsp-update-image -
16:55
this is what i have don
16:56
oops, looks like spam. sorry
17:00
<alkisg_web>
nano /etc/dnsmasq.d/ltsp-server-dnsmasq.conf and replace amd64 with i386
17:03
<Guest60560>
nice. i found some lines where i can change this. should i reboot after i changed this?
17:05
<alkisg_web>
service dnsmasq restart
17:06alkisg_web has left IRC (alkisg_web!c23fefeb@gateway/web/freenode/ip.194.63.239.235, Quit: Page closed)
17:13Guest60560 has left IRC (Guest60560!5dc4a513@gateway/web/freenode/ip.93.196.165.19, Ping timeout: 246 seconds)
17:29telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
17:30telex has joined IRC (telex!teletype@freeshell.de)
18:01vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi, Ping timeout: 245 seconds)
18:29dave has joined IRC (dave!40079a49@gateway/web/freenode/ip.64.7.154.73)
18:29dave is now known as Guest76105
18:29Guest76105 has left IRC (Guest76105!40079a49@gateway/web/freenode/ip.64.7.154.73)
18:31cjg has joined IRC (cjg!40079a49@gateway/web/freenode/ip.64.7.154.73)
18:34
<cjg>
Hello. I'm looking for a way for my ltsp fat clients to check that they are still connected to the ltsp server. I'm looking at this from a precautionary standpoint in that if the connection is lost for a period of time the thin client will alert the user and reboot. Kind of like a watchdog I suppose. Is this in place on ltsp?
18:41
And would it be best to use this watchdog from the individual client or from the ltsp server?
18:46
<Hyperbyte>
You just said you're running both fat and thin clients. That correct?
18:46
Also, I'm curious why you want this. Is your server or network instable?
18:50
<cjg>
We're running just fat clients (no thin clients). Our network is quite stable, but I'm considering using ltsp in our small office and I support them remotely. I do have a hands and eyes resource onsite if need be. I'm still learning ltsp and want to be proactive if I can to alleviate any issues that might arise down the road.
18:51AlexPortable has left IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-iameoxkcepbuomfw, Quit: Connection closed for inactivity)
18:53
<cjg>
A bit more detail for you...the ltsp server runs in a VM (hosted on a Dell 710). I have iDRAC access to the host server and server redundancy setup so I'm comfortable that I can get to the LTSP server without issue. But it's the clients that connect to the ltsp server I'm concerned about. My testing has not found any issues so far in my lab. These fat clients use rdp to an assigned Windows VM running on our lan.
18:54
If an issue was to arise I want to make sure I have a solution in place to solve the problem with the clients at each workstation in the office reconnecting to their assigned virtual machines.
19:35gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Remote host closed the connection)
19:44alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
19:45
<Hyperbyte>
cjg, right, when you're using rdp this actually makes sense. But still you have to ask yourself: why would the computers suddenly lose their network connection?
19:45
And what happens when they do?
19:46vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
19:47
<Hyperbyte>
Since their OS is mounted over network, losing the network connection is like ripping out the harddisk while the OS is running.
19:47
You have to ask yourself: is it possible for an operating system to recover from that and if it is, would you want it to?
19:48
<alkisg>
vagrantc: $ grep NTPSERVER /usr/share/ltsp/init-ltsp.d/50-set-time
19:48
sed -i -e 's/^NTPSERVERS=".*"/NTPSERVER="'$TIMESERVER'"/' /etc/default/ntpdate
19:48
Typo there, missing "S"
19:48
<vagrantc>
ouch
19:48gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
19:48
<alkisg>
...but, ntpdate doesn't use NTPSERVERS from that file
19:49
It uses /etc/ntp.conf, which we create even if it doesn't exist
19:49
<vagrantc>
it's a maze to figure out what it does use ... last i looked it's a series of fallbacks
19:49
<alkisg>
So I think that we had 2 issues there, that resulted in everything working fine :P
19:49
<Hyperbyte>
cjg, simply put, it's not possible to recover. At most you could put some stuff in ram (running program) that checks if there's a connection, and if there isn't, sends reboot command to the kernel (and then it's hoping that the kernel hasn't panicked yet from it's root filesystem loss)
19:49
<alkisg>
vagrantc: I propose that we just complete remove the /etc/default/ntpdate editing, and only leave a comment that it's not used
19:50
<Hyperbyte>
cjg, and even -if- you manage to reboot, then what? The clients will hang in BIOS with "please insert boot medium", because they'll reboot within ~10 seconds and there's a very small chance that the server can be back in those 10 seconds.
19:52
<alkisg>
xnbd-client does have a --recovery-command-reboot for that
19:52
<vagrantc>
alkisg: i'm not so convinced...
19:52
alkisg: but i can look into it more
19:53
<alkisg>
vagrantc: NTPDATE_USE_NTP_CONF=yes inside /etc/default/ntpdate, means "use /etc/ntp.conf", and that's on by default
19:54
vagrantc: but, why don't we change the time at boot? now some problems are caused, e.g. if a client has the wrong date, epoptes won't start because the certificate isn't yet valid
19:54
<vagrantc>
alkisg: but if it's not set to yes, then we should either set it to yes, or add the NTPSERVERS stuff
19:54
<alkisg>
I think we once did, but reverted to letting the ntpdate service manage it instead?
19:54Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)
19:54
<alkisg>
If it's not set to yes, then the user that changed it should put correct values in NTPSERVERS there too
19:55
<vagrantc>
i really prefer for init-ltsp.d to only edit the configuration of ervices and let the services do the right thing.
19:55
<alkisg>
He obviously decided not to use lts.conf but conffile editing
19:55
Me too, but there's a point there
19:55
<cjg>
Hyperbyte, thank you for the comments. This completely makes sense. So far in my testing I've not found a reason to be concerned with losing connection as my fat client has stayed connected via RDP for days at a time (even through an ltsp server reboot).
19:55
<alkisg>
ntpdate has a -b setting exactly for boot-time services
19:56
<vagrantc>
alkisg: file a bug, or bugs, and we can discuss it :)
19:56
<alkisg>
After the bug report?! Where's the fun in that?! :)
19:56
<vagrantc>
i mean, we can discuss it anyways, but our schedules don't always line up
19:57* alkisg prefers to file bug reports after he knows what to propose there
19:57
<vagrantc>
heh
19:57
well, you know what you propose so far :)
19:57
<alkisg>
Knipwim has a generic 50-set-time that I believe would work for us too
19:57
So we can just remove the debian-specific one
19:58
<vagrantc>
i don't have the time to dig into it at the moment, so a bug report would make it easy for me to add to my todo llist
19:58
<cjg>
One further question regarding clients (in my case fat clients) and the ltsp server. As I just mentioned, my rdp connection from the fat client stays connected even if my ltsp server reboots. Does the fat clients need to be rebooted (in that they should reestablish their connection tot he ltsp server) whenever the ltsp server gets rebooted? Not that we do frequent reboots.
19:58
<alkisg>
vagrantc: Sure, np, we can talk about that another time
19:58
<cjg>
Just checking on best practice for those times when we shutdown the ltsp server for backup purposes.
19:58
<vagrantc>
alkisg: and i've never been good at digging into irc logs
19:58
<alkisg>
There are too many bug reports open currently, I was looking to close that one quickly without too much fuss
19:59
No worries I'll remind you another time
19:59* vagrantc hrms
19:59
<alkisg>
The typo is in code that doesn't have any effect anyway
20:06
<Hyperbyte>
cjg, rebooting server is like pulling harddisk from all clients at once. The programs that are running will keep running, if they don't cause kernel panics meanwhile. Since you're only running RDP, it's a relatively simple environment, so it keeps running.
20:08
cjg, if you want to do something with the client (like, restart rdp for whatever reason) it might not work, because it can't find the RDP client. But then again, it might work just as well because the RDP client could be cached in memory.
20:08
cjg, in other words: completely unpredictable. If something does go wrong, reboot fixes everything.
20:13
<cjg>
Hyperbyte..Good point. Is there an instruction from ltsp to view all connected clients by IP or logged in name? I found an awk script while googling that may have given me this detail...I never did get the script to work in that it didn't return any information (and no errors). Does ltsp have a built in command?
20:14
<Hyperbyte>
alkisg knows this one. :-)
20:19vmlintu has joined IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi)
20:23Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Quit: I Leave)
20:23
<cjg>
Thank you Hyperbyte. I'll await a reply when alkisg has time to reply.
20:42vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi, Ping timeout: 256 seconds)
20:58vmlintu has joined IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi)
21:31walter_ has joined IRC (walter_!d4febef2@gateway/web/freenode/ip.212.254.190.242)
21:31
<walter_>
hi all
21:31
is it possible on a debian wheezy ltsp installation to setup a ubuntu chroot for servig thin ltsp clients?
21:33
<championofcyrodi>
walter_ : i think ltsp-pnp does something like that
21:35
maybe not actually.
21:35vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
21:39
<walter_>
nope, ltsp-pnp doesnt do it
21:39
:-(
21:40
i did: ltsp-build-client --dist utopic --mirror http://hk.archive.ubuntu.com/ubuntu --arch i386
21:41
but ltsp-build-client uses the wrong security mirrors
21:42
<championofcyrodi>
hmmm, i did a client build myself a little while ago... noticed firefox title bar looked a bit weird w/ some other language's font.
21:43
not sure what it was
21:43
kind of english, but had something else going on.
21:44
i remember someone explaining how to do the build w/ verbose mode... and there was an Environment variable you could set for the mirror to use
21:44
i think it might have just been $MIRROR
21:44
http://manpages.ubuntu.com/manpages/lucid/man8/ltsp-build-client.8.html
21:44
--mirror
21:45
Select the mirror to download packages from. file:/// and http:// URLs are supported.
21:45
also check your DNS... i think it finds the best mirror using DNS or something
21:45
*tries to find the best mirror
21:47
maybe you want this one? http://us.archive.ubuntu.com/ubuntu/dists/trusty-security/
21:56
<cjg>
alkisg - Is there an instruction from ltsp to view all connected clients by IP or logged in name? Does ltsp have a built in command?
21:59
<championofcyrodi>
from the server, i use 'ps -ef | grep priv' and it will show the ssh connections from the clients by username
21:59
cjg^
22:00
ps -ef | grep priv | awk '{print $9}'
22:00
that get's you a little closer
22:01
ps -ef | grep sshd | grep priv | awk '{print $9}'
22:02
lol
22:02
even better...
22:02
just type 'users'
22:03
http://www.manpagez.com/man/1/users/
22:17
<cjg>
championofcyrodi - Outstanding! This works perfectly. I don't know how I missed this. Is there a way to capture the IP address of each connected user through the terminal as well?
22:20
<championofcyrodi>
netstat -taupen
22:20
will show all connections...
22:21
and from there you can likely parse the sshd connections... maybe map them by pid to the sshd session in ps -ef
22:21
but there might be an even easier way, i don't know
22:22gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Remote host closed the connection)
22:26
<alkisg>
!client-list
22:26
<ltsp`>
client-list: to get a list of all nbd-clients (which sometimes is the same as ltsp clients), run: netstat -tn | sed -n 's/.*:10809 *\([0-9.]*\):.*/\1/p' | sort -Vu
22:26
<alkisg>
cjg: check if this helps you ^
22:26
No internal command, nope
22:26
You can do something similar with ssh connections if you want...
22:28
(I just read the backlog, championofcyrodi has already told you that, ok... :))
22:28
<championofcyrodi>
:p
22:29
<alkisg>
There's also "w"
22:29
Better than users :)
22:29ricotz has left IRC (ricotz!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)
22:33
<cjg>
alkisg and championofcyrodi - Thanks to you both. I can put these together into a bash script now to give me the client name and the IP address. I've confirmed I can see the IP addresses using the netstat command alkisg gave me.
22:33
I'm curious...Does client-list refer to something within ltsp though?
22:34
<alkisg>
The netstat command also gives you non-logged in terminals
22:34
<cjg>
Is that a command.
22:34
<alkisg>
It just lists the nbd connections
22:34
It's not strictly "ltsp clients", like ssh isn't always "ltsp users"
22:34
...but usually nbd is for ltsp, at least for ltsp users :)
22:35
<cjg>
So netstat command give me non-logged in terminals as well. good to know. Can the nbstat command be tweaked to show or identify non-logged in as opposed to logged in as well?
22:35
<alkisg>
No, you'd need to cross-reference the nbd list with the ssh list
22:36
<cjg>
Ok. Just catching up here on all this information (Gold Jerry, Gold!). So the 'w' command gives me the name and IP address as well. Where can I find what each column refers to using 'w'?
22:37
<alkisg>
man w
22:37
<cjg>
right on. Thank you!
22:37
<alkisg>
np
22:39vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
22:56
<alkisg>
Whoops vagrantc you beat me in the commit
22:57
Although I think $TIMESERVER should go inside the quotes to prevent syntax errors in case one tries to put multiple servers there...
22:57
np, it's code that doesn't take effect anyway, next topic... :)
22:58
- # Modify /etc/default/ntpdate
22:58
- sed -i -e 's/^NTPSERVERS=".*"/NTPSERVER="'$TIMESERVER'"/' /etc/default/ntpdate
22:58
+ # Modify /etc/default/ntpdate. Note that currently that file sets
22:58
+ # NTPDATE_USE_NTP_CONF=yes, so it gets TIMESERVER from /etc/ntp.conf.
22:58
+ sed -i -e "s/^\(NTPSERVERS=\).*/\1\"$TIMESERVER\"/" /etc/default/ntpdate
22:58* alkisg waves
22:58alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
23:02gbaman has joined IRC (gbaman!~gbaman@89.185.154.123)
23:04gbaman has left IRC (gbaman!~gbaman@89.185.154.123, Client Quit)
23:27
<vagrantc>
hm. cleaner sed, but takes more thinking to figure it out
23:28* vagrantc never really liked / as delimiter
23:58telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)