On 8/18/2018 6:46 PM, Prasad K. Dharmasena wrote:
> pam_afs_session "nopag" should be used in conjunction with USM.
>
>
> If no PAG is set, the 'two advantages' described
> in http://docs.openafs.org/Reference/1/pagsh.html go away.
> Specifically, this part "If the credential structure is
Am 19.08.2018 um 00:46 schrieb Prasad K. Dharmasena:
> So, we must pick our poison? A: live w/o '"systemctl --user" and all
> that stuff' or B: pam_afs_session with 'nopag'
Tried the latter (incl. re-install of dbus-user-session), but still
didn't get systemctl --user to work (after re-login
Am 17.08.2018 um 11:38 schrieb Gaja Sophie Peters:
> The main problem that we face at the moment is that there are TWO
> sessions opened, and (especially in "Ubuntu"-Session)
With "Ubuntu", you mean Gnome, I guess. KDE doesn't suffer from that
problem.
Bye...
Dirk
--
Dirk Heinrichs
GPG
On 8/17/2018 5:38 AM, Gaja Sophie Peters wrote:
> Am 17.08.2018 um 02:41 schrieb Prasad K. Dharmasena:
>> I've installed OpenAFS and pam-afs-session on Ubuntu 18.04 (bionic)
>> via (a)
>> vendor supplied packages, and (b) building from source (1.6.22.3). On
>> both
>> machines, logging in via gdm
Am 17.08.2018 um 02:41 schrieb Prasad K. Dharmasena:
I've installed OpenAFS and pam-afs-session on Ubuntu 18.04 (bionic) via (a)
vendor supplied packages, and (b) building from source (1.6.22.3). On both
machines, logging in via gdm doesn't get me a token.
Has anyone else seen this on
>
> pam_afs_session "nopag" should be used in conjunction with USM.
If no PAG is set, the 'two advantages' described in
http://docs.openafs.org/Reference/1/pagsh.html go away. Specifically, this
part "If the credential structure is identified by a UNIX UID rather than a
PAG, then the local
Am 18.08.2018 um 02:44 schrieb Prasad K. Dharmasena:
> Thanks for the pointer. I did 'dpkg -r dbus-user-session' and
> rebooted. Now 'pam-afs-session' does the right thing and obtains a
> token.
BTW: That's not pam-afs-session's fault. It did the right thing before
uninstalling
On 8/17/2018 8:44 PM, Prasad K. Dharmasena wrote:
> Thanks for the pointer. I did 'dpkg -r dbus-user-session' and
> rebooted. Now 'pam-afs-session' does the right thing and obtains a token.
>
> However, @poettering points out in the systemd/issues/7261 thread,
>
> Are there any
Thanks for the pointer. I did 'dpkg -r dbus-user-session' and rebooted.
Now 'pam-afs-session' does the right thing and obtains a token.
However, @poettering points out in the systemd/issues/7261 thread,
Are there any downsides?
>
> Yes, many. You turned off user service management entirely.
Hi,
try to remove the dbus-user-session package and look if it works.
Have a look at https://github.com/systemd/systemd/issues/7261
regards,
Andy
Am 17.08.2018 um 02:41 schrieb Prasad K. Dharmasena:
I've installed OpenAFS and pam-afs-session on Ubuntu 18.04 (bionic)
via (a) vendor supplied
I've installed OpenAFS and pam-afs-session on Ubuntu 18.04 (bionic) via (a)
vendor supplied packages, and (b) building from source (1.6.22.3). On both
machines, logging in via gdm doesn't get me a token. SSH in, however, does
obtain a token. For both gdm and ssh logins, the auth.log shows the
11 matches
Mail list logo
