You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a non-root user who launched rhproxy in my login shell, I can currently only run rhproxy while I'm the login shell is running. The service gets killed soon after I log out.
Please enhance the rhproxy installation by allowing the service to survive logging out. To achieve that, Alberto mentioned the following command:
$ loginctl enable-linger
The text was updated successfully, but these errors were encountered:
I just created a simple user (not a member of wheel) and run without the user I got the following:
[aab@aab-dsc ~]$ loginctl enable-linger
==== AUTHENTICATING FOR org.freedesktop.login1.set-user-linger ====
Authentication is required to run programs as a non-logged-in user.
Multiple identities can be used for authentication:
1. Alberto Bellotti (abellotti)
2. Discovery Admin (dscadmin)
Choose identity to authenticate as (1-2):
Whereas running it with the user worked fine (and not needing sudo either).
actually loginctl enable-linger and loginctl disable-linger also work without $USER if logging in directly to the box. If one su - to the user from another account, the $USER is needed. So specifying $USER would handle both cases.
As a non-root user who launched rhproxy in my login shell, I can currently only run rhproxy while I'm the login shell is running. The service gets killed soon after I log out.
Please enhance the rhproxy installation by allowing the service to survive logging out. To achieve that, Alberto mentioned the following command:
The text was updated successfully, but these errors were encountered: