chris job.fr | 21 Feb 2011 16:09
Picon

Unix : home directory

  Hello,

  Our users have two home directories : a local one (/home/user1) and
the "pam directory" (/pam/users1).  When a user goes on a unix
platform of the laboratory, he is automatically on the pam directory
(/pam/users1).
  Is it possible to do this thing : if the pam directory is
inaccessible, the user is automatically on their local directory
(/home/user1).

Thank you for your suggestion
Chris
--
chrisjob.fr <at> gmail.com
Guillaume Allegre | 21 Feb 2011 17:19
Picon
Favicon
Gravatar

Re: Unix : home directory

Le lun. 21 f�vr. 2011 à 16:09 +0100, chris job.fr a ecrit :
>   Hello,
> 
>   Our users have two home directories : a local one (/home/user1) and
> the "pam directory" (/pam/users1).  When a user goes on a unix
> platform of the laboratory, he is automatically on the pam directory
> (/pam/users1).
>   Is it possible to do this thing : if the pam directory is
> inaccessible, the user is automatically on their local directory
> (/home/user1).
> 

Maybe you could explain how (and when) the /pam/* directories 
are mounted, and which filesystem ? nfs...

A very basic solution would be to have each /pam/userN as a symbolic 
link on /home/userN, which would be the fallback. 
When automounting (?) is OK, it would be replaced by the real "shared" /pam/userN

--

-- 
 ° /\    Guillaume Allègre            Membre de l'April
  /~~\/\   Allegre.Guillaume <at> free.fr  Promouvoir et défendre le logiciel libre
 /   /~~\    tél. 04.76.63.26.99      http://www.april.org

_______________________________________________
Pam-list mailing list
Pam-list <at> redhat.com
https://www.redhat.com/mailman/listinfo/pam-list
chris job.fr | 21 Feb 2011 18:06
Picon

Re: Unix : home directory

The local directory is on the disl of the user's computer, but the pam
directory is a NFS file system.  The user can use differents computers
and can find his data everywhere (on the pam directory). But he can do
something confidentially on his own system (a local directory).
  Sometimes we have problem with the NFS storage and with this
solution (connection on the pam directory), the use can't connect
anywhere. The problem is on Unix.

  So the symbolic link is not the solution.

Thank you
Chris

2011/2/21 Guillaume Allegre <allegre.guillaume <at> free.fr>:
> Le lun. 21 f�vr. 2011 à 16:09 +0100, chris job.fr a ecrit :
>>   Hello,
>>
>>   Our users have two home directories : a local one (/home/user1) and
>> the "pam directory" (/pam/users1).  When a user goes on a unix
>> platform of the laboratory, he is automatically on the pam directory
>> (/pam/users1).
>>   Is it possible to do this thing : if the pam directory is
>> inaccessible, the user is automatically on their local directory
>> (/home/user1).
>>
>
> Maybe you could explain how (and when) the /pam/* directories
> are mounted, and which filesystem ? nfs...
>
>
(Continue reading)

Florian Lengyel | 21 Feb 2011 19:01
Picon

Re: Unix : home directory

What is the directory specified by

getent passwd user1

(however you manage users; e.g., /etc/passwd, LDAP, NIS, Samba AD to PAM sid to uid/gid translation with idmap_rid in /etc/samba/smb.conf etc)?

You may be able to do what you want with automount multimaps...


On Mon, Feb 21, 2011 at 12:06 PM, chris job.fr <chrisjob.fr <at> gmail.com> wrote:
The local directory is on the disl of the user's computer, but the pam
directory is a NFS file system.  The user can use differents computers
and can find his data everywhere (on the pam directory). But he can do
something confidentially on his own system (a local directory).
 Sometimes we have problem with the NFS storage and with this
solution (connection on the pam directory), the use can't connect
anywhere. The problem is on Unix.

 So the symbolic link is not the solution.

Thank you
Chris

2011/2/21 Guillaume Allegre <allegre.guillaume <at> free.fr>:
> Le lun. 21 f�vr. 2011 à 16:09 +0100, chris job.fr a ecrit :
>>   Hello,
>>
>>   Our users have two home directories : a local one (/home/user1) and
>> the "pam directory" (/pam/users1).  When a user goes on a unix
>> platform of the laboratory, he is automatically on the pam directory
>> (/pam/users1).
>>   Is it possible to do this thing : if the pam directory is
>> inaccessible, the user is automatically on their local directory
>> (/home/user1).
>>
>
> Maybe you could explain how (and when) the /pam/* directories
> are mounted, and which filesystem ? nfs...
>
>
> A very basic solution would be to have each /pam/userN as a symbolic
> link on /home/userN, which would be the fallback.
> When automounting (?) is OK, it would be replaced by the real "shared" /pam/userN
>
>
> --
>  ° /\    Guillaume Allègre            Membre de l'April
>  /~~\/\   Allegre.Guillaume <at> free.fr  Promouvoir et défendre le logiciel libre
>  /   /~~\    tél. 04.76.63.26.99      http://www.april.org
>
> _______________________________________________
> Pam-list mailing list
> Pam-list <at> redhat.com
> https://www.redhat.com/mailman/listinfo/pam-list

_______________________________________________
Pam-list mailing list
Pam-list <at> redhat.com
https://www.redhat.com/mailman/listinfo/pam-list

_______________________________________________
Pam-list mailing list
Pam-list <at> redhat.com
https://www.redhat.com/mailman/listinfo/pam-list
akshar kanak | 3 Mar 2011 06:30
Picon

info regarding failure of modules

Dear Team
        When any PAM api (like pam_authenticate, pam_acct_mgmt etc
)fails . is it possible to get the information about which module has
actually failed  or matrix of oparation done on the module stack (Like
how each module operated and its status and its reasons for failure )
.

Thanks and regards
Akshar
Thorsten Kukuk | 3 Mar 2011 07:23
Picon

Re: info regarding failure of modules

On Thu, Mar 03, akshar kanak wrote:

> Dear Team
>         When any PAM api (like pam_authenticate, pam_acct_mgmt etc
> )fails . is it possible to get the information about which module has
> actually failed  or matrix of oparation done on the module stack (Like
> how each module operated and its status and its reasons for failure )
> .

Not from the PAM api. Most modules have a debug option, which
will print more informations to syslog.

  Thorsten

--

-- 
Thorsten Kukuk, Project Manager/Release Manager SLES
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
GF: Markus Rex, HRB 16746 (AG Nuernberg)
Palmer, Gerald | 3 Mar 2011 17:32

pam_env setting root PS1

it does not appear that you can use the "#" pound sign in any variable in the pam_env module. 
It looks like any pound is interpreted as the beginning of a comment.
 
As a result one cannot set the prompt string "PS1" for root to the "#"
_______________________________________________
Pam-list mailing list
Pam-list <at> redhat.com
https://www.redhat.com/mailman/listinfo/pam-list

Gmane