|00:35||lucascastro has joined IRC (email@example.com)|
|00:41||lucascastro has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|01:57||eadthem_gfg has left IRC (email@example.com, Quit: Leaving)|
|07:55||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|08:18||Statler has joined IRC (Statler!~Georg@p5B30E084.dip0.t-ipconnect.de)|
|10:18||jeremies has joined IRC (firstname.lastname@example.org)|
|11:56||jeremies has left IRC (email@example.com, Quit: Leaving)|
|12:18||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Ping timeout: 252 seconds)|
|12:19||Statler has left IRC (Statler!~Georg@p5B30E084.dip0.t-ipconnect.de, Remote host closed the connection)|
|14:02||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|15:21||GodFather has left IRC (GodFatheremail@example.com, Ping timeout: 268 seconds)|
|17:41||lucascastro has joined IRC (firstname.lastname@example.org)|
|17:47||jeremies has joined IRC (email@example.com)|
How to stop a thin client that has autologin activated?
To power it off? From epoptes
Or from the menu, if you have a recent mate version
Yes to power it off
From the menu of the client?
From the menu of the client it boots the client another time.
Yes from the client menu. Are you using mate?
And you select poweroff and it reboots?
The computer doesn't reboot in the sense to boot the bios but it shows a black screen and then it shows another time the desktop start screen of mate.
With epoptes it works
OK. Some desktops were patched to do this for ltsp, it looks like the mate patch isn't there
So from the client you would need to call the epoptes logout/endsession script
E.g. make a desktop shortcut for it
Ok. Thank you.
alkisg: do you know if having a desktop computer wake up all the time can make its life shorter ?
jeremies: I don't know what "wake up all the time" means, as opposed to stand by?
No I don't think it can make its life shorter
I mean idle
idle is already woken up
It's not sleeping
I don't understand what you mean, tell it again using more words.
With the computer powered on (that is the state when you can work with it) all the time, its life isn't shortened ?
Well, it depends. There are servers running for 20 years without dying. So normally no, it shouldn't shorten its life.
Now if you have an SSD or an nvidia card working all the time etc they may be worn out after a lot of use
|18:41||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|18:55||adrianor1 has joined IRC (firstname.lastname@example.org)|
|18:58||adrianorg has left IRC (email@example.com, Ping timeout: 256 seconds)|
|19:13||adrianor1 is now known as adrianorg|
if you install a package with apt in a thin client the package gets installed in the image of the server?
what do you mean by "in a thin client" ?
on a thin client, all the software that the user interacts with is installed on the server
but you can open a terminal and install a package
and if you're running a thin client, that terminal is running on the server
and so will install software on the server
think of a thin client as another mouse, monitor and keyboard for the server
that said, in general it's recommended to use ltsp fat clients these days, if your client hardware can support it
but when you update the image that package will be removed, isn't it?
in a thin client, nothing gets installed on the thin client
it loads it's operating system from the image on the server
all applications, terminals, web browsers, software installation programs, run and operate on the server
so when you install software from a thin client, it's no different than installing it on the server
other thin clients will get the same software installed
and when you rebuild the image, you'll still connect to the same server with the same software installed
if you're running an ltsp fat client, it's different
now, if you're messing around with the LTSP chroot, that's another story
like i said earlier, think of a thin client as another mouse, monitor and keyboard for the server
if you're running a fat client, or running your terminal as a localapp, it's a different story
ok. thank you
|22:52||lucascastro has left IRC (firstname.lastname@example.org, Read error: Connection reset by peer)|
|22:52||lucascastro has joined IRC (email@example.com)|
|23:26||jeremies has left IRC (firstname.lastname@example.org, Quit: Leaving)|