Hello Nico,

thanks for your effort.

> Do not confuse /var/idmap/... with /var/run/idmap/...  The first is on
> persistent storage, the other is on tmpfs.  In this case you say the
> log mentions /var/idmap/idmap.db -- removing /var/run/idmap/idmap.db
> isn't going to help.  See below.


> This is clue number three.  This error comes from SQLite2, and it
> indicates that the library was unable to create a temporary file in
> that same directory (IIUC).  Note that the real problem is the
> inability to create a file, not anything to do with the database
> itself being corrupted -- the error seems a bit misleading.  Was
> /var/idmap read-only at the time that the idmap service started?  

Thanks. I don't realize, that the problems comes from SQLite, and not from the 
idmap daemon.
I don't know if the idmap service was unable to write to /var/idmap because of 
an read-only directory.
As I can see, when I try to start the daemon, the directory ist writeable. I 
have temporarily changed the 
permissions to 777, but this change nothing.

> What build of Solaris are you running?

-bash-4.0$ uname -a
SunOS tom 5.11 snv_151a i86pc i386 i86pc


cifs-discuss mailing list

Reply via email to