Dan Nelson wrote:
/bin/ls is linked statically, which means it only knows about compat,
files, nis, and dns; you can build a dynamic one, or step up and write
Ahh, thank you for this explanation. :-)
There are other strange things with -CURRENT and LDAP-setup: I have
jdk13 running on the machine
In the last episode (Oct 08), Uwe Laverenz said:
> [EMAIL PROTECTED] wrote:
> >Nevertheless the problem with file attributes persists.
>
> I have the same problem here. I guess that 'ls' doesn't care about
> nsswitch?!
/bin/ls is linked statically, which means it only knows about compat,
files, n
[EMAIL PROTECTED] wrote:
Nevertheless the problem with file attributes persists.
I have the same problem here. I guess that 'ls' doesn't care about
nsswitch?!
cu,
Uwe
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-
Since nobody responded I will do it myself :-).
Further investigation shown that the problem with connecting via ssh was only with the
Putty client.
Normal command line ssh from another unix host worked fine. The Google search found
one message targeting this problem.
The solution is to use ssh2
Hi,
I just suceeded to install and configure pam_ldap authentication on my
5.1Release box. Everything seems to work fine (ftp, telnet, samba, ...)
except for ssh.
Any attempt to login (as user whose account is defined in the LDAP
directory) from a remote host using ssh end up with the error me
