Bug#319814: use of DBD CNID backend fails with error Unable to get stamp value from CNID backend

2005-07-25 Thread Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25-07-2005 01:36, Tim Miller Dyck wrote: Package: netatalk Version: 2.0.2-3 Dear netatalk maintainers: I am having a problem using netatalk with a DBD (transactional) backend. The CNID database is not getting created properly and the

Bug#319814: use of DBD CNID backend fails with error Unable to get stamp value from CNID backend

2005-07-25 Thread Tim Miller Dyck
Dear Jonas: Thank you for that tip! That was my problem. I added the following lines to /etc/init.d/netatalk on my system to do this automatically: if [ $CNID_METAD_RUN = yes -a -x /usr/sbin/cnid_metad ]; then /usr/sbin/cnid_metad echo -n cnid_metad fi ...

Bug#319814: use of DBD CNID backend fails with error Unable to get stamp value from CNID backend

2005-07-25 Thread Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25-07-2005 16:34, Tim Miller Dyck wrote: Dear Jonas: Thank you for that tip! That was my problem. I added the following lines to /etc/init.d/netatalk on my system to do this automatically: if [ $CNID_METAD_RUN = yes -a -x

Bug#319814: use of DBD CNID backend fails with error Unable to get stamp value from CNID backend

2005-07-24 Thread Tim Miller Dyck
Package: netatalk Version: 2.0.2-3 Dear netatalk maintainers: I am having a problem using netatalk with a DBD (transactional) backend. The CNID database is not getting created properly and the afpd server is unable to access it. The default CDB backend works fine. Creating the database