[opensuse] What is /run/user/<user-id> directory and how to make sure it's created?
Hello: I would like to help users by logging in through VNC session. Since the user doesn't have strong password I don't allow to log in the user through ssh. Instead I log in in my name and then su to that user and start the vncserver. Briefly: ssh <user1> target.machine user1@target> su user2 user2@target> vncserver :1 So far it's OK. When I try to connect to the vncserver I get only a blank window with an error message: Call to lnusertemp failed (temporary directories full?). Check your installation. VNC log file shows: Error: cannot create directory "/run/user/1002": Permission denied startkde: Call to lnusertemp failed (temporary directories full?). Check your installation. 1002 is the UID of user2. I guess as I su-ed to user 2 from user1 login, the directory hasn't been created. How can I fix this one? If the given user is logged in locally this problem doesn't appear, but I need to use the VNC session even if the user is logged out. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Fri, 23 Jan 2015 19:02:18 +0100 (CET)
Istvan Gabor
Hello:
I would like to help users by logging in through VNC session. Since the user doesn't have strong password I don't allow to log in the user through ssh. Instead I log in in my name and then su to that user and start the vncserver. Briefly:
ssh <user1> target.machine
user1@target> su user2 user2@target> vncserver :1
So far it's OK. When I try to connect to the vncserver I get only a blank window with an error message:
Call to lnusertemp failed (temporary directories full?). Check your installation.
VNC log file shows:
Error: cannot create directory "/run/user/1002": Permission denied startkde: Call to lnusertemp failed (temporary directories full?). Check your installation.
1002 is the UID of user2. I guess as I su-ed to user 2 from user1 login, the directory hasn't been created. How can I fix this one? If the given user is logged in locally this problem doesn't appear, but I need to use the VNC session even if the user is logged out.
/run/user/<uid> is intended to be temporary user directory with lifetime of "at least one user session exists". It is created by logind when first session is registered by pam_systemd. Now, plain "su" does not create user session, so it cannot work. "su -l" /may/ work. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov írta:
В Fri, 23 Jan 2015 19:02:18 +0100 (CET) Istvan Gabor пишет:
Hello:
I would like to help users by logging in through VNC session. Since the user doesn't have strong password I don't allow to log in the user through ssh. Instead I log in in my name and then su to that user and start the vncserver. Briefly:
ssh <user1> target.machine
user1@target> su user2 user2@target> vncserver :1
So far it's OK. When I try to connect to the vncserver I get only a blank window with an error message:
Call to lnusertemp failed (temporary directories full?). Check your installation.
VNC log file shows:
Error: cannot create directory "/run/user/1002": Permission denied startkde: Call to lnusertemp failed (temporary directories full?). Check your installation.
1002 is the UID of user2. I guess as I su-ed to user 2 from user1 login, the directory hasn't been created. How can I fix this one? If the given user is logged in locally this problem doesn't appear, but I need to use the VNC session even if the user is logged out.
/run/user/<uid> is intended to be temporary user directory with lifetime of "at least one user session exists". It is created by logind when first session is registered by pam_systemd.
Now, plain "su" does not create user session, so it cannot work. "su -l" /may/ work.
Thanks Andrei. Unfortunately su -l doesn't make a logion session in this context, doesn't work. If I remember correctly in previous openSUSE versions (11.x 12.2) I could use the above described method to log in and use the VNC session as a su-ed user. In openSUSE 13.2 the behavior is different. Other method to try? (This can be a show-stopper for oS13.2). Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Fri, 23 Jan 2015 19:49:57 +0100 (CET)
Istvan Gabor
Andrei Borzenkov írta:
В Fri, 23 Jan 2015 19:02:18 +0100 (CET) Istvan Gabor пишет:
Hello:
I would like to help users by logging in through VNC session. Since the user doesn't have strong password I don't allow to log in the user through ssh. Instead I log in in my name and then su to that user and start the vncserver. Briefly:
ssh <user1> target.machine
user1@target> su user2 user2@target> vncserver :1
So far it's OK. When I try to connect to the vncserver I get only a blank window with an error message:
Call to lnusertemp failed (temporary directories full?). Check your installation.
VNC log file shows:
Error: cannot create directory "/run/user/1002": Permission denied startkde: Call to lnusertemp failed (temporary directories full?). Check your installation.
1002 is the UID of user2. I guess as I su-ed to user 2 from user1 login, the directory hasn't been created. How can I fix this one? If the given user is logged in locally this problem doesn't appear, but I need to use the VNC session even if the user is logged out.
/run/user/<uid> is intended to be temporary user directory with lifetime of "at least one user session exists". It is created by logind when first session is registered by pam_systemd.
Now, plain "su" does not create user session, so it cannot work. "su -l" /may/ work.
Thanks Andrei. Unfortunately su -l doesn't make a logion session in this context, doesn't work.
If I remember correctly in previous openSUSE versions (11.x 12.2) I could use the above described method to log in and use the VNC session as a su-ed user. In openSUSE 13.2 the behavior is different. Other method to try? (This can be a show-stopper for oS13.2).
Try ssh-ing as user instead of su-ing to it. This will give you full login session. You can setup public key authentication so you do not need to know user password (and setup public key to execute specific user command - although I do not know how well it plays together with systemd session concept). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov írta:
В Fri, 23 Jan 2015 19:49:57 +0100 (CET) Istvan Gabor пишет:
Andrei Borzenkov írta:
В Fri, 23 Jan 2015 19:02:18 +0100 (CET) Istvan Gabor пишет:
Hello:
I would like to help users by logging in through VNC session. Since the user doesn't have strong password I don't allow to log in the user through ssh. Instead I log in in my name and then su to that user and start the vncserver. Briefly:
ssh <user1> target.machine
user1@target> su user2 user2@target> vncserver :1
So far it's OK. When I try to connect to the vncserver I get only a blank window with an error message:
Call to lnusertemp failed (temporary directories full?). Check your installation.
VNC log file shows:
Error: cannot create directory "/run/user/1002": Permission denied startkde: Call to lnusertemp failed (temporary directories full?). Check your installation.
1002 is the UID of user2. I guess as I su-ed to user 2 from user1 login, the directory hasn't been created. How can I fix this one? If the given user is logged in locally this problem doesn't appear, but I need to use the VNC session even if the user is logged out.
/run/user/<uid> is intended to be temporary user directory with lifetime of "at least one user session exists". It is created by logind when first session is registered by pam_systemd.
Now, plain "su" does not create user session, so it cannot work. "su -l" /may/ work.
Thanks Andrei. Unfortunately su -l doesn't make a logion session in this context, doesn't work.
If I remember correctly in previous openSUSE versions (11.x 12.2) I could use the above described method to log in and use the VNC session as a su-ed user. In openSUSE 13.2 the behavior is different. Other method to try? (This can be a show-stopper for oS13.2).
Try ssh-ing as user instead of su-ing to it. This will give you full login session. You can setup public key authentication so you do not need to know user password (and setup public key to execute specific user command - although I do not know how well it plays together with systemd session concept).
This is very bad news. The method you suggest is not a real option for me. If using these keys I have to carry/copy the keys to the different sites and if there is a change it becomes useless. The method I've described worked for me for long time. It's a pity it doesn't work anymore, I'd say it a regression. Such things are very frustrating. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Fri, 23 Jan 2015 21:37:26 +0100 (CET)
Istvan Gabor
Andrei Borzenkov írta:
В Fri, 23 Jan 2015 19:49:57 +0100 (CET) Istvan Gabor пишет:
Andrei Borzenkov írta:
В Fri, 23 Jan 2015 19:02:18 +0100 (CET) Istvan Gabor пишет:
Hello:
I would like to help users by logging in through VNC session. Since the user doesn't have strong password I don't allow to log in the user through ssh. Instead I log in in my name and then su to that user and start the vncserver. Briefly:
ssh <user1> target.machine
user1@target> su user2 user2@target> vncserver :1
So far it's OK. When I try to connect to the vncserver I get only a blank window with an error message:
Call to lnusertemp failed (temporary directories full?). Check your installation.
VNC log file shows:
Error: cannot create directory "/run/user/1002": Permission denied startkde: Call to lnusertemp failed (temporary directories full?). Check your installation.
1002 is the UID of user2. I guess as I su-ed to user 2 from user1 login, the directory hasn't been created. How can I fix this one? If the given user is logged in locally this problem doesn't appear, but I need to use the VNC session even if the user is logged out.
/run/user/<uid> is intended to be temporary user directory with lifetime of "at least one user session exists". It is created by logind when first session is registered by pam_systemd.
Now, plain "su" does not create user session, so it cannot work. "su -l" /may/ work.
Thanks Andrei. Unfortunately su -l doesn't make a logion session in this context, doesn't work.
If I remember correctly in previous openSUSE versions (11.x 12.2) I could use the above described method to log in and use the VNC session as a su-ed user. In openSUSE 13.2 the behavior is different. Other method to try? (This can be a show-stopper for oS13.2).
Try ssh-ing as user instead of su-ing to it. This will give you full login session. You can setup public key authentication so you do not need to know user password (and setup public key to execute specific user command - although I do not know how well it plays together with systemd session concept).
This is very bad news. The method you suggest is not a real option for me. If using these keys I have to carry/copy the keys to the different sites and if there is a change it becomes useless. The method I've described worked for me for long time. It's a pity it doesn't work anymore, I'd say it a regression. Such things are very frustrating.
May be I was not clear. You log into remote system and instead of "su" do "ssh" to local host. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov > írta:
В Fri, 23 Jan 2015 21:37:26 +0100 (CET) Istvan Gabor пишет:
Andrei Borzenkov írta:
В Fri, 23 Jan 2015 19:49:57 +0100 (CET) Istvan Gabor пишет:
Andrei Borzenkov írta:
В Fri, 23 Jan 2015 19:02:18 +0100 (CET) Istvan Gabor пишет:
Hello:
I would like to help users by logging in through VNC session. Since the user doesn't have strong password I don't allow to log in the user through ssh. Instead I log in in my name and then su to that user and start the vncserver. Briefly:
ssh <user1> target.machine
user1@target> su user2 user2@target> vncserver :1
So far it's OK. When I try to connect to the vncserver I get only a blank window with an error message:
Call to lnusertemp failed (temporary directories full?). Check your installation.
VNC log file shows:
Error: cannot create directory "/run/user/1002": Permission denied startkde: Call to lnusertemp failed (temporary directories full?). Check your installation.
1002 is the UID of user2. I guess as I su-ed to user 2 from user1 login, the directory hasn't been created. How can I fix this one? If the given user is logged in locally this problem doesn't appear, but I need to use the VNC session even if the user is logged out.
/run/user/<uid> is intended to be temporary user directory with lifetime of "at least one user session exists". It is created by logind when first session is registered by pam_systemd.
Now, plain "su" does not create user session, so it cannot work. "su -l" /may/ work.
Thanks Andrei. Unfortunately su -l doesn't make a logion session in this context, doesn't work.
If I remember correctly in previous openSUSE versions (11.x 12.2) I could use the above described method to log in and use the VNC session as a su-ed user. In openSUSE 13.2 the behavior is different. Other method to try? (This can be a show-stopper for oS13.2).
Try ssh-ing as user instead of su-ing to it. This will give you full login session. You can setup public key authentication so you do not need to know user password (and setup public key to execute specific user command - although I do not know how well it plays together with systemd session concept).
This is very bad news. The method you suggest is not a real option for me. If using these keys I have to carry/copy the keys to the different sites and if there is a change it becomes useless. The method I've described worked for me for long time. It's a pity it doesn't work anymore, I'd say it a regression. Such things are very frustrating.
May be I was not clear. You log into remote system and instead of "su" do "ssh" to local host.
Yes, I really haven't understood correctly. What you suggest (ssh-ing to localhost) works. Thanks for the tip! A looked into this /run/dir directory stuff and found it is defined as XDG_RUNTIME_DIR. Interestingely, in openSUSE 12.2 and even in 13.1 this directory is made permanent. After the user's logout it's not deleted. While in oS 13.2 it is only temporary and is deleted after logout. I wonder what rule/setting makes the difference. Thank you again, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-23 19:02, Istvan Gabor wrote:
Hello:
I would like to help users by logging in through VNC session. Since the user doesn't have strong password I don't allow to log in the user through ssh. Instead I log in in my name and then su to that user and start the vncserver. Briefly:
ssh <user1> target.machine
user1@target> su user2
As a rule, I never do "su", but "su -". And on some circumstances, as Andrei said, "ssh user@localhost", works when su failed. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
"Carlos E. R."
On 2015-01-23 19:02, Istvan Gabor wrote:
Hello:
I would like to help users by logging in through VNC session. Since the user doesn't have strong password I don't allow to log in the user through ssh. Instead I log in in my name and then su to that user and start the vncserver. Briefly:
ssh <user1> target.machine
user1@target> su user2
As a rule, I never do "su", but "su -". And on some circumstances, as Andrei said, "ssh user@localhost", works when su failed.
su -l does not create the /run/user/$UID directory, ssh to localhost does. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Andrei Borzenkov -
Carlos E. R. -
Istvan Gabor