Hi all,
I'm just learning OpenLDAP; I'm hope it isn't a silly question.
I've mounted a OpenLDAP (version 2.4 in a FreeBSD 7.x platform) as account authentication server and all works fine. The clients are FreeBSD and GNU/Linux Debian. One problem I've found is related to loginShell field in posixAccount schema. It's because of when I was setting up the servers, I've configured /bin/csh as the default shell for the users
It's ok in FreeBSD clients (csh exists in default instalation), but you get an error when you try to authenticate a Debian client. ¿Why? Simple, the default shell in Debian is /bin/bash, not the defined /bin/csh. Currently, do you have two options to workaround this issue:
* install csh in Debian clients and assure that the binary path is /bin/csh * make a symlink /bin/csh which point to /bin/bash
At present, I've chosen the second option.
¿Is correct this workaround or maybe I don't know some other obvious method to get it?
I don't see you having any other options. If your clients all support a loginShell then as the admin you need to make sure that the shell is available on those platforms.
On 24/12/2008, Jordi Espasa Clofent jespasac@minibofh.org wrote:
Hi all,
I'm just learning OpenLDAP; I'm hope it isn't a silly question.
I've mounted a OpenLDAP (version 2.4 in a FreeBSD 7.x platform) as account authentication server and all works fine. The clients are FreeBSD and GNU/Linux Debian. One problem I've found is related to loginShell field in posixAccount schema. It's because of when I was setting up the servers, I've configured /bin/csh as the default shell for the users
It's ok in FreeBSD clients (csh exists in default instalation), but you get an error when you try to authenticate a Debian client. ¿Why? Simple, the default shell in Debian is /bin/bash, not the defined /bin/csh. Currently, do you have two options to workaround this issue:
- install csh in Debian clients and assure that the binary path is /bin/csh
- make a symlink /bin/csh which point to /bin/bash
At present, I've chosen the second option.
¿Is correct this workaround or maybe I don't know some other obvious method to get it?
-- Thanks, Jordi Espasa Clofent
openldap-technical@openldap.org