Ubuntu Servers :: Restrict User Session Numbers And Allow Resuming Previous User Session?
Jun 30, 2010
I am currently in a project to set up an LTSP server with 10 thin clients. I am using Ubuntu 9.10 (Karmic).
Installing server and booting clients are working fine. Now, according to the need, I have to restrict user session numbers and allow resuming previous user session.
I have achieved to do the first one, but still could not able to setup the second one. As per requirement, if some thin can have power failure, the same session should be restored back. I am confused here, if I need to focus on saving xsessions or saving gnome sessions. I am looking for a concrete solution as I am running out of time.
In recent versions of ubuntu, the behavior of gdm and gnome is changed so that if a gnome user doesn't touch the mouse or keyboard for a while, the session is locked, and they have to type their password in order to get back in. I dislike this behavior, because on some of the machines I use and manage, people will walk away and not come back, and then there is no way to log them out. I can switch and log in as a different user, but the AWOL user's session is sitting there eating up resources until the machine is rebooted. I prefer the old behavior, with no locking. Is there any way to get the old behavior back? I've looked through the gdm.conf docs, but can't seem to find anything relevant. This actually seems more like a gnome issue than a gdm issue. I think what's changed is that gnome now invokes a screensaver after a certain amount of time, and that screensaver locks the session.
I'm having problems resuming a suspended session on my HP DV6-1240ea laptop. On attempting to resume a suspended session the screen remains blank. I've tried pressing the Caps Lock key to see if the LED lights but it does not which would suggest the system has not started.
I installed KDE 4.3.5 on my existing Gnome desktop and i have two users using the computer. Now from Gnome I am accustomed to switch between session very easy and the sessions continue to run. If I use the Switch option from KDE it just looks my screen and does not switch. Is it possible that I miss some programs? I installed it with Yast and used the group option. I am pretty sure that I missed something during the installation.
I recently installed debian 8 stretch with xfce. Since the first time I boot, I have problem starting my X session: from lightdm I always attemped 2 or 3 times before it login (it returned me on lightdm prompt after a short splash screen).
Now it stopped working: the only way I can start xsession is running startx as root. When I try as user it starts the "splash" and return me to the tty with this error message:
Code: Select allServer terminated with error (1). Closing log file(EE)
This is my ~/.local/share/xorg/Xorg.0.log
Code: Select all[ 27.703] X.Org X Server 1.18.2 Release Date: 2016-03-11 [ 27.704] X Protocol Version 11, Revision 0 [ 27.704] Build Operating System: Linux 3.16.0-4-amd64 i686 Debian [ 27.704] Current Operating System: Linux debian 4.3.0-1-686-pae #1 SMP Debian 4.3.5-1 (2016-02-06) i686
And this is my /etc/X11//Xsession
Code: Select all#!/bin/sh # # /etc/X11/Xsession # # global Xsession file -- used by display managers and xinit (startx) # $Id: Xsession 967 2005-12-27 07:20:55Z dnusinow $
and this the .xsession-errors:
Code: Select allXsession: X session started for lucatastrophe at Tue Mar 29 10:21:09 CEST 2016 localuser:lucatastrophe being added to access control list openConnection: connect: No such file or directory cannot connect to brltty at :0 dbus-update-activation-environment: setting MAIL=/var/mail/lucatastrophe
I try to reconfigure Xorg but the Xorg -configure command result in another segmentation fault.
I think that the problem could be related with old configuration (when I install this version of debian I maintain the /home partition and my previous OS was debian 7 with xfce).
Quite some time ago I managed to get sound working perfectly on my DELL Inspiron 1720 under openSUSE 11.2 and KDE 4.3.5. Then suddenly some months ago for one of the four regular users on my system sound stopped working! KMix is always muted after KDE session startup for this user and even if you unmute it there's still absolutely no sound; in particular, the commandspeaker-test -c2 -l5 -twavdoesn't generate any sound (while I do see the printed output which doesn't contain any error messages). Even if I su to root in the very same Konsole window speaker-test remains silent!
Since sound is OK for the three other regular users I've already compared KMix settings as well as System Settings > Multimedia for each of the regular users but found absolutely no differences. BTW: In System Settings > Multimedia I have XINE set as the backend and "PulseAudio" has priority over "HDA Intel (STAC92xx Analog)" for all sort of audio output, and - perhaps needless to mention - all the four regular users are members of group "audio".
I recently installed Suse Linux enterprise Desktop 11 on my box. I created an user and logged in first time into a GNOME session without any problems. Last time I logged in I selected the session as TWM and that got me into the T windows manager just fine. Now when I log out and try to log back into a GNOME session, it will still log me into the TVM sessionI have tried restarting the boxHowever, when I remote log in to the machine it will let me get on the GNOME session just fine. I'm guessing this is probably a really simple fix, however I am a Linux newbie and doing a google search isn't yielding me what I'm looking for.
Outside of using something like screen, is it possible to 'assume' an active user session under Linux/UNIX?For example, I ssh to my server from home. Then I ssh to it form work. I want to kill the home-spawned session, and "take-over" all of the processes that it had running.
Recently I deleted files from my root/share folder in an attempt to remove a program which had made the system virtually unusable. Upon reboot of the system I accessed the partition I had just edited and I found that I was unable to login using the login manager, every time I hit login it just returns me to the same screen displaying the message: unable to start session.
i wonder if you can modify KDE so that users can only log in once with one session.Currently, with KDE 4.5, i have the problem that user can log in several times and then ending up with an application used in a different session which means that you can not use it in the other session.
Is possible (by root of course) to run a command from console, that will be executed on X-session owned by another user on the same linux box/machine ? Example: Can root open xclock for another local user logged into X11 ?
I have problem with sshd server, its authenticate user and then terminate the session. Here is debug log: Jan 1 04:26:41 server sshd: debug1: userauth-request for user root service ssh-connection method none Jan 1 04:26:41 server sshd: debug1: attempt 0 failures 0 Jan 1 04:26:43 server sshd: debug1: userauth-request for user root service ssh-connection method password Jan 1 04:26:43 server sshd: debug1: attempt 1 failures 0 Jan 1 04:26:43 server sshd: Accepted password for root from xx.xx.xx.xxx port 50971 ssh2 Jan 1 04:26:43 server sshd: debug1: monitor_child_preauth: root has been authenticated by privileged process .....
I noticed (the hard way) that enabling a guest session under 9.04 does not lock the source user. I enabled a guest session for someone and came back to find them rooting through my files. By quitting the guest session, it goes back to the source user's desktop without requiring a password. Shouldnt it go to gnome-screensaver automatically? Can this be changed? Is it a bug?
to replicate: log into source user's account use the menu to start a guest session quit the guest session root through files un-opposed.
I've got a somewhat anemic box, resource-wise, set up in the office where any authorized user plus a guest account can log on. Guest is tightly restricted, but we get a lot of people passing through who need one-time or occasional access - this isn't the big problem. What's causing me problems is that a user will log in, walk away or go to the john and the screen locks. Next user (or this one comes back) and winds up doing another login. At the end of a week or so, I may have a couple of dozen sessions listed when I ask for "users". Since some of these session contain open applications they eat up an awful lot of a marginal amount of available memory. How do I kill the entire session (as root) for a user? Gotta be simple but it's not obvious to me.
I'm in the process of restricting access to my Linux production box, where ssh access needs to be limited to only a few MAC addresses.I've followed the instructions outlined in this guide and ran the following two commands:
/sbin/iptables -A INPUT -m mac --mac-source XX:XX:XX:XX:XX:XX -j DROP /sbin/iptables -A INPUT -p tcp --destination-port 22 -m mac --mac-source XX:XX:XX:XX:XX:XX -j ACCEPT root@xxxx:~/#: iptables --list
I've recently installed Fedora 14 (x86_64) on my Alienware m15x laptop which has a NVIDIA GTX 260m onboard. Now I have followed leigh123linux's guide to installing those drivers on F14. The installation is a success and everything seems to be in working order, until the system randomly logs the user out and/or restarts the session with no warning. The screen goes black and the nvidia logo appears and then its back to the login screen again. This can happen many times with no apparent stop insight. This does not happen with the default F14 drivers that come with the installation, I have tried several re installations of the Fedora OS and several re installations of the NVIDIA driver, i still have the same problems.
I'd like to use screen to execute a file with a certain session name instead of just numbers... or at least have a more permanent name, I'd like to be able to use it all in one command though. So I can put it into a script.Also: is there a way I can remove or change what comes up at the debian login screen so instead of debain 5.0 I can make it say something else? Also when I login the message that comes up is a little annoying, is there a way I could remove or change that too?