ltsp-discuss Mailing List for Linux Terminal Server Project (LTSP)

Copied from https://github.com/ltsp/ltsp/issues/1#issuecomment-1397954759
Happy new year to all!
And as always, special thanks to Vagrant for uploading to Debian.

## Announcing LTSP 23.01

A new version LTSP 23.01 is available in the [proposed 
PPA](https://ltsp.org/advanced/proposed-ppa/). Please test and verify 
that it doesn't cause any issues for you, as it will be uploaded in the 
[stable PPA](https://ltsp.org/docs/ppa/) and in [Debian 
testing](https://packages.debian.org/testing/ltsp) in a few days.

Changelog from the previous version:

   * Search for new memtest86+ binaries (#783)
   * Don't chmod -x epoptes anymore
   * Avoid systemd lingering (#778)
   * Avoid broken pipe warning (#767)
   * Better sssd autodetection (#749)
   * Support arctica-greeter (#742)
   * Search for DISABLE_SYSTEM_SERVICES in /lib too (#690)


Also, copied from 
https://github.com/epoptes/epoptes/issues/1#issuecomment-1397956393

## Announcing Epoptes 23.01

A new Epoptes 23.01 version is available in the [proposed 
PPA](https://epoptes.org/documentation/ppa/). Please test and verify 
that it doesn't cause any issues for you, as it will be uploaded in the 
[stable PPA](https://epoptes.org/documentation/ppa/) and in [Debian 
testing](https://packages.debian.org/testing/epoptes) in a few days.

Changelog from the previous version:

   * Avoid thumbshot.py crashes on wayland (#184)
   * Bump benchmark timeout from 3 to 5 sec
   * Remove constraints unnecessary since buster (#152)
   * Import translations from launchpad
   * Use iperf --full-duplex for benchmark (#183)
   * Update chat room URL (#168)
   * Run epoptes over SSH socket forwarding (#182)
   * Make "Execute command" translatable (#181)
   * Optimize wait_for_dns (#179)
   * Support a main epoptes server
   * Silence x11vnc
   * Use the main mac address (#178)
   * Avoid xwininfo hangs (#177)
   * If SERVER is an MDNS name, retry indefinitely (#162)
   * Work around broken output in recent iperf versions (#164)
   * Allow controlling specific groups (#159)
   * Use relative Exec=epoptes path (#158)

I did it with NIS on the lan. Not sure about it's security level though.
LDAP may be better suited.

https://www.google.com/url?sa=t&source=web&rct=j&url=https://www.server-world.info/en/note%3Fos%3DUbuntu_20.04%26p%3Dnis%26f%3D1&ved=2ahUKEwiogZrzlK72AhV0KH0KHbuFBVsQFnoECAsQAQ&usg=AOvVaw0SGHmoCypJB2ut9PturQaY

https://www.google.com/url?sa=t&source=web&rct=j&url=https://www.server-world.info/en/note%3Fos%3DUbuntu_20.04%26p%3Dnis%26f%3D2&ved=2ahUKEwiogZrzlK72AhV0KH0KHbuFBVsQFnoECAkQAQ&usg=AOvVaw00d8njpC33BwLvG-vJ0ApM

On Fri, Mar 4, 2022, 6:39 PM Joseph Bishay <jos...@gm...> wrote:

> Hello,
>
> Our Ubuntu LTSP server and thin clients are the main focus of our network,
> but we have some other Ubuntu servers providing additional services
> (backup, VOIP, etc.).  The network admin have to create accounts on each
> machine and remember the different passwords for each of these additional
> servers.  Is there a way to have LTSP act as the main authenticator for
> these other servers, similar to how it is authenticating when you log into
> a thin client?  This way we centralize the username and passwords and make
> it easy to add / remove users?
>
> Thank you.
> Joseph
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
>

Hello,

Our Ubuntu LTSP server and thin clients are the main focus of our network,
but we have some other Ubuntu servers providing additional services
(backup, VOIP, etc.).  The network admin have to create accounts on each
machine and remember the different passwords for each of these additional
servers.  Is there a way to have LTSP act as the main authenticator for
these other servers, similar to how it is authenticating when you log into
a thin client?  This way we centralize the username and passwords and make
it easy to add / remove users?

Thank you.
Joseph

Copied from https://github.com/ltsp/ltsp/issues/1#issuecomment-1019081703

As always, special thanks to Vagrant for uploading to Debian.

## Announcing LTSP 22.01

A new version LTSP 22.01 is available in the [proposed 
PPA](https://ltsp.org/advanced/proposed-ppa/). Please test and verify 
that it doesn't cause any issues for you, as it will be uploaded in the 
[stable PPA](https://ltsp.org/docs/ppa/) and in [Debian 
testing](https://packages.debian.org/testing/ltsp) in a few days.

Changelog from the previous version:

   * Use cp -u to inject ltsp (#636)
   * Prefer go-md2man or pandoc over ronn for man pages (#635, #640)
   * Use more compatible markdown (#634)
   * Introduce DISABLE_SYSTEM_SERVICES (#495)
   * debian/watch: Use tags to scan for new upstream versions
   * Suggest single partitions for VMs (#618)
   * Implement ltsp remoteapps (#597)
   * Avoid creating /srv/ltsp/raspios/boot/overlays/overlays (#594)
   * Check if iPXE has the features we need (#579)
   * Add e4:5f:01 rpi OUI in dnsmasq and ltsp.conf (#498)
   * Implement multiseat autodetection (#133)
   * Use correct root hash in ltsp.conf.5.md (#547)
   * Correctly replace BASE_DIR in ltsp.ipxe (#416)
   * Don't hardcode LTSP paths in 25-ro-root.sh (#485)
   * Use the system hostname (#568)
   * Use DNS=1 on ltsp clients (#373)
   * Introduce undocumented ltsp session
   * Add PATH and username for CRONTAB_x (#454)
   * Check if sssd.conf exists (#450)

Am 26.03.21 um 14:45 schrieb Joseph Bishay:
> Hello Rolf,
> 
> Thank you for your response.
> 
> On Fri, Mar 26, 2021 at 4:53 AM Rolf-Werner Eilert <rw...@os... 
> <mailto:rw...@os...>> wrote:
> 
>     On our server, I have scripts that can read a list of usernames to make
>     or remove multiple accounts.
> 
> 
> Do you mind sharing the script (or at least the relevant parts)?
> 
>     And we are running LTSP5 under Ubuntu Mate 18 (yet), but I plan to
>     update to a new server soon. However, I guess the same will be
>     necessary
>     there.
> 
> 
> We are also running Ubuntu Mate 18 and it's been working very well so 
> we're not planning on updating yet.
> 
> Thank you so much,
> Joseph
> 

Sorry Joseph for being so late - just stumbled over this one on the 
search of another thread. Of course, I can let you have my script.

It is written in Gambas, a powerful Basic interpreter which is able to 
run everything from script to webapp to IDE-based full-blown 
applications. As it is Basic, it should be easily readable.

The relevant parts are written as shell commands, i. e. bash. That makes 
it even easier to understand, I hope.

I found, however, that I made scripts for making new user homes and 
copying old ones from a previous server. Obviously, there has not been a 
need to make a script for cleanup like in your case. But it should be 
easily creatable.

Sorry, all commentary in my scripts is in German...

Here we go, this is "make new accounts from a list of Name:username pairs":

#!/usr/bin/env gbs3

'Nov. 2018 auf Ubuntu Mate

'legt alle oder einen Teil der Accounts an, die in der Liste 
"account.liste" stehen

'NEU: Ohne account.liste wird nix gemacht!


'- Wenn es den Accountnamen schon gibt, wird er übersprungen.
'- Die Office-Icons können bei Mate einfach so aus der /etc/skel in die 
User-Accounts kopiert werden.

dim i, j, po as integer
dim username, userid, userbez, userpw, icondatei, t$ as string
dim ls as new string[]	'Filterliste (account.liste)
dim teil as new string[]
dim pwdaten as new string[]


print "Start:"

if not exist(Application.Dir &/ "account.liste") then
     print "account.liste nicht gefunden, Abbruch"
     quit
end if


if exist(Application.Dir &/ "account.liste") then
     ls = split(file.load(Application.Dir &/ "account.liste"), chr$(10))
     for i = 0 to ls.Max
	if trim$(ls[i]) <> "" then
	    print ls[i] & ":"
	    teil = split(ls[i], ",")
	    if teil.Count < 2 then
		print "Fehler: immer username, Langname angeben! - Abbruch"
		quit
	    end if
	    username = trim$(teil[0])	'=$HOME
	    userbez = trim$(teil[1])	'=Langname

	    if exist("/home/" & username) then
		print username & " existiert schon, überspringen..."
	    else
							'neuen Benutzer anlegen:
			shell "useradd -c \"" & userbez & "\" -G schueler -m -s /bin/bash " & 
username WAIT

							'für die Passwörter:
			pwdaten.add(username & ":hallo")

							'Benutzerverz. etwas privater machen:
			shell "chmod 750 /home/" & username WAIT '(bei Ubuntu geht 750, weil 
Hauptgruppe = User)

							'Aufgabenverz. einrichten:
			shell "mkdir /home/usrsharemisc/" & username WAIT
			shell "chown " & username & ":schueler " & "/home/usrsharemisc/" & 
username WAIT
			shell "chmod 750 " & "/home/usrsharemisc/" & username WAIT
			'*** Vorsicht: jetzt vom richtigen Pfad aus: ***
			shell "ln -s /usr/local/share/all/ttasks/" & username & " /home/" & 
username & "/Dokumente/Aufgaben" WAIT

			print "- eingerichtet."
			print " "
	    end if
	end if
     next

     print "- Passwörter schreiben..."
     if pwdaten.Count > 0 then
	File.Save(Application.Dir &/ "passwortAendern.liste", 
pwdaten.Join(chr$(10)))
	shell "cat " & Application.Dir &/ "passwortAendern.liste | chpasswd" WAIT
	Kill Application.Dir &/ "passwortAendern.liste"
     end if


end if

print "---------"
print "...fertig."

Am 26.03.21 um 14:45 schrieb Joseph Bishay:
> Hello Rolf,
> 
> Thank you for your response.
> 
> On Fri, Mar 26, 2021 at 4:53 AM Rolf-Werner Eilert <rw...@os... 
> <mailto:rw...@os...>> wrote:
> 
>     On our server, I have scripts that can read a list of usernames to make
>     or remove multiple accounts.
> 
> 
> Do you mind sharing the script (or at least the relevant parts)?
> 
>     And we are running LTSP5 under Ubuntu Mate 18 (yet), but I plan to
>     update to a new server soon. However, I guess the same will be
>     necessary
>     there.
> 
> 
> We are also running Ubuntu Mate 18 and it's been working very well so 
> we're not planning on updating yet.
> 
> Thank you so much,
> Joseph
> 


And this one is for copying existing accounts from a previous server:

#!/usr/bin/env gbs3

'Nov. 2018 für Umstieg auf Ubuntu Mate

'legt alle oder einen Teil der Accounts an; wenn es eine Liste 
"account.liste" gibt,
'werden nur Accounts angelegt, die dort drinstehen (die Liste muss nur 
die Accountnamen enthalten).

'NEU: Ohne account.liste wird nix gemacht!

'NEU: *** Wenn /mnt/<altes /home> gemountet ist, kann das alte $HOME 
gleich mit kopiert werden

'- Es wird nach Kopien vorgegangen: /etc/passwd.orig und 
/etc/shadow.orig vom alten Server. Diese müssen existieren!
'- Wenn es den Accountnamen schon gibt, wird er übersprungen.
'- Aus der /etc/shadow.orig werden die Passwörter in die /etc/shadow 
übernommen.
'- Die Office-Icons können bei Mate einfach so aus der /etc/skel in die 
User-Accounts kopiert werden.

dim i, j, po as integer
dim username, userid, userbez, userpw, icondatei, t$ as string
dim pw as new string[]	'Userliste Original (/etc/passwd.orig)
dim sh as new string[]	'Passwörter Original (/etc/shadow.orig)
dim sn as new string[]	'Passwörter neu (/etc/shadow)
dim ls as new string[]	'Filterliste (account.liste)
dim teil as new string[]


print "Start:"

if not exist("/etc/passwd.orig") then
     print "/etc/passwd.orig nicht gefunden, Abbruch"
     quit
end if

if not exist("/etc/shadow.orig") then
     print "/etc/shadow.orig nicht gefunden, Abbruch"
     quit
end if

if not exist(Application.Dir &/ "account.liste") then
     print "account.liste nicht gefunden, Abbruch"
     quit
end if


if exist(Application.Dir &/ "account.liste") then
     print "Listen vorhanden, /etc/passwd.orig wird gefiltert:"
     ls = split(file.load(Application.Dir &/ "account.liste"), chr$(10))
     pw = split(file.load("/etc/passwd.orig"), chr$(10))
     sh = split(file.load("/etc/shadow.orig"), chr$(10))
     for i = 0 to pw.count - 1
	if trim$(pw[i]) <> "" then
	    teil = split(pw[i], ":")
	    username = teil[0]	'=$HOME
	    userid = teil[2]	'=ID-Nr.
	    userbez = teil[4]	'=Langname
	    if cint(userid) > 999 AND username <> "nobody" then
		po = ls.find(username)
		if po > -1 then
		    print username & " (" & userid & ") " & userbez
		    if exist("/home" &/ username) then
			print "- gibt es schon, überspringen..."
			print " "
		    else
			for j = 0 to sh.count - 1	'altes Passwort raussuchen:
			    teil = split(sh[j], ":")
			    if teil[0] = username then
				userpw = teil[1]
				break
			    end if
			next

							'neuen Benutzer anlegen:
			shell "useradd -c \"" & userbez & "\" -G schueler -m -s /bin/bash -u 
" & userid & " " & username WAIT

							'altes Passwort einsetzen:
			sn = split(file.load("/etc/shadow"), chr$(10))
			for j = 0 to sn.count - 1
			    teil = split(sn[j], ":")
			    if teil[0] = username then
				teil[1] = userpw
				sn[j] = teil.join(":")
				file.save("/etc/shadow", sn.join(chr$(10)))
				break
			    end if
			next

							'Benutzerverz. etwas privater machen:
			shell "chmod 750 /home/" & username WAIT '(bei Ubuntu geht 750, weil 
Hauptgruppe = User)

							'Aufgabenverz. einrichten:
			shell "mkdir /home/usrsharemisc/" & username WAIT
			shell "chown " & username & ":schueler " & "/home/usrsharemisc/" & 
username WAIT
			shell "chmod 750 " & "/home/usrsharemisc/" & username WAIT
			'*** Vorsicht: jetzt vom richtigen Pfad aus: ***
			shell "ln -s /usr/local/share/all/ttasks/" & username & " /home/" & 
username & "/Dokumente/Aufgaben" WAIT

							'Kopie des alten $HOMEs machen
			if exist("/mnt/" & username) then
			    print "  - altes $HOME kopieren..."
			    shell "mkdir /usr/local/share/all/alteHomes/" & username WAIT
			    shell "cp -a /mnt/" & username & "/* 
/usr/local/share/all/alteHomes/" & username WAIT

							'wg. Umstellung von Suse auf Ubuntu jetzt "USER:USER":
			    shell "chown -R " & username & ":" & username & " 
/usr/local/share/all/alteHomes/" & username WAIT

							'Link von $HOME auf Kopie des alten $HOMEs
			    shell "ln -s /usr/local/share/all/alteHomes/" & username & " 
/home/" & username & "/altesHome" WAIT
			end if

			print "- eingerichtet."
			print " "
		    end if
		end if
	    end if
	end if
     next

end if

print "---------"
print "...fertig."

Copied from https://github.com/ltsp/ltsp/discussions/469


I haven't had enough free time to properly read all the news about 
freenode and libera.
But for the last couple of months I've been testing matrix.org and I 
didn't have any complaints.

So I've started a new ltsp room on matrix:

- You can join it from a web browser: 
https://app.element.io/#/room/#ltsp:matrix.org
- It also offers native applications for e.g. mobile phones
- I installed an IRC bridge, so all text is automatically mirrored 
between the martix room and the freenode #ltsp channel
- Although, the matrix room also supports files, pictures, voice chat, 
video chat and a lot more

For now it's just a proposal; it's up to the community to embrace it or 
not. Later on we may move the IRC bridge from freenode to libera or oftc.
If anyone has a better idea, I'm open to suggestions! I wouldn't want 
closed-source solutions or self-hosting solutions though.

In case noone helps with ldminfod and you're unable to resolve the issue,
and IF you're using fat clients instead of thin clients,
note that you should be able to create a new chroot/image in the 
existing LTSP server (or move the existing one to /srv/ltsp), delete all 
the old LTSP and LDM packages, and follow the new LTSP installation 
instructions:

https://ltsp.org/docs/installation/

The new LTSP isn't using LDM at all anymore, has moved from 
isc-dhcp-server and tftpd-hpa to dnsmasq, so the troubleshooting 
procedures are completely different now... (and it's much easier to 
setup and troubleshoot it).

Cheers,
Alkis

On 5/4/21 6:29 PM, mi...@se... wrote:
Hi,
I'm migrating ltsp server from older debian to debian10, but I can't
make it work.

I installed all required packages, copied chroots - /opt/ltsp, tftp -
/var/lib/tftpboot, /srv/tftp via rsync to their right directories on the
new server. (I also tried ltsp-update-kernels, ltsp-update-sshkeys to
make sure the copy is working). On dhcp server I simply change
next-server parameter to test it. I'm sure it passes ip address and
other parameters to the client correctly.

All seems to be working until client connects to server's X session (or
tries to connect?)
All I found is this syslog - ldminfod gives me this message repeatedly.
No ldm log found, no message on client screen, no xsession errors.
Unfortunately I don't know where to look for error logs or help anymore.
I've also read many threads but they didn't really help much.

May  4 14:39:39 debian10 in.tftpd[3332035]: tftp: client does not accept
options
May  4 14:39:49 debian10 rpc.mountd[87913]: authenticated mount request
from 192.168.1.230:924 for /opt/ltsp/amd64 (/opt/ltsp)
May  4 14:40:00 debian10 ldminfod[3332173]: connect from 192.168.1.230
(192.168.1.230)
May  4 14:40:19 debian10 ldminfod[3332295]: connect from 192.168.1.230
(192.168.1.230)
...

Thanks in advance.


_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
        https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Hi,

I'm migrating ltsp server from older debian to debian10, but I can't make it
work.





I installed all required packages, copied chroots - /opt/ltsp, tftp - /var/
lib/tftpboot, /srv/tftp via rsync to their right directories on the new 
server. (I also tried ltsp-update-kernels, ltsp-update-sshkeys to make sure 
the copy is working). On dhcp server I simply change next-server parameter 
to test it. I'm sure it passes ip address and other parameters to the client
correctly.





All seems to be working until client connects to server's X session (or 
tries to connect?)


All I found is this syslog - ldminfod gives me this message repeatedly. No 
ldm log found, no message on client screen, no xsession errors. 
Unfortunately I don't know where to look for error logs or help anymore. I'
ve also read many threads but they didn't really help much.




May  4 14:39:39 debian10 in.tftpd[3332035]: tftp: client does not accept 
options
May  4 14:39:49 debian10 rpc.mountd[87913]: authenticated mount request from
192.168.1.230:924 for /opt/ltsp/amd64 (/opt/ltsp)
May  4 14:40:00 debian10 ldminfod[3332173]: connect from 192.168.1.230 
(192.168.1.230)
May  4 14:40:19 debian10 ldminfod[3332295]: connect from 192.168.1.230 
(192.168.1.230)

...




Thanks in advance.

Hi Peter,

this list is for LTSP5,
while the new LTSP is supported on github.
Please open a discussion there:
https://github.com/ltsp/ltsp/discussions

Cheers,
Alkis

On 4/25/21 8:09 PM, Peter Tuharsky wrote:
Hallo, guys

I'm trying to run LTSP20 on Debian Bullseye (testing). I do it
accordingly to https://ltsp.org/docs/installation/

I don't see any problem during installation, but the client bootup
process ends with:


Could not configure PAM for SSH authentication!

LTSP command failed: /usr/share/ltsp/client/login/pamltsp install

Stopping plymouth

Aborting ltsp


Please, does anybody have an idea, what could be the culprit? Google
dosen't give a clue.




_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Hallo, guys

I'm trying to run LTSP20 on Debian Bullseye (testing). I do it 
accordingly to https://ltsp.org/docs/installation/

I don't see any problem during installation, but the client bootup 
process ends with:


Could not configure PAM for SSH authentication!

LTSP command failed: /usr/share/ltsp/client/login/pamltsp install

Stopping plymouth

Aborting ltsp


Please, does anybody have an idea, what could be the culprit? Google 
dosen't give a clue.

We have some remote workstations that traditionally have been local 
installs of Ubuntu, but since the offices are connected to our main 
network across fiber we would like to transition to LTSP thick clients. 
 From time to time employees in the main office needs to view the remote 
desktop, either for technical support or support with their job duties. 
Not everyone who helps them should have access to all desktops on our 
network, as epoptes provides, and they will be connecting from multiple 
workstations. In the past we have run remote desktop sharing (vino) 
remotely and used remmina locally to view it. When I try to start vino 
through the gnome-control-center in Ubuntu 20.04 thick clients, it 
refuses to start. Running gnome-control-center from the command line 
shows the following error: "(gnome-control-center:26271): 
sharing-cc-panel-WARNING **: 14:50:14.358: Failed to enable service 
vino-server: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Sharing 
cannot be enabled on this network, status is '0'". Can anybody tell me 
how to get vino working, or recommend another program that allows VNC 
viewers to view a specific LTSP desktop?
-- 
Michael Crider, IT Supervisor
Howell-Oregon Electric Cooperative
West Plains MO
http://www.hoecoop.org

Hello Rolf,

Thank you for your response.

On Fri, Mar 26, 2021 at 4:53 AM Rolf-Werner Eilert <rw...@os...>
wrote:

> On our server, I have scripts that can read a list of usernames to make
> or remove multiple accounts.
>

Do you mind sharing the script (or at least the relevant parts)?

And we are running LTSP5 under Ubuntu Mate 18 (yet), but I plan to
> update to a new server soon. However, I guess the same will be necessary
> there.
>

We are also running Ubuntu Mate 18 and it's been working very well so we're
not planning on updating yet.

Thank you so much,
Joseph



> Am 26.03.21 um 02:52 schrieb Joseph Bishay:
> > Hello everyone,
> >
> > I hope you are all doing very well today.
> >
> > We are running our LTSP server and things are working very well.
> >
> > Over the years, and especially recently, we've had a situation where we
> > had a large number of students who finished at the school but their
> > files and accounts are still on the LTSP server.
> >
> > Is there a best-practice or any recommendations for how to deal with
> > accounts that are no longer active?  Both the username themselves as
> > well as their files, etc?  I'd like to free up space and resources and
> > clean up the users, etc.
> >
> > Thanks so much!
> > Joseph
> >
> >
> > _____________________________________________________________________
> > Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
> >        https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> > For additional LTSP help,   try #ltsp channel on irc.freenode.net
> >
>
>
>
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
>

On our server, I have scripts that can read a list of usernames to make 
or remove multiple accounts.

As our students have a special personal "Tasks" directory to store their 
works/homeworks for exchange with the teachers, these scripts have a bit 
more jobs than just call useradd and userdel. Moreover, students are 
assigned certain group rights and stuff.

And we are running LTSP5 under Ubuntu Mate 18 (yet), but I plan to 
update to a new server soon. However, I guess the same will be necessary 
there.

Regards
Rolf


Am 26.03.21 um 02:52 schrieb Joseph Bishay:
> Hello everyone,
> 
> I hope you are all doing very well today.
> 
> We are running our LTSP server and things are working very well.
> 
> Over the years, and especially recently, we've had a situation where we 
> had a large number of students who finished at the school but their 
> files and accounts are still on the LTSP server.
> 
> Is there a best-practice or any recommendations for how to deal with 
> accounts that are no longer active?  Both the username themselves as 
> well as their files, etc?  I'd like to free up space and resources and 
> clean up the users, etc.
> 
> Thanks so much!
> Joseph
> 
> 
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>        https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
> 

Hello everyone,

I hope you are all doing very well today.

We are running our LTSP server and things are working very well.

Over the years, and especially recently, we've had a situation where we had
a large number of students who finished at the school but their files and
accounts are still on the LTSP server.

Is there a best-practice or any recommendations for how to deal with
accounts that are no longer active?  Both the username themselves as well
as their files, etc?  I'd like to free up space and resources and clean up
the users, etc.

Thanks so much!
Joseph

Copied from https://github.com/ltsp/ltsp/issues/1#issuecomment-753452587
Happy new year to all!
And as always, special thanks to Vagrant for uploading to Debian.

## Announcing LTSP 21.01

A new version LTSP 21.01 is available in the [proposed 
PPA](https://ltsp.org/advanced/proposed-ppa/). Please test and verify 
that it doesn't cause any issues for you, as it will be uploaded in the 
[stable PPA](https://ltsp.org/docs/ppa/) and in [Debian 
testing](https://packages.debian.org/bullseye/ltsp) in a few days.

Changelog from the previous version:

   * Update copyright in man pages
   * Support openssh 8.4 (#358)
   * Document separate partitions in ltsp image (#347)
   * Correctly pass SSH_OPTIONS to pamltsp (#114)
   * Increase SSHFS cleanup timeout
   * Avoid more than 2 login error messages (#353)
   * Remove all resume configuration files (#346)
   * Transform INCLUDE into section_call (#343)
   * Rename Raspbian to Raspberry Pi OS (#342)
   * Allow NFS home in live CDs (#138)
   * Avoid tmpfs home (#338)
   * Make images accessible only by root (#336)
   * Document the correct /etc/ltsp/bin/sshfs path (#341)
   * Initial SSSD/LDAP support (#338)
   * Update issue template for discussions
   * Prevent AUTOLOGIN blocking boot in unmatched clients (#157)
   * Disable nfs-kernel-server by default
   * Update ltsp.conf.5.md

Heureka! :) I found it...

There is a cache file /var/lib/misc/dnsmasq.leases where dnsmasq stores 
any leases it once made, seemingly forever. On my server, this file 
dated from Sept 11, long before I changed the MAC-IP pairs in 
/etc/dnsmasq.conf, and it still had the old configuration for my client 
numbers 104 and 140.

Each time it starts, dnsmasq seems to look into this file first before 
looking up the adresses in dnsmasq.conf. So I deleted the file, 
restarted dnsmasq service, and voilà: Now it read the new client address 
for my number 104, everything works fine.

The leases file is built up again now: each time dnsmasq must find a 
"new" address, it writes its result here. So when I  have to write any 
other changes into dnsmasq.conf, I will have to delete the leases file 
and restart the service.

Regards
Rolf


Am 25.11.20 um 08:50 schrieb Rolf-Werner Eilert:
> This is a problem under LTSP5 with Ubuntu Mate 18.
> 
> To make things short: I have a 2 NIC setup, and on the inner line with 
> 192.168.67.x is the LTSP network. There is a long list in dnsmasq.conf 
> with each client to have fixed MAC-to-IP-to-LTSP numbers (so I am able 
> to identify each client).
> 
> The list works well, but now I put one of the clients to another lab to 
> replace a defective one. The numbers were changed in dnsmasq.conf, but 
> the client is still identified under its former IP. Rebooting didn't fix 
> it.
> 
> Here is an excerpt of the list. I used 140 to replace 104:
> 
> dhcp-host=94:C6:91:14:FC:30,ws001,192.168.67.101,infinite
> dhcp-host=94:C6:91:15:F7:3A,ws002,192.168.67.102,infinite
> dhcp-host=94:C6:91:15:41:1E,ws003,192.168.67.103,infinite
> #dhcp-host=94:C6:91:14:E3:87,ws004,192.168.67.104,infinite
> dhcp-host=94:C6:91:15:A8:96,ws004,192.168.67.104,infinite
> 
> and down in the list where 140 came from:
> 
> #dhcp-host=94:C6:91:15:A8:96,ws040,192.168.67.140,infinite
> 
> The strange thing is, the whole setup keeps running as if I had never 
> changed anything on dnsmasq.conf. Is there a another list? I couldn't 
> find any. One clue might be that from day one, my naming "ws..." was 
> ignored and all clients are named "LTSP...". But if dnsmasq.conf doesn't 
> have any effect, where have the correct IPs come from since then?
> 
> Setting "#" should work as a comment, shouldn't it? (Otherwise down in 
> the list the old 140 entry would overwrite the new one above, of course 
> that would explain it, but there are lots of more comments in the file...)
> 
> Maybe someone here with an idea?
> 
> Regards
> Rolf
> 
> 
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
> 

Thank you Sean for the hint.

My /etc/dnsmasq.d/ltsp-server-dnsmasq.conf only holds some general 
rules. The /etc/dnsmasq.conf seems to be the real and only (?) 
configuration file in my setup. At least I haven't found any other.

All values in this file seem to be regarded, but when I change 
something, the new values are not read but the old ones continue. So the 
question is, what to do after changing this file? "service dnsmasq 
restart" doesn't help.

Regards
Rolf


Am 30.11.20 um 09:32 schrieb Sean Carte:
> This mailing list isn't used anymore, please use the LTSP community issues:
> https://github.com/ltsp/ltsp/issues/ 
> <https://github.com/ltsp/ltsp/issues/68>
> 
> But, since I'm still here, which dnsmasq.conf are you using? There's 
> /etc/dnsmasq.d/ltsp-dnsamasq.conf and /etc/dnsmasq.conf.
> 
> On Wed, 25 Nov 2020 at 10:09, Rolf-Werner Eilert <rw...@os... 
> <mailto:rw...@os...>> wrote:
> 
>     This is a problem under LTSP5 with Ubuntu Mate 18.
> 
>     To make things short: I have a 2 NIC setup, and on the inner line with
>     192.168.67.x is the LTSP network. There is a long list in dnsmasq.conf
>     with each client to have fixed MAC-to-IP-to-LTSP numbers (so I am able
>     to identify each client).
> 
>     The list works well, but now I put one of the clients to another lab to
>     replace a defective one. The numbers were changed in dnsmasq.conf, but
>     the client is still identified under its former IP. Rebooting didn't
>     fix it.
> 
>     Here is an excerpt of the list. I used 140 to replace 104:
> 
>     dhcp-host=94:C6:91:14:FC:30,ws001,192.168.67.101,infinite
>     dhcp-host=94:C6:91:15:F7:3A,ws002,192.168.67.102,infinite
>     dhcp-host=94:C6:91:15:41:1E,ws003,192.168.67.103,infinite
>     #dhcp-host=94:C6:91:14:E3:87,ws004,192.168.67.104,infinite
>     dhcp-host=94:C6:91:15:A8:96,ws004,192.168.67.104,infinite
> 
>     and down in the list where 140 came from:
> 
>     #dhcp-host=94:C6:91:15:A8:96,ws040,192.168.67.140,infinite
> 
>     The strange thing is, the whole setup keeps running as if I had never
>     changed anything on dnsmasq.conf. Is there a another list? I couldn't
>     find any. One clue might be that from day one, my naming "ws..." was
>     ignored and all clients are named "LTSP...". But if dnsmasq.conf
>     doesn't
>     have any effect, where have the correct IPs come from since then?
> 
>     Setting "#" should work as a comment, shouldn't it? (Otherwise down in
>     the list the old 140 entry would overwrite the new one above, of course
>     that would explain it, but there are lots of more comments in the
>     file...)
> 
>     Maybe someone here with an idea?
> 
>     Regards
>     Rolf
> 
> 
>     _____________________________________________________________________
>     Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>     https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
>     For additional LTSP help,   try #ltsp channel on irc.freenode.net
>     <http://irc.freenode.net>
> 
> 
> 
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>        https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
> 

Sorry, please forgive my confusion.

On Mon, 30 Nov 2020 at 10:39, Alkis Georgopoulos <al...@gm...> wrote:

> Hi all,
>
> This mailing list is still used for LTSP5 discussions.
> https://github.com/ltsp/ltsp/issues/ is for new LTSP bugs,
> and https://github.com/ltsp/ltsp/discussions/ is for new LTSP discussions.
>
> (since github introduced the "discussions" feature, the "community
> issues" were migrated to "ltsp discussions"; and the whole "ltsp
> community repository", https://github.com/ltsp/community, will be
> deleted shortly)
>
> Alkis
>
> On 11/30/20 10:32 AM, Sean Carte wrote:
> This mailing list isn't used anymore, please use the LTSP community issues:
> https://github.com/ltsp/ltsp/issues/
> <https://github.com/ltsp/ltsp/issues/68>
>
> But, since I'm still here, which dnsmasq.conf are you using? There's
> /etc/dnsmasq.d/ltsp-dnsamasq.conf and /etc/dnsmasq.conf.
>
> On Wed, 25 Nov 2020 at 10:09, Rolf-Werner Eilert <rw...@os...
> <mailto:rw...@os...>> wrote:
>
>      This is a problem under LTSP5 with Ubuntu Mate 18.
>
>      To make things short: I have a 2 NIC setup, and on the inner line with
>      192.168.67.x is the LTSP network. There is a long list in dnsmasq.conf
>      with each client to have fixed MAC-to-IP-to-LTSP numbers (so I am able
>      to identify each client).
>
>      The list works well, but now I put one of the clients to another lab
> to
>      replace a defective one. The numbers were changed in dnsmasq.conf, but
>      the client is still identified under its former IP. Rebooting didn't
>      fix it.
>
>      Here is an excerpt of the list. I used 140 to replace 104:
>
>      dhcp-host=94:C6:91:14:FC:30,ws001,192.168.67.101,infinite
>      dhcp-host=94:C6:91:15:F7:3A,ws002,192.168.67.102,infinite
>      dhcp-host=94:C6:91:15:41:1E,ws003,192.168.67.103,infinite
>      #dhcp-host=94:C6:91:14:E3:87,ws004,192.168.67.104,infinite
>      dhcp-host=94:C6:91:15:A8:96,ws004,192.168.67.104,infinite
>
>      and down in the list where 140 came from:
>
>      #dhcp-host=94:C6:91:15:A8:96,ws040,192.168.67.140,infinite
>
>      The strange thing is, the whole setup keeps running as if I had never
>      changed anything on dnsmasq.conf. Is there a another list? I couldn't
>      find any. One clue might be that from day one, my naming "ws..." was
>      ignored and all clients are named "LTSP...". But if dnsmasq.conf
>      doesn't
>      have any effect, where have the correct IPs come from since then?
>
>      Setting "#" should work as a comment, shouldn't it? (Otherwise down in
>      the list the old 140 entry would overwrite the new one above, of
> course
>      that would explain it, but there are lots of more comments in the
>      file...)
>
>      Maybe someone here with an idea?
>
>      Regards
>      Rolf
>
>
>      _____________________________________________________________________
>      Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
>      For additional LTSP help,   try #ltsp channel on irc.freenode.net
>      <http://irc.freenode.net>
>
>
>
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>         https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
>
>
>
>
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
>

Hi all,

This mailing list is still used for LTSP5 discussions.
https://github.com/ltsp/ltsp/issues/ is for new LTSP bugs,
and https://github.com/ltsp/ltsp/discussions/ is for new LTSP discussions.

(since github introduced the "discussions" feature, the "community 
issues" were migrated to "ltsp discussions"; and the whole "ltsp 
community repository", https://github.com/ltsp/community, will be 
deleted shortly)

Alkis

On 11/30/20 10:32 AM, Sean Carte wrote:
This mailing list isn't used anymore, please use the LTSP community issues:
https://github.com/ltsp/ltsp/issues/
<https://github.com/ltsp/ltsp/issues/68>

But, since I'm still here, which dnsmasq.conf are you using? There's
/etc/dnsmasq.d/ltsp-dnsamasq.conf and /etc/dnsmasq.conf.

On Wed, 25 Nov 2020 at 10:09, Rolf-Werner Eilert <rw...@os...
<mailto:rw...@os...>> wrote:

     This is a problem under LTSP5 with Ubuntu Mate 18.

     To make things short: I have a 2 NIC setup, and on the inner line with
     192.168.67.x is the LTSP network. There is a long list in dnsmasq.conf
     with each client to have fixed MAC-to-IP-to-LTSP numbers (so I am able
     to identify each client).

     The list works well, but now I put one of the clients to another lab to
     replace a defective one. The numbers were changed in dnsmasq.conf, but
     the client is still identified under its former IP. Rebooting didn't
     fix it.

     Here is an excerpt of the list. I used 140 to replace 104:

     dhcp-host=94:C6:91:14:FC:30,ws001,192.168.67.101,infinite
     dhcp-host=94:C6:91:15:F7:3A,ws002,192.168.67.102,infinite
     dhcp-host=94:C6:91:15:41:1E,ws003,192.168.67.103,infinite
     #dhcp-host=94:C6:91:14:E3:87,ws004,192.168.67.104,infinite
     dhcp-host=94:C6:91:15:A8:96,ws004,192.168.67.104,infinite

     and down in the list where 140 came from:

     #dhcp-host=94:C6:91:15:A8:96,ws040,192.168.67.140,infinite

     The strange thing is, the whole setup keeps running as if I had never
     changed anything on dnsmasq.conf. Is there a another list? I couldn't
     find any. One clue might be that from day one, my naming "ws..." was
     ignored and all clients are named "LTSP...". But if dnsmasq.conf
     doesn't
     have any effect, where have the correct IPs come from since then?

     Setting "#" should work as a comment, shouldn't it? (Otherwise down in
     the list the old 140 entry would overwrite the new one above, of course
     that would explain it, but there are lots of more comments in the
     file...)

     Maybe someone here with an idea?

     Regards
     Rolf


     _____________________________________________________________________
     Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
     https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
     For additional LTSP help,   try #ltsp channel on irc.freenode.net
     <http://irc.freenode.net>



_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
        https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

This mailing list isn't used anymore, please use the LTSP community issues:
https://github.com/ltsp/ltsp/issues/
<https://github.com/ltsp/ltsp/issues/68>

But, since I'm still here, which dnsmasq.conf are you using? There's
/etc/dnsmasq.d/ltsp-dnsamasq.conf and /etc/dnsmasq.conf.

On Wed, 25 Nov 2020 at 10:09, Rolf-Werner Eilert <rw...@os...> wrote:

> This is a problem under LTSP5 with Ubuntu Mate 18.
>
> To make things short: I have a 2 NIC setup, and on the inner line with
> 192.168.67.x is the LTSP network. There is a long list in dnsmasq.conf
> with each client to have fixed MAC-to-IP-to-LTSP numbers (so I am able
> to identify each client).
>
> The list works well, but now I put one of the clients to another lab to
> replace a defective one. The numbers were changed in dnsmasq.conf, but
> the client is still identified under its former IP. Rebooting didn't fix
> it.
>
> Here is an excerpt of the list. I used 140 to replace 104:
>
> dhcp-host=94:C6:91:14:FC:30,ws001,192.168.67.101,infinite
> dhcp-host=94:C6:91:15:F7:3A,ws002,192.168.67.102,infinite
> dhcp-host=94:C6:91:15:41:1E,ws003,192.168.67.103,infinite
> #dhcp-host=94:C6:91:14:E3:87,ws004,192.168.67.104,infinite
> dhcp-host=94:C6:91:15:A8:96,ws004,192.168.67.104,infinite
>
> and down in the list where 140 came from:
>
> #dhcp-host=94:C6:91:15:A8:96,ws040,192.168.67.140,infinite
>
> The strange thing is, the whole setup keeps running as if I had never
> changed anything on dnsmasq.conf. Is there a another list? I couldn't
> find any. One clue might be that from day one, my naming "ws..." was
> ignored and all clients are named "LTSP...". But if dnsmasq.conf doesn't
> have any effect, where have the correct IPs come from since then?
>
> Setting "#" should work as a comment, shouldn't it? (Otherwise down in
> the list the old 140 entry would overwrite the new one above, of course
> that would explain it, but there are lots of more comments in the file...)
>
> Maybe someone here with an idea?
>
> Regards
> Rolf
>
>
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
>

This is a problem under LTSP5 with Ubuntu Mate 18.

To make things short: I have a 2 NIC setup, and on the inner line with 
192.168.67.x is the LTSP network. There is a long list in dnsmasq.conf 
with each client to have fixed MAC-to-IP-to-LTSP numbers (so I am able 
to identify each client).

The list works well, but now I put one of the clients to another lab to 
replace a defective one. The numbers were changed in dnsmasq.conf, but 
the client is still identified under its former IP. Rebooting didn't fix it.

Here is an excerpt of the list. I used 140 to replace 104:

dhcp-host=94:C6:91:14:FC:30,ws001,192.168.67.101,infinite
dhcp-host=94:C6:91:15:F7:3A,ws002,192.168.67.102,infinite
dhcp-host=94:C6:91:15:41:1E,ws003,192.168.67.103,infinite
#dhcp-host=94:C6:91:14:E3:87,ws004,192.168.67.104,infinite
dhcp-host=94:C6:91:15:A8:96,ws004,192.168.67.104,infinite

and down in the list where 140 came from:

#dhcp-host=94:C6:91:15:A8:96,ws040,192.168.67.140,infinite

The strange thing is, the whole setup keeps running as if I had never 
changed anything on dnsmasq.conf. Is there a another list? I couldn't 
find any. One clue might be that from day one, my naming "ws..." was 
ignored and all clients are named "LTSP...". But if dnsmasq.conf doesn't 
have any effect, where have the correct IPs come from since then?

Setting "#" should work as a comment, shouldn't it? (Otherwise down in 
the list the old 140 entry would overwrite the new one above, of course 
that would explain it, but there are lots of more comments in the file...)

Maybe someone here with an idea?

Regards
Rolf

LTSP applied and got accepted in the github discussions beta program, so 
[discussions](https://github.com/ltsp/ltsp/discussions) got enabled for 
the LTSP repository.

This means that the [LTSP community 
repository](https://github.com/ltsp/community) is now obsolete.
Its [issues](https://github.com/ltsp/community/issues) will be moved 
into discussions,
and its [wiki](https://github.com/ltsp/community/wiki) will be moved 
into the [LTSP repository wiki](https://github.com/ltsp/ltsp/wiki).

This will be done over the next few days.
Please do not file community issues anymore, but start ltsp discussions 
instead.

https://github.com/ltsp/ltsp/discussions

Cheers,
Alkis

Hi Rolf,

Please use https://github.com/Epoptes/epoptes/issues for Epoptes issues.

Cheers,
Alkis


Στις Πέμ, 17 Σεπ 2020, 13:57 ο χρήστης Rolf-Werner Eilert <
rw...@os...> έγραψε:

> Alkis,
>
> This is on LTSP5, I run Epoptes as remoteapp as you know, and one of our
> teachers does. I did an update, and I saw that it updated Epoptes too.
>
> Now suddenly I can see myself under Found Clients and X-Hidden. Does the
> teacher see me as well? I hope not (and cannot check it right now).
> Normally one shouldn't see oneself anyway, or have you changed this for
> some reason?
>
> Regards
> Rolf
>
>
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
>

Alkis,

This is on LTSP5, I run Epoptes as remoteapp as you know, and one of our 
teachers does. I did an update, and I saw that it updated Epoptes too.

Now suddenly I can see myself under Found Clients and X-Hidden. Does the 
teacher see me as well? I hope not (and cannot check it right now). 
Normally one shouldn't see oneself anyway, or have you changed this for 
some reason?

Regards
Rolf