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


Channel log from 21 February 2020   (all times are UTC)

01:00vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
05:42forbiddenera has joined IRC (forbiddenera!~forbidden@S0106000420fffff1.cg.shawcable.net)
05:44
<forbiddenera>
trying to do chrootless; get error: LTSP command failed: /usr/share/ltsp/client/login/pwmerge --ltsp --quiet /tmp/......
05:45
alkisg: thanks though, for your hard work putting this together
05:49
<alkisg>
forbiddenera: have you done any PAM changes?
05:57
<forbiddenera>
did apt update/upgrade. different error slightly now.. and I don't think I have; it's a pretty vanilla ubuntu install.
05:57
<alkisg>
forbiddenera: what's the error now?
05:58
<forbiddenera>
full text: https://pastebin.com/0QuZZk5w
05:59
<alkisg>
forbiddenera: all this is strange, do you mind if I have a look?
05:59
!vnc-dide
05:59
<ltspbot>
vnc-dide: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect srv1-dide.ioa.sch.gr - this is a reverse connection, it doesn't need port forwarding etc.
05:59
<forbiddenera>
this was the error I received before updating, https://pastebin.com/9XFQFUGm
06:00
<alkisg>
Yes, it sounds like you deleted your server /etc/passwd
06:00
<forbiddenera>
not sure I have any X installed
06:00
<alkisg>
Which would be rather strange
06:00
Do you have a separate partition for etc?
06:00
<forbiddenera>
yeah, not the case. it's there and populated.
06:00
nope
06:00
<alkisg>
What's your host OS, where you SSH from?
06:01
<forbiddenera>
curious why you ask/think that might matter?
06:01
<alkisg>
To share screen
06:01
<forbiddenera>
win10 in this case; not really by choice though
06:01
<alkisg>
I support 20 teachers per day
06:01
Screen sharing takes 10 times less time
06:02
Like, 30 minutes vs 3 minutes, really
06:02
<forbiddenera>
yep, understandable, appreciate that you're willing to do so
06:02
if you give me a sec I can give you ssh
06:02
<alkisg>
No need, you can reverse share console too
06:02
If you don't want that, no worries, we can do it the slow way
06:03
<forbiddenera>
eh apparently at least xterm is installed
06:03
<alkisg>
socat SYSTEM:"sleep 1; exec screen -xRR ra",pty,stderr tcp:81.186.20.0:5499 & screen -l -S ra
06:03
If you have screen and socat installed, you can share a console with me with that ^
06:03
<forbiddenera>
nice
06:03
<alkisg>
So that you can also see what I'm doing, and so that I don't need to ask for passwords etc
06:04
<forbiddenera>
:)
06:04
curious how you client from that;
06:04
<alkisg>
forbiddenera: I've programmed a script for that
06:04
Which command are you trying?
06:04
ltsp image / ?
06:05
<forbiddenera>
ltsp image x86_64
06:05
wanted to do chrootless
06:05
<alkisg>
There's the problem
06:05
Now that's chrootless
06:05
You don't need to create an empty dir
06:05
As then, it tries to find etc inside the empty dir
06:05
<forbiddenera>
tried without creating it but got a different error
06:06
sorry I meant I wanted chrooted not chrootless my bad
06:06
<alkisg>
Chrooted would need a chroot
06:06
Did you create one?
06:06
The new LTSP doesn't handle chroot or VM creation
06:07
You want a VM? Use vbox and create it by installing from an iso, etc
06:07
Want a chroot? Create it by using vagrant or docker or deboostrap or whatever you like
06:07
LTSP takes care the publishing step
06:09forbiddenera has left IRC (forbiddenera!~forbidden@S0106000420fffff1.cg.shawcable.net, Read error: Connection reset by peer)
06:12forbiddenera has joined IRC (forbiddenera!~forbidden@S0106000420fffff1.cg.shawcable.net)
06:12
<forbiddenera>
crashed
06:12
<alkisg>
AMD cpu? :D
06:12
<forbiddenera>
intel actually
06:12
amd gpu though lol
06:12
which is mining eth
06:12
<alkisg>
What crashed, ltsp?
06:12
Or everything?
06:12
<forbiddenera>
nah im sure it was unrelated
06:13
<alkisg>
OK, try it again, no vnc needed
06:13
forbiddenera: see irclogs.ltsp.org to see what I wrote to you above about chroots and images
06:13
<forbiddenera>
yeah didn't help I use BX on the same box
06:14
<alkisg>
What is bx?
06:14
<forbiddenera>
bitchx irc client
06:15
dunno if anyone still uses it..old school but works :)
06:15
<alkisg>
You mean that you already had the logs and you don't need the online logs?
06:16
Anyway, if you want chrooted, you need to create a chroot, without help from ltsp
06:16
<forbiddenera>
no since I use it on the same box and it crashed, I did need the logs :)
06:17
in your opinion what's the easiest way to create a chroot or vm image, don't really care which; I plan on having multiple clients boot from this, I don't really need each client to be completely separate, like I'm sure all clients could boot off the same image
06:17
<alkisg>
forbiddenera: in my opinion, chrootless is easiest, vm is easy, chroot isn't
06:17
<forbiddenera>
in fact I'm almost considering just using chrootless; the host is basically setup as I need for the clients
06:18
<alkisg>
Right. Go for that :)
06:18
<forbiddenera>
what caveats would there be for chrootless then? do I have to worry about any clients overwriting anything important?
06:18
<alkisg>
No
06:18
<forbiddenera>
also curious why the script keeps putting localhost as the NS in /etc/resolv.conf
06:18
<alkisg>
If you have e.g. lighttpd running on the server, you need to tell the clients not to run it as a service, via ltsp.conf
06:19
Which script? LTSP doesn't touch the server's resolv.conf
06:19
This is managed by systemd nowadays
06:19
<forbiddenera>
wierd, every time I ran it my resolv.conf dropped my lan nameserver
06:19
never had that happen on this system until playing with this
06:19
<alkisg>
Can I see again?
06:20
socat SYSTEM:"sleep 1; exec screen -xRR ra",pty,stderr tcp:81.186.20.0:5499 & screen -l -S ra
06:20
forbiddenera: you upgraded this from 16.04, which used resolvconf
06:21
<forbiddenera>
'tis possible apt did it as well
06:21
<alkisg>
18.04 doesn't use it, and you're supposed to manually remove it, and let systemd manage resolv.conf
06:21
<forbiddenera>
ah
06:21
thx
06:21
<alkisg>
Press enter if you agree
06:22
I'm not sure if you want to remove efibootmgr...
06:22
<forbiddenera>
eh thanks for catching that .. need to fix those packages sometime
06:22
not an EFI system so probably don't need it
06:22
<alkisg>
OK that's the correct, systemd resolv.conf there
06:23
This points to the systemd resolver, which then uses your resolvers
06:23
<forbiddenera>
awesome. didn't notice that when upgrading.
06:23
<alkisg>
(closed screen)
06:23
<forbiddenera>
this is just a dev-test-shitbox anyway
06:23
<alkisg>
It's best to do clean installs in general
06:23
Not upgrades
06:24
<forbiddenera>
i mean I have a gpu in it mining eth..definitely not what I'd call a 'good server'
06:24
yeah.. I generally prefer doing that if I can.
06:24
might end up wiping and redoing it later but again it's just kind of a test box
06:24
anything important here is on my xenserver
06:25
which I'm also considering ditching.. haven't decided though
06:25
my router vm is freebsd (pfsense) and acceleration is broken on eth drivers which, well, sucks
06:26
had to disable offloading which can result in like 50% cpu on a 8-core xeon when downloading torrents for example
06:26
anyway i'll probably just try chrootless for now; probably fine for my limited use case right now
06:27
essentially I want to netboot anything with a CPU I have and start it mining monero because I have power included in my rent and my landlord is a dink.
06:28* alkisg doesn't feel comfortable with the goal, but chrootless should be fine for that anyway
06:28
<forbiddenera>
curious why you prefer sudo -i vs sudo bash? .. I lose colored prompts when using -i and not with bash
06:28
<alkisg>
sudo bash leaves the user env, instead of creating a clean one
06:28
So, running e.g. gedit would give you root owned files under ~
06:28
<forbiddenera>
ah
06:28
<alkisg>
And a root-owned dconf database could then cause numerous issues
06:29
<forbiddenera>
pretty rare I meet/speak to anyone who knows unix/linux so well; again thanks for your time making ltsp happen
06:29
<alkisg>
np
06:30
<forbiddenera>
and you might be more comfortable if you knew my landlord was scamming me for $; thus I'm just returning the favor in a way. TBH I do feel a bit bad about the wasted electricity
06:30
I'm sure I'll find many other uses though
06:31
when I get more hw, I want to have it setup so I can deploy new vm hosts whenever; plug them into a VLAN, boot them up, they self-configure and add to pool
06:32
done netboot before for installing OS's quite a bit but never really for running a "thin"-ish client
06:52forbiddenera has left IRC (forbiddenera!~forbidden@S0106000420fffff1.cg.shawcable.net, Read error: Connection reset by peer)
07:29forbiddenera has joined IRC (forbiddenera!~forbidden@S0106000420fffff1.cg.shawcable.net)
07:30
<forbiddenera>
got Could not locate vmlinuz and initrd.img in /srv/ltsp/images/x86_64.img at the end of diskless
07:30
er chrootless
07:31
<alkisg>
forbiddenera: is /boot in a different partition?
07:32
<forbiddenera>
on /dev/sda1 .. / is /dev/mapper/oberon--vg-root
07:32
<alkisg>
!learn boot-partition as If you're using a separate partition for /boot, you need to define it in ltsp image, see: https://github.com/ltsp/ltsp/issues/43#issuecomment-541269010
07:32
<ltspbot>
The operation succeeded.
07:32
<forbiddenera>
thx
07:32
<alkisg>
np
07:36
<forbiddenera>
so i'm trying the work around but reading the commands, confused about the umount before running the ltsp script? doesn't that just remove what we just copied or I'm obviously missing something
07:37
<alkisg>
forbiddenera: oh. No, not the workaround, just the single command that I linked to
07:37
OK let me amend...
07:37
!forget boot-partition
07:37
<ltspbot>
The operation succeeded.
07:38
<alkisg>
!learn boot-partition as 'If you're using a separate partition for /boot, you need to define it like e.g. `ltsp image /,,/boot,subdir=boot`. See `man ltsp ipxe` for more on "advanced image sources".'
07:38
<ltspbot>
The operation succeeded.
07:38
<alkisg>
!boot-partition
07:38
<ltspbot>
boot-partition: 'If you're using a separate partition for /boot, you need to define it like e.g. ltsp image /,,/boot,subdir=boot . See man ltsp ipxe for more on "advanced image sources".'
07:38
<alkisg>
!learn boot-partition as `If you're using a separate partition for /boot, you need to define it like e.g. "ltsp image /,,/boot,subdir=boot". See "man ltsp ipxe" for more on "advanced image sources".`
07:38
<ltspbot>
The operation succeeded.
07:39
<alkisg>
!forget boot-partition 1
07:39
<ltspbot>
The operation succeeded.
07:39
<alkisg>
!boot-partition
07:39
<ltspbot>
boot-partition: If you're using a separate partition for /boot, you need to define it like e.g. "ltsp image /,,/boot,subdir=boot". See "man ltsp ipxe" for more on "advanced image sources".
07:39
<forbiddenera>
so I need to just run 'ltsp image /,,/boot,subdir=boot' instead
07:39
<alkisg>
Forget the "workaround" in the link I gave, I meant only that single command, not to continue reading the whole issue, as it was resolved later on
07:39
Right
07:40
<forbiddenera>
mksquashfs taking forever lmao
07:40
<alkisg>
Normally it needs 10 minutes
07:40
It depends on image size and CPU/disk speed
07:40
<forbiddenera>
eh maybe not too slow then
07:40
this is an old-ass server
07:40
PE2950iii3
07:40
s/3//;
07:41
xeon e5430s .. 5450s in my other one and this mac pro i'm on.. need newer hw :(
07:42
does the job though i guess; anything else of this age isn't too useful; over 10 years old now
07:43
but i started on a c64/128 and have a 8088 "laptop" (marrow pivot) sitting here I just got working again for fun so it's all relative really
07:44
i wish my stuff was all at least one gen newer.. ddr3 instead of power hungry fbdimm.. stuff like avx and ht and iommu
07:48
this particular system I think just has a laptop drive in it right now lol.. all the 15k SAS drives are elsewhere in raids..so that's probably not helping the speed..i'd say 15min.. what all does it put in this image? not everything..?
07:51
<alkisg>
Pretty much everything except /home and passwords
07:53
<forbiddenera>
goodenuf
07:57
now that im done all the install stuff, should be good to netboot something eh?
07:57
<alkisg>
!install
07:57
<ltspbot>
install: To install LTSP: https://ltsp.org/docs/installation/
07:58
<alkisg>
This has all the necessary steps
07:58
<forbiddenera>
thats what i mean, done all that
07:58
<alkisg>
Then sure
07:58
<forbiddenera>
lets give it a shot then :D
08:02
i wonder if the system im testing on blinks the hd access light on network boot access?
08:03
its blinking like nuts like it would if i was booting off hd lol
08:04
its booting though; many services failing
08:05
mysql, /etc/rc.local compat, tftp, ldm .. none i care about so far i think
08:07
<alkisg>
Mysql will fail as its password wasn't included; so you may just disable it from ltsp.conf to avoid the message
08:07
<forbiddenera>
how much ram, if any, is used for ramfs stuff or is everything 100% over net?
08:07
<alkisg>
rc.local compat probably means a bad command there
08:08
<forbiddenera>
yeah, it's not finding my gpu management script
08:08
<alkisg>
tftp... tftpd-hpa? you may uninstall that
08:08
ldm? uninstall the old ltsp
08:08
Scripts in /home are only available after login
08:08
<forbiddenera>
yeah i probably started trying to do this like just before you announced your rerwite
08:08
https://github.com/Shaped/amdpwrman
08:08
<alkisg>
You can put things in /usr/local and run `ltsp image` (slow), or in /etc/ltsp and run `ltsp initrd` (fast)
08:09
<forbiddenera>
yeah not needed really here and as I was still working on the script I never moved it out of /home
08:10
after started update utmp .. seems to be maybe stuck .. or taking it's sweet time .. disk access light is still blinking occasionally
08:11
<alkisg>
What are you using for networking?
08:11
<forbiddenera>
I still think it's neat this efi does thaI guess..the way it blinks is more reminiscient of a LAN blink vs an hd blink
08:11
<alkisg>
E.g. do you have dhcp in /etc/network/interfaces? Are you using netplan? Network manager?
08:12
<forbiddenera>
tbh I don't know haha
08:12
<alkisg>
LTSP removes the most common stuff, but if you have something weird that tells the client to do dhcp at that point, it will break netroot
08:12
<forbiddenera>
whatever it defaulted to after installing 16 and upgrading to 18 i guess
08:13
<alkisg>
It depends on whether it was a server .iso installation or a desktop one etc etc
08:13
<forbiddenera>
probably server but i don't remember
08:13
most likely server knowing me
08:14
/etc/netplan is empty
08:14
<alkisg>
Does the client ip answer to pings?
08:14
<forbiddenera>
/etc/network/interfaces is populated
08:15
yes
08:15
<alkisg>
It's not that then
08:15
<forbiddenera>
let me check and see if it's budged
08:15
<alkisg>
Is it supposed to show a gui, or just text login?
08:15
Also try ctrl+alt+f2 etc
08:15
<forbiddenera>
should just be text
08:16
yeah i was gonna try that
08:16
no ssh atm
08:16
<alkisg>
epoptes ftw :)
08:17
<forbiddenera>
never used that
08:17
looks cool though
08:18
and of course you're the dev
08:18
<alkisg>
;)
08:19
<forbiddenera>
unforunately I don't really have X setup anywhere
08:19
I suppose I could vnc into this box or run an x client on my win box
08:19
<alkisg>
Yeah you're not the typical ltsp user
08:19
x2go from windows would work, sure
08:19
Or vnc, rdp..
08:23forbiddenera has left IRC (forbiddenera!~forbidden@S0106000420fffff1.cg.shawcable.net, Ping timeout: 240 seconds)
08:26forbiddenera has joined IRC (forbiddenera!~forbidden@S0106000420fffff1.cg.shawcable.net)
08:26
<forbiddenera>
in theory i could migrate vms from bare to virt and back ..that was odd..i guess FN wants me to STFU
08:28
sshd is nonexistent it seems on a client ? service start sshd returns unit not found
08:30
<alkisg>
Yeah it's a security issue so it's disabled by default
08:30
man ltsp.conf => read about KEEP_SYSTEM_SERVICES
08:30
<forbiddenera>
thx
08:31
where's ltsp.conf? I have to redo the image after changing it?
08:32
<alkisg>
!ltsp.conf
08:32
<ltspbot>
ltsp.conf: Configuration file for LTSP: https://ltsp.org/man/ltsp.conf/
08:32
<alkisg>
Read that
08:32
<forbiddenera>
ah. should've read the first bit instead of just skipping down
08:33
assumed one might've existed already
08:33
<alkisg>
No, in my view all /etc should be empty by default, and only local changes should be put there
08:37
<forbiddenera>
actually booted right to the login prompt this time
08:43
sshd is running but i can't even connect localhost
08:45
when it wasnt running it was connection closed now its connection reset ; sshd config is default
08:48
regen host keys?
08:49
yep that wasit
08:50
perfect. i think i'm where i need to be for now. thanks for your help again and work on the project. it's great when people make things easier with linux. keep up the good work
08:53
if the server bails but comes back, will it just cause a delay or worse issues? just out of curiosity..i'd think it would just timeout while down on any reads/writes right?
08:56
just doubled the efficiency of this system due to it being on linux instead of windows doing the same thing. sweet.
09:02statler_ has joined IRC (statler_!~Georg@gwrz3.lohn24.de)
09:05
<alkisg>
NFS continues properly even after big delays; SSH and SSHFS after small delays; NBD doesn't (only the old LTSP used NBD)
09:55GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Read error: Connection reset by peer)
09:56GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net)
10:05
<forbiddenera>
killuserprocesses was set to yes on booted nodes but not the host :(
10:16
any way around regen ssh keys every boot?
10:33
.. read the issue regarding killuserprocesses; running systemd-run --user --scope screen results in an errror
10:44
https://github.com/systemd/systemd/issues/3388
10:45
<alkisg>
forbiddenera: I think you need to describe the goal, not the error
10:46
"i want to do this xxx thing and I'm trying that yyy thing"
10:46
<forbiddenera>
well i want to keep a screen session running after logout
10:46
<alkisg>
Why?
10:46
Are you sure you don't want a service instead?
10:46
<forbiddenera>
not really; easier to just launch the miner, detach and go on
10:46
it's something that has interactivity thus screen
10:47
<alkisg>
Sounds like a service to me
10:47
Not a user process
10:47
<forbiddenera>
even if i want to reattach to it
10:48
<alkisg>
Sure, if I understand you correctly, that process doesn't relate to sessions
10:48
<forbiddenera>
running screen as a service seems a little silly
10:48
<alkisg>
Nah, leaving things running after logout sounds sillier, I agree with logind on that
10:49
<forbiddenera>
which is fair; but i should be able to use systemd-run --user --scope to take the scope out of the session
10:49
literally what the manpage says to do
10:49
<alkisg>
That part would be a question for the #systemd channel
10:50
<forbiddenera>
is there a way to prevent ltsp from enforcing killuserprocesses?
10:50
<alkisg>
Regarding the ssh keys, they're excluded from image.excludes, man ltsp.conf and search about exclude
10:50
You can put a POST_INIT command to set killuserprocesses to whatever you like; but note that then sshfs won't be unmounted etc
10:51
As you're then missing the "session ended" point
10:53
<forbiddenera>
is ltsp using sshfs? thought the default was nfs or something .. im otherwise not mounting anything within a user session
10:53
<alkisg>
nfs for /, and sshfs for /home
10:54
You can easily set nfs for /home too, if you prefer that (which in this case you should)
10:54
<forbiddenera>
is anything in /home mounted whenever a user logs in then? if its just mounted on boot/shutdown then not sure how it would affect..not properly unmount on shutdown?
10:54
<alkisg>
(i mean the "not allowing the session to end" use case)
10:55
/home/username is mounted via sshfs on user login
10:55
And unmounted on user logout
10:55
<forbiddenera>
ah
10:55
<alkisg>
As sshfs is secure, while nfs (or sshd on the clients) isn't
10:55
So it makes a good default
10:55
<forbiddenera>
understandable
10:56
<alkisg>
bbl
10:56
<forbiddenera>
would be nice if the listed workaround for systemd worked though; i'm hitting a bug that's listed as solved/closed even though my systemd should be new enough
10:56
np thx for the help &Time
11:10forbiddenera has left IRC (forbiddenera!~forbidden@S0106000420fffff1.cg.shawcable.net, Remote host closed the connection)
11:16forbiddenera has joined IRC (forbiddenera!~forbidden@S0106000420fffff1.cg.shawcable.net)
11:26forbiddenera has left IRC (forbiddenera!~forbidden@S0106000420fffff1.cg.shawcable.net, Read error: Connection reset by peer)
11:41Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
12:04forbiddenera has joined IRC (forbiddenera!~forbidden@S0106000420fffff1.cg.shawcable.net)
12:08
<forbiddenera>
so the issue in systemd i guess maybe not fixed til 238; my system uses 237 fully updated; had to enable legacy cgroups to be able to create a user service; now just have to pass the kernel option on to the boot clients. i set KERNEL_PARAMETERS="systemd.legacy_systemd_cgroup_controller=1" in [clients] but it doesn't work/show up in /proc/cmdline on clients
12:09
i did run ltsp initrd after
12:10
i see 95 ; guess it did confuse a user :p
12:14
oops ltsp ipxe is what i probably needed
12:19
well that finally works..now my 2nd system isn't letting me login and is getting connection reset by peer :/
12:23
eh my laptop wasnt shifting for some reason..had to capslock every capital in my pw..the connection errors gone now too..so finally good..took way too long to fix the systemd thing haha..anyway chhers&thxagain
12:23forbiddenera has left IRC (forbiddenera!~forbidden@S0106000420fffff1.cg.shawcable.net, Quit: BitchX: fit to feel groovy)
12:47section1 has joined IRC (section1!~section1@vps-1722311-x.dattaweb.com)
13:30mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy)
15:19mnevans has joined IRC (mnevans!8008b09d@zero.geol.umd.edu)
15:22
<mnevans>
chrootless mode: I am wondering how to get ltsp clients to pick up non /home partitions that are in the /etc/fstab on the server, but then don't appear in the client. I added a line in /etc/ltsp/ltsp-local.conf, FSTAB_HOME=... (but I don't want /home to be replaced, just add another partition to be mounted), recreated the image, ltsp ipxe, ltsp
15:22
initrd. No joy.
15:29
chrootless mode: I have a client that doesn't recognize the native 1920 x 1080 display, but instead gives 1024x768. All of them default seem to create an extended display which doesn't exist, making login and customization for a new user difficult. I have to open a terminal window and use xrandr --output DisplayPort off to eliminate the ghost
15:29
extended display.
15:29
This mnevans: what a whiner! :)
15:30
But would appreciate suggestions for how to change the behavior for all clients to not find a nonexistent extended display.
15:31
Using X.org and XFCE. Which was great previously on this hardware and under ltsp5.
15:47
<alkisg>
mnevans: you want the other partitions to go to the x86_64.img image, or to be available via nfs?
15:50
I.e. do they have static content or dynamic?
15:54
<mnevans>
Alkis, thanks. I am not sure I understand your questions (sorry!) I want files in the other partition to be accessible to client users. I would also like to be able to write files there occasionally from a client connection. Just as if I were logged into the console, or into the server via an ssh connection, I would see that partition.
15:54
<alkisg>
mnevans: for example, /usr goes to the image, while /home is available over sshfs
15:54
This is because usr is static, while home has dynamic content
15:54
I'm guessing you mean "dynamic content", in which case you may use NFS
15:55
With NFS, you export directories from the server's /etc/exports.d, and you use FSTAB_x to create client fstab lines to mount them
15:55
<mnevans>
so I would add the line FSTAB_x to /etc/ltsp/ltsp-local.conf? With same form as in the example in the template?
15:56
<alkisg>
There's no /etc/ltsp/ltsp-local.conf; use /etc/ltsp/ltsp.conf
15:56
Yes, same form as the example for /home
15:56
<mnevans>
facepalm...
15:57
<alkisg>
Re: display, to disable ghost displays you can pass video=eDP-1:d in KERNEL_PARAMETERS
15:57
Want me to check via vnc?
15:57
!vnc-edide
15:57
<ltspbot>
vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
15:58
<mnevans>
I would, except I have to run a meeting now. But I think this helps me get started once I finish that meeting. But I thought I put local modifications into something other than ltsp.conf, b/c ltsp.conf gets overwritten by one of the ltsp applets?
15:59
<alkisg>
No, nothing touches ltsp.conf
15:59
All the other files like /etc/dnsmasq.d/ltsp-dnsmasq.conf DO get overwritten though
15:59
As they're autogenerated; while ltsp.conf, isn't autogenerated, it's manually edited
16:00
<mnevans>
OK! Thanks!
16:00
<alkisg>
np :)
16:01
<mnevans>
If I change ltsp.conf and ltsp-nsf.exports in /etc/exports.d/, do I need to recreate the ltsp image?
16:01
<alkisg>
Whenever you change ltsp.conf, you need to run `ltsp initrd`, which takes 1 sec
16:02
Server changes like /etc/exports.d, need things like `exportfs -ra`, to re-read the nfs exports, but they're not related to ltsp, they don't need you to run any ltsp commands
16:02
<mnevans>
Got it! Thanks!
16:03
But have to reboot the client(s)?
16:03
<alkisg>
Yes, the clients read ltsp.conf when they boot, so they need to be rebooted when you change it
17:49mnevans2 has joined IRC (mnevans2!8008b09d@zero.geol.umd.edu)
17:55
<mnevans>
Fixed! thank you. I am sorry - where would I put KERNEL_PARAMETERS? In ltsp.conf? under a new section called [kernel_parameters]?
17:56
Here is an even more basic question. My clients come up with local hardware resources rather than the server's. But the server's disks. How do I ensure I get the server's CPU and memory?
18:11uumas has left IRC (uumas!uumaskapsi@gateway/shell/matrix.org/x-fkamlfdkuhmzskdp, Ping timeout: 245 seconds)
18:12alexxtasi[m] has left IRC (alexxtasi[m]!alexxtasim@gateway/shell/matrix.org/x-ibvvfdhswtrnbnia, Ping timeout: 246 seconds)
18:12lysuumas has left IRC (lysuumas!uumaslyseo@gateway/shell/matrix.org/x-mmjunrrwkzogtjxp, Ping timeout: 256 seconds)
18:15
<alkisg>
mnevans, read ltsp.conf man page:
18:15
!ltsp.conf
18:15
<ltspbot>
ltsp.conf: Configuration file for LTSP: https://ltsp.org/man/ltsp.conf/
18:15
<alkisg>
Search for KERNEL_PARAMETERS there, including the example
18:15
The new ltsp doesn't support thin clients
18:15
If you want thin clients, you'd need to use rdp/x2go/vnc etc
18:17Sleaker_ has joined IRC (Sleaker_!quasselcor@172.110.7.65)
18:18Sleaker has left IRC (Sleaker!quasselcor@172.110.7.65, Ping timeout: 240 seconds)
18:24section1 has left IRC (section1!~section1@vps-1722311-x.dattaweb.com, Quit: Leaving)
18:27alexxtasi[m] has joined IRC (alexxtasi[m]!alexxtasim@gateway/shell/matrix.org/x-yskfewxbjguptjpv)
18:28Sleaker_ is now known as Sleaker
18:30alexxtasi[m] has left IRC (alexxtasi[m]!alexxtasim@gateway/shell/matrix.org/x-yskfewxbjguptjpv, Client Quit)
18:31
<mnevans>
Oh wow - that's a big change in my world. I thought the whole point of ltsp was thin client-server architecture.
18:31
I do have x2goserver/client already set up for remote access.
18:32
I think it can be set up for thin clients... https://wiki.x2go.org/doku.php/wiki:advanced:tce:install
18:32
Now I am off topic...
18:36statler_ has left IRC (statler_!~Georg@gwrz3.lohn24.de, Remote host closed the connection)
18:39
<alkisg>
ltsp was about thin clients, but then thin clients got deprecated by all the world, hardware and software
18:39
so now ltsp is about netbooting fat clients mostly
18:48
<mnevans>
Ah. I am left behind... I liked the low maintenance, low energy, low cost, scalable aspects of the thin clients.
18:50
<alkisg>
then modern browsing came :)
18:54
<mnevans>
Once more I am confused. I should change my screen name... What does browsing have to do with it?
18:58
<alkisg>
a youtube video needs 5 gbps on thin clients
18:58
and just 1 mbps on fat clients
18:59
can't have local net with 50 gbps for 10 clients...
19:03alexxtasi[m] has joined IRC (alexxtasi[m]!alexxtasim@gateway/shell/matrix.org/x-zgbytxhzfgwmmogu)
19:06
<alkisg>
Also, graphics card and operating systems now use compositing, not things like "arcs" and "circles"
19:06
Remote xorg isn't really suitable anymore
19:07
and directx, opengl, shaders... lots of fancy stuff for desktop environments
19:34uumas has joined IRC (uumas!uumaskapsi@gateway/shell/matrix.org/x-wzbzqrpjmeuuffzz)
19:34lysuumas has joined IRC (lysuumas!uumaslyseo@gateway/shell/matrix.org/x-wsrenratnlfskfwd)
21:28
<mnevans>
Alkis - I see. Although I don't understand why a fat client would use so much less bandwidth for something streaming from the internet.
21:29
My problem is that I want to do scientific computing on the server. I guess perhaps the solution is simply to ssh or x2goclient into the server for that.
22:42Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)