From: "Stef Walter" <stefw(a)redhat.com>
To: cockpit-devel(a)lists.fedorahosted.org
Sent: Tuesday, February 25, 2014 3:47:40 AM
Subject: Re: More basic newbie questions
On 25.02.2014 09:29, Marius Vollmer wrote:
> Mark Constable <markc(a)renta.net> writes:
>
>> Okay so I guess if I ramble on about my Archlinux attempts then it won't
>> be dismissed out of hand.
>
> Definitely not! :-)
>
>> A user called "irtimmer" has submitted a storaged
>> source package to the Archlinuxs AUR repository and I ended up maintaining
>> the cockpit-git package. Archlinux currently uses systemd v209 by default.
>>
>>
https://aur.archlinux.org/packages/storaged
>>
https://aur.archlinux.org/packages/cockpit-git
>
> Oho, cool! But please don't advertise these two packages as 'stable'
or
> 'useable' just yet...
>
>> FWIW cockpitd and cockpit-ws seem to run but when I browse to
>>
https://localhost:21064/
>> I can't login, most likely because of this...
>>
>> Feb 25 17:49:21 tosh cockpit-ws[6824]: PAM unable to
>> dlopen(/usr/lib/security/pam_sepermit.so):
>> /usr/lib/security/pam_sepermit.so: cannot open shared object file: No
>> such file or directory
>
> Cockpit has its own PAM module, and you need to adjust it for your
> distribution. I think there is no good way around this, or is there?
Marius is right, but in the interest of clarity, this is not a 'PAM
module' but a 'PAM config'. Carry on ...
Oh, something to do with pam ? I couldn't login to my laptop this morning...on the
gdm screen briefly flashed something about pam_nologin. Rebooted and was able to login.
Don't see anything interesting in syslog.
Bizarre/fun :-)