Lucas,
You don't need to do anything. Simply set:
LDM_LIMIT_ONE_SESSION = True
in your lts.conf file.
--
LDM does not warn when a user is already logged in
https://bugs.launchpad.net/bugs/67366
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi.
I am using ubuntu 9.04 server. But there is not a directory called rc.d
in ldm.
I need create it?
Help.
Thx.
--
LDM does not warn when a user is already logged in
https://bugs.launchpad.net/bugs/67366
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
This bug has been fixed with the S15-userLoginCheck ldm rc.d script
included in the upstream code and in Jaunty. Marking the bug as fix
released upstream (it's already marked as fixed for ubuntu).
** Changed in: ltsp
Status: New => Fix Released
--
LDM does not warn when a user is already
Thank you for your quick response.
Yes, I am using Ubuntu, I will make the changes you have suggested and get
back!
Warm Regards,
Avinash
On Tue, Nov 4, 2008 at 5:17 PM, GideonRomm
<[EMAIL PROTECTED]>wrote:
> If you are using Ubuntu, the lts.conf file should be in:
> /var/lib/tftpboot/ltsp/i3
If you are using Ubuntu, the lts.conf file should be in:
/var/lib/tftpboot/ltsp/i386/lts.conf
If it is not there, create it in the format:
[default]
LDM_LIMIT_ONE_SESSION = True
Also, if using Ubuntu, after adding the S15-userLoginCheck, you should run:
sudo ltsp-update-image --arch=i386
-G
Hi GideonRomm,
I did create the S15-userLoginCheck under
/opt/ltsp/i386/usr/lib/ldm/rc.d and copied the contents of your
attachment. I also found another file under this directory called S01
-setup-xauth.
I also added the LDM_LIMIT_ONE_SESSION = True in lts.conf file. I
restarted the dhcp3-server
included in intrepid
** Changed in: ltsp (Ubuntu Intrepid)
Status: In Progress => Fix Released
--
LDM does not warn when a user is already logged in
https://bugs.launchpad.net/bugs/67366
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Gadi,
Wow, great work =) I don't understand a lot of your script but it looks
to me like this script will also kill stale procs (I.E. not procs in
another active user session) - is that true? If so, it might be worth
mentioning that this would replace the unofficial package
"gnome-watchdog", w
The attached file can be used in:
/opt/ltsp/i386/usr/lib/ldm/rc.d/S15-userLoginCheck
with lts.conf param:
LDM_LIMIT_ONE_SESSION = True
** Attachment added: "rc.d file to achieve limiting one session per server"
http://launchpadlibrarian.net/17939928/S15userLoginCheck.20080924
--
LDM does
** Also affects: ltsp
Importance: Undecided
Status: New
--
LDM does not warn when a user is already logged in
https://bugs.launchpad.net/bugs/67366
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
I am using Ubuntu Studio + LTSP 5.0 and i am facing the same problem.
The server doesnot warn the user that he/she has already logged in on
another machine.
This creates a problem when the user open the same file, make changes
and save the file, which is already open on another machine.
Hope this
Oliver is perfectly right about the gdm, due to my present problems with
using ldm I am very much up to date on how to setup gdm 8-)
Best,
r.r.
--
LDM does not warn when a user is already logged in
https://bugs.launchpad.net/bugs/67366
You received this bug notification because you are a member
i dont think we should differ from gdm behavior here ... afaik it
automatically warns the user about an existing session with a dialog
that has a button saying "log me in anyway" and afaik its configurable
by the admin if the dialog is shown ... (i have to look, i may be wrong
here)
--
LDM does n
A clustered approach is too much to get in for this round. We'll handle the
simple "same server" case for now, and spec this out next time.
Lots of possible issues on this one: what if the file's created, but the lock
information becomes stale due to improper logout. Where do we
put it? Should
One important thing to support multiple hosts : multiple sessions must
be avoided over the whole cluster. A kind of global variable is needed
for that. A lock file can be used in the home directory for that, that
contains Xsession PID and the server on which the session is started.
Assuming that ea
lets do that properly and have a separate feedback gui app for the differen
feedbacks we can have if the greeter is gone ... not zenity :)
if you got something for the backend let me know, i'll look into hacking up a
basic gui :)
--
LDM does not warn when a user is already logged in
https://bu
Did some initial work on this. Looks like as part of the new rc
subsystem within ldm, we can do a pgrep for session information, If
found, then we can use something like zenity to pop up a warning. I'll
look at getting something into bzr this weekend.
--
LDM does not warn when a user is already
I am seeing this problem too. Is there a workaround until the fix (apart
from a re-install) ? Or is Ctrl-Alt-Backspace the only way out ?
Thanks,
-Mohan.
--
LDM does not warn when a user is already logged in
https://bugs.launchpad.net/bugs/67366
You received this bug notification because you are
I'll handle this as part of the LDM rewrite
** Changed in: ltsp (Ubuntu)
Assignee: Oliver Grawert => Scott Balneaves
Status: Confirmed => In Progress
--
LDM does not warn when a user is already logged in
https://bugs.launchpad.net/bugs/67366
You received this bug notification because
Using an edubuntu server install made from the feisty i386 edubuntu dvd
20070418, I absentmindedly logged in twice - once on a thin client and
once on the server.
The result was that on the server I was no longer able to log out at
all. Even logging out on the client and C-A-Backspace-killing the
** Changed in: ltsp (Ubuntu)
Importance: Undecided => Wishlist
Assignee: (unassigned) => Oliver Grawert
Status: Unconfirmed => Confirmed
--
LDM does not warn when a user is already logged in
https://launchpad.net/bugs/67366
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
closing the Baltix part, assuming that the problem isn't occuring in
Baltix
** Changed in: Ubuntu
Sourcepackagename: None => ltsp
** Changed in: Baltix
Status: Unconfirmed => Rejected
--
LDM does not warn when a user is already logged in
https://launchpad.net/bugs/67366
--
ubuntu-bugs
** Also affects: Ubuntu
Importance: Undecided
Status: Unconfirmed
--
LDM does not warn when a user is already logged in
https://launchpad.net/bugs/67366
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
23 matches
Mail list logo
