[Bug 865337] New: systemd holds open users in KDE that are loged out, KDE holds open KDEsuid from that user
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c0 Summary: systemd holds open users in KDE that are loged out, KDE holds open KDEsuid from that user Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: stakanov@freenet.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=579753) --> (http://bugzilla.novell.com/attachment.cgi?id=579753) suid stays open User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 This is a possible security problem, at least I to me it seems so. Create a system with three users in kde (A,B,C). Log in the first one (A), the second one (B), the third one(C). Switch between users with alt+ctrl+F7 etc (VT change). Use sudo in terminal with the second one. Now close user "B". Close user C after this. This will cause the first anomaly. The system will hang with a black screen and a minus blinking in the left upper corner. To get out of this you have to change to the first user that was opened. Only then you see a desktop again. Now, if you go to switch user, you see as a user still online the VT of user C. You see VT8 as unused and then of course user A as VT7. Now open with Alt+F2 the processes. You will see: if you do use just the users, they will stay open after logout with two processes: sd-pam and systemd. This is annoying because if (use-case) a user wants to suppress the user in yast he cannot. It says: user still logged in. The user should NOT be logged in anymore. But really tricky it gets when you use sudo. Then you find: the two processes stay open on a per user base but also the process KDESuid of the user that was owner stays open. This process gets not even killed when you do it givin the password of root in the list. You have to open a terminal, search for it and kill it with root rights and Kill (PID number). A logged-out user that in reality is logged-in with a KDEsuid seem to me a bad thing. Put this toghether with the fact that in multiusersystems 64 bit KDE listens on 6001 ecc by default.... Reproducible: Always Steps to Reproduce: 1.create system with three users. 2.login all three, use e.g. sudo with the second 3.logout the second then the third Actual Results: system locks with black screen on logout if the order of logout is not the order of login. Two processes are staying logged in although the user was logged out. If sudo was used in KDE sudo stays open and cannot be easily killed (IF it is noticed by the admin). If one wants to suppress a user with yast, this is denied as "user logged in" logout user first. BTW when this happens also the multi-monitor support often breaks leaving all users with a "cloned mointor" instead of a multi-monitor. This is the case as long as all "logged in processes" are not eliminated, thus, either the user restarts the system, or he kills with the terminal and root rights all the users in question one by one and then logs in again. Otherwise the multi-monitor support will stay broken. Expected Results: A user logged out should be logged out. KDEsuid has to be terminated when the user that evoked it logs out. The order of log out should be insignificant and the system should not lock up with a black screen. Multi-support should not crash of course, but if it does, simple logout and login should be sufficient to restore a working desktop with settings as foreseen. (The monitor thing is just a symptom for the fact that a logged out user does not log out). This is a standard opensuse 13.1 installation. However the users are created with umask 077 (that is the only deviation from the standard). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c1 --- Comment #1 from Drazenko Djuricic <djuricicd@gawnet.ch> 2014-02-24 20:04:52 UTC --- I think this is related too? "systemd" also prevents your home directory from getting properly unmounted if you used "ecryptfs" to encrypt it. This bug was NOT present in openSUSE 12.3. But in openSUSE 13.1 you get the phenomenon that "systemd" seems to keep a PAM session open for your user even after you logout (the home directory remains decrypted and readable!); hence the command "ecryptfs-umount-private" fails to work properly; instead it tells me that the directory is mounted in another session. Another user already tried to report this to the "systemd" folks, but the response there was "not our bug" ...? https://bugs.freedesktop.org/show_bug.cgi?id=72759#c1 http://nwrickert2.wordpress.com/2013/12/16/systemd-user-manager-ecryptfs-and... The root cause here seems to be that even after a user logs out, "systemd" keeps running a "/usr/lib/systemd/systemd --user" process under the ID of the user and also a "(sd-pam)" (= systemd-PAM component?) session; also under the ID of the user. So ... even after logout a user's session never really ends and thus causes numerous side-effects in KDE, sudo, ecryptfs, yast and many other places ...? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c2 --- Comment #2 from Stakanov Schufter <stakanov@freenet.de> 2014-02-24 22:09:52 UTC --- Yeap. Has also the effect that if you do not watch out, an LVM encrypted container of /dev/home stays open while you think the system is shutdown. Instead of opensuse this is getting more "dirty little susy wide open". Seriously, maybe the systemd people have a point there. There will be probably a way to set this up if you change the whole system (and then you are dependent on it, this is all the trick AFAIU). Maybe one should have a look about how Mageia is handling this, if they have the same problem. They have 208 running. If yes, it may well be a systemd problem. If not they are right and it is "not their bug". Probably it will all be O.K. when systemd version 3.10 will come out (the one that integrates support for starting Libre-office and latex :@) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c Xiyuan Liu <xyliu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyliu@suse.com AssignedTo|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c3 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |stakanov@freenet.de --- Comment #3 from Dr. Werner Fink <werner@suse.com> 2014-02-25 07:47:00 UTC --- You may give the latest systemd-208 a try and report if this works for you: http://download.opensuse.org/repositories/Base:/System/openSUSE_13.1/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c4 --- Comment #4 from Stakanov Schufter <stakanov@freenet.de> 2014-02-25 08:21:54 UTC --- Thank you for your suggestion. I will try, but not on this machine (as it is my "production" machine and uttermost key). Beginning next week I can try this on a 32 bit 13.1 machine that may be "scarified" in case things go wrong. AFAIK the 32 bit behaves exactly as the 64 bit in this regard. I will let you know around Monday next week reporting here if that is O.K. for you. Greets. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c5 Neil Rickert <nrickert@ameritech.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nrickert@ameritech.net --- Comment #5 from Neil Rickert <nrickert@ameritech.net> 2014-02-25 12:30:11 UTC --- Mostly I'm adding myself to the CC list. I am wondering more and more, why we switched to "systemd" instead of "sysvinit". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c6 Drazenko Djuricic <djuricicd@gawnet.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |djuricicd@gawnet.ch --- Comment #6 from Drazenko Djuricic <djuricicd@gawnet.ch> 2014-03-05 21:34:58 UTC --- (In reply to comment #3)
You may give the latest systemd-208 a try and report if this works for you:
http://download.opensuse.org/repositories/Base:/System/openSUSE_13.1/
Sorry, openSUSE-noob here ... How do I apply this patch? Do I need to add the above URL in "yast" as repository? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c7 --- Comment #7 from Stakanov Schufter <stakanov@freenet.de> 2014-03-05 22:58:37 UTC --- You should maybe not do it and wait for the result. If you wish to try, you join the aforementioned repo. I did this today. There is currently at least one dependency issue, I will report back here soon after a few days of testing. I did install 209 on a 32 bit system. As it behaves identical as the 64 it should give the same results. P.S. if you are defining yourself as a opensuse-"noop" this is I guess not perfectly stable software and I avoided to do experiments on my production system. You should do the same or at least perform a solid backup before proceeding. Good luck. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c8 --- Comment #8 from Drazenko Djuricic <djuricicd@gawnet.ch> 2014-03-05 23:27:35 UTC --- (In reply to comment #7)
I avoided to do experiments on my production system...
Yes, I have test systems for that. What dependency issues did you run into? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c9 Stakanov Schufter <stakanov@freenet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|stakanov@freenet.de | --- Comment #9 from Stakanov Schufter <stakanov@freenet.de> 2014-03-06 07:01:09 UTC --- O.K. When installing from the indicated repo, you will get a problem with libdbus-1-3 that should install the version 1.7.10-168.1-i586 but cannot so installs version 1.7.4-4.8.1 The component:load kernel modules fails at boot and mkinitrd is forced to uninstall. The advantage you get is none. The user logged out stays proudly logged in with the two processes sd-pam and systemd. The kdesu that stayed open too, has vanished now even in the 208 version of the regular deposits (at least, it is still there when opening the process table but "vanishes" soon after so, I guess it is now killed correctly). However there is a new process that at time stays open which is a .py process, (Do not recall full the name maybe main.py?). This happens with the regular repos but in a not regular way. If you do the substitution with the "base" repos as said, there is an other curious effect: the grub selection does not accept enter when doing it, but runs the whole countdown, no matter what. Other keys however work normally and KDE is flawless, so this seems to be specific to grub2. Is there any possibility that the base repo changed something in grub-functionality? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c10 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |stakanov@freenet.de --- Comment #10 from Dr. Werner Fink <werner@suse.com> 2014-03-24 13:33:49 UTC --- Test out latest systemd from http://download.opensuse.org/repositories/Base:/System/openSUSE_13.1/ and report -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c11 --- Comment #11 from Stakanov Schufter <stakanov@freenet.de> 2014-03-26 05:57:24 UTC --- Hello Werner. I will do so, but as the last time (shortly after writing the 06.03) the update of that repo comming in, broke the 32 bit system, I have to arrange for a convenient backup first. (It was by no way drammatic, just hanging when coming to the kdm screen and thus I had to fiddle it out in console from failsafe mode. So you guessed it, I am on my main machine. As soon as done the arrangements I will then give you feedback ASAP. Will take a few days, but within this week I guess. Thank you for your patience. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c12 Achim Mildenberger <admin@fph.physik.uni-karlsruhe.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |admin@fph.physik.uni-karlsr | |uhe.de --- Comment #12 from Achim Mildenberger <admin@fph.physik.uni-karlsruhe.de> 2014-04-09 08:17:40 UTC --- I'm also encountering two hanging processes after user-logins. /usr/lib/systemd/systemd --user (sd-pam) on openSuSE 13.1. Since these are hosts which have a lot of different users logging in, I'm somewhat concerned about the consequences. In http://nwrickert2.wordpress.com/2013/12/16/systemd-user-manager-ecryptfs-and... I read, that pam-config -d --systemd might be a workaround, but has side-effects. If anyone here knows the list of side-effects, I'd be glad. As far as I understand, systemd --user is started via pam at logins/ssh-access. Which mechanism is supposed to stop these processes after a logout? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c13 --- Comment #13 from Dr. Werner Fink <werner@suse.com> 2014-04-09 08:19:46 UTC --- (In reply to comment #12) Guess: you have not tested http://download.opensuse.org/repositories/Base:/System/openSUSE_13.1/ ... have you? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c14 --- Comment #14 from Achim Mildenberger <admin@fph.physik.uni-karlsruhe.de> 2014-04-09 09:55:32 UTC --- Thank you very much, Werner! Upgrading to systemd-210-619.1.x86_64.rpm systemd-sysvinit-210-619.1.x86_64.rpm from your repository helps a lot. As it seems, there is still a (smaller) issue: systemd --user (sd-pam) remain if there is an open mount (e.g. a USB-stick). Maybe this is being discussed here: https://bugs.freedesktop.org/show_bug.cgi?id=70214 Anyway, are you planning to release an update of systemd for 13.1? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c15 --- Comment #15 from Dr. Werner Fink <werner@suse.com> 2014-04-09 10:12:46 UTC --- (In reply to comment #14)
Anyway, are you planning to release an update of systemd for 13.1?
I've burned my fingers with such updates -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c16 --- Comment #16 from Drazenko Djuricic <djuricicd@gawnet.ch> 2014-04-27 10:09:28 UTC --- (In reply to comment #15)
(In reply to comment #14)
Anyway, are you planning to release an update of systemd for 13.1?
I've burned my fingers with such updates
Sorry if I ask ... but what will happen now? Will this annoying bug ever be fixed in 13.1? Or can we expect a fix in 13.2? Regards. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c17 --- Comment #17 from Stakanov Schufter <stakanov@freenet.de> 2014-04-27 11:28:38 UTC --- Well as far as the needinfo is concerned, I will give the info about the 4 of May. It was not possible before. What about systemd, if I well understand these updates are quite tricky as they involve the need for a good testing. Maybe Werner made a patch available for tumbleweed or it is in factory. I would expect that for the next edition it will be fixed. A bit that is also my fault, I do not have the possibility to use a testing machine and the testing I did before already "killed" one installation (not badly but at the time it was some work). So I will give info about the first week of may (and will do so ASAP promised). Maybe you may then try to install the patch from the repo on your machine if you dare. Or if the testing is OK for you, you may put the repo in your list and try and report back here. They more people try the better it is. Cheers. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c18 --- Comment #18 from Dr. Werner Fink <werner@suse.com> 2014-04-28 13:06:20 UTC --- (In reply to comment #17) I do not find the time to port all those changes back to 13.1 as this not only requires a lot of backporting but also a lot of testing andin fact I can not test all those fixes as I do not have all the test scenarios around. Nevertheless you're welcome to test out http://download.opensuse.org/repositories/Base:/System/openSUSE_13.1/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c19 --- Comment #19 from Achim Mildenberger <admin@fph.physik.uni-karlsruhe.de> 2014-04-28 13:55:20 UTC --- If I may add this statement: In my view, it's a pity that there is no update for 13.1, especially since 13.1 is planned to be a release with long-term support. Your version (comment #14, systemd-210-619.1.x86_64.rpm, from sometime in April 2014) is running fine here on 34 desktops. Up to know I didn't recognize any issues. It looks like the version maintainend in http://download.opensuse.org/repositories/Base:/System/openSUSE_13.1/ is constantly being upgraded. Nevertheless, as far as I understand now, the aim of this effort is not to get a generally released patch? Of course, I have to admit, I can't really estimate the risks of a systemd update... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c20 --- Comment #20 from Dr. Werner Fink <werner@suse.com> 2014-04-28 14:12:43 UTC --- (In reply to comment #19) One major problem is that in fact there are several other packages which sould also updated if systemd will be updated. E.g. multipath-tools and many others. It is perfect for you that 34 desktops are running but I had burned my fingers in past with systemd updates (compare with bug #854884) and I'm aware that not all users are able to debug such problems into its fully deep as they are not software engineers and/or familiar with how to do software engineering. Indeed some of the bug reports requires a crystal ball and a lot of time from my side and both I do not have :( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- OS/Version|Other |openSUSE 13.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c21 Stakanov Schufter <stakanov@freenet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|stakanov@freenet.de | --- Comment #21 from Stakanov Schufter <stakanov@freenet.de> 2014-05-06 16:26:39 UTC --- Hello Werner, I have good news for you. Your work was (at least on a 32 bit with standard KDE system) absolutely fruitful. I did try to open several user, to use SUID, to log out from that user, not respecting the order of opening. De facto a few processes stay open for about 10-15 seconds after log out but after that magically close and the system is like you would expect it. No process of logged out user seems to stay open. The only adverse effect currently was a request to install by hand a dbus package with a higher version than that of the systemd repo. This resolved the conflict and the dbus patch of today installed smoothly. If I would have chosen the primary conflict solving proposed by yast I would have uninstalled 149 packages. So you may look on the last dbus patch to see if some dependency has to be adapted. I will now use the system extensively for about a week doing whatever comes to my mind may be shitty for systemd to handle. :-) After that I will report back a last time. My feeling: good, I think you made it. But to be dead sure, I wish to test further. What to say...I am delighted up to now. Kind regards, thank you and compliments. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c22 --- Comment #22 from Mischa Salle <mischa.salle@gmail.com> 2014-05-16 11:24:50 UTC --- I'm bitten by this same bug, for me it prevents a proper shutdown, resulting in a timeout after 1 min 30 sec (the timeout for user@1000.service). See also https://bugzilla.novell.com/show_bug.cgi?id=867069 and the long threads starting http://lists.freedesktop.org/archives/systemd-devel/2014-February/016727.htm... and http://lists.freedesktop.org/archives/systemd-devel/2013-December/015191.htm... I've now `fixed' it using the workaround of a ~/.kde4/shutdown script killing the systemd user instance but I really hope this will properly be fixed in 13.1. It's not an option for me to use too many add-on repositories. Best wishes, Mischa Salle -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=865337 Joschi Brauchle <joschibrauchle@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joschibrauchle@gmx.de --- Comment #23 from Joschi Brauchle <joschibrauchle@gmx.de> --- We are having the same problem at our institute in combination with NFSv4 and Kerberos mounts. The user mounts its home from an NFSv4 server via autofs. Unfortunately, due to systemd leaving an "(sd-pam)" process hanging around which accesses the user home even after user logout, the NFSv4 share cannot be unmounted. After a while, the user kerberos tickets for the nfsv4 mount expires and things are in a big mess, as the user is not even aware of the situation as he has logged out long before. The "(sd-pam)" processes and now inaccessible nfs4 mounts keep sticking around forever until the machine is rebooted. We currently refrain to automatically kill all "(sd-pam)" processes after user logout to prevent this scenario. Not nice... -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com