Nalin Dahyabhai wrote:
> On Fri, Nov 30, 2001 at 11:33:45AM +0100, Heinrich Rebehn wrote:
>
>>Accidently, when i did a simple "ldapsearch" on the server i noticed that the
>>automountInfromation entry was:
>>
>> automountInformation:: Oi9kZXYvaGRhMQ==
>>
>>This is because the entry starts with a colon and is therefore represented in
>>base64 notation. You normally don't run into this problem since usually the
>>entry starts with "-fstype=...", but i left it out because i suspected problems
>>with it. After putting "-fstype=auto" in front of it, all was fine:-)
>>
>>I don't know if this behaviour is a bug or a feature, but I would definitely
>>prefer an error message over a frozen machine!
>>
>
> The base64 encoding is performed for you by ldapsearch -- the
> LDAP lookup module actually gets ":/dev/hda1" as the value for
> the attribute, so it doesn't need to decode the result.
I had a look into the openldap database file and it also contained the encoded
information, so i do not think that ldapsearch performs any encoding.
Anyway, is there any way to have autofs run in the foreground an output its
error messages to stdout, so i can see what autofs is really trying to mount?
There's nothing written into syslog.
>
> Sorry, but I think the problem you experienced lies elsewhere.
>
> Nalin
>
--
Heinrich Rebehn
"Have disk - will travel"
University of Bremen
Physics / Electrical and Electronics Engineering
- Department of Telecommunications -
E-mail: mailto:[EMAIL PROTECTED]
Phone : +49/421/218-4664
Fax : -3341
