Make pam.d directory configurable

[yifanjiang]

Change according to the discussion in #2547 .

[matt335672]

Hi @yifanjiang

I'm out of time this week to have a good look at this, but after a quick glance this indeed looks like I was thinking of. This will definitely be useful to SuSE and any other distros that don't use /etc/pam.d.

A quick question- is there a good reason why you didn't add /pam.d to the pam config dir?

Speak soon.

[yifanjiang]

A quick question- is there a good reason why you didn't add /pam.d to the pam config dir?

Hi @matt335672 , thanks for looking into this. The reason was to make it a little more flexible for downstream packaging. While I took a second look, keeping a consistent lexical style with socketdir and sesmanruntimedir might be a better choice. So I update through the changes.

[metalefty]

I'm fine with this now. Waiting for @matt335672 's approval.

[matt335672]

I was all ready to approve this, then I read this useful comment from @thkukuk

I suggest the following amendment.

@yifanjiang - I apologise for messing you about like this. However, what we've now got something that should be able to support the use-cases mentioned by @thkuk

[matt335672]

Thanks for the quick edits @yifanjiang

Again, I apologise for the confusion.

[matt335672]

@metalefty - I think this should be backported to v0.9. Do you agree?

[metalefty]

@matt335672 Yes, it is definitely useful.