search for: messaging_dgm_create_lockfil

..., strerror(ret))); goto fail_unlink; } And the output of ./smbd -i -d 2 is: lock file name is: /opt/local/samba4/var/cache/lck/7561 unique is 0 unique_len is: -1 messaging_dgm_lockfile_create: ftruncate failed: Invalid argument messaging_dgm_init: messaging_dgm_create_lockfile failed: Invalid argument messaging_dgm_init failed: Invalid argument Tom Schulz Applied Dynamics Intl. schulz at adi.com

...4.2.0rc4 will run on a Solaris 10 i386 system. After getting it to build, startup fails. Starting it up as smbd -i -d 10 The output indicates that everything is starting normally until the following is output: messaging_dgm_lockfile_create: ftruncate failed: Invalid argument messaging_dgm_init: messaging_dgm_create_lockfile failed: Invalid argument messaging_dgm_init failed: Invalid argument And then it exits. Where do I start to look to find the problem? Tom Schulz Applied Dynamics Intl. schulz at adi.com

...0 ip=2001:67c:248c:233::b bcast= netmask=ffff:ffff:ffff:ffff:: added interface eth0 ip=10.10.0.11 bcast=10.10.0.255 netmask=255.255.255.0 invalid ownership on directory /var/cache/samba/lck messaging_dgm_lockfile_create: Could not create lock directory: No such file or directory messaging_dgm_init: messaging_dgm_create_lockfile failed: No such file or directory messaging_dgm_init failed: No such file or directory Enter richard's password: Connecting to 10.10.0.12 at port 445 Doing spnego session setup (blob length=96) got OID=1.2.840.48018.1.2.2 got OID=1.2.840.113554.1.2.2 got OID=1.3.6.1.4.1.311.2.2.10 got principa...