On Wed, 2004-03-31 at 13:10, Matti Aarnio wrote: > > DBTYPE=gdbm > > DBEXT=.gdbm > > DBEXTtest=.gdbm > > > > [26087] modp_gdbm: cannot open ! (File open error) > > [26087] search_gdbm: cannot open ! (File open error) > > [26087] modp_gdbm: cannot open ! (File open error) > > [26087] search_gdbm: cannot open ! (File open error) > > Huh ? For me this one works.. > > Do run "zmailer newdb", and try it manually. This runs fine, .gdbm files are created and look OK. > There is also "trace db" that you can give to the router to > see when it calls database functions. Most miraculous: when run interactively, the router *WORKS*! At least "router crosser@...." gives correct response. When started as daemon, the result is (almost) the same: [26171] <19618198171.20040331162341@naumen.ru>: address: zopyrus-bounces@itconnection.ru [26171] <19618198171.20040331162341@naumen.ru>: file: 274518 <zopyrus-bounces@itconnection.ru> => <ilya@chronus.sovam.com> [26171] <19618198171.20040331162341@naumen.ru>: address: ilya@chronus.sovam.com [26171] modp_gdbm: cannot open ! (File open error) [26171] search_gdbm: cannot open ! (File open error) [26171] modp_gdbm: cannot open ! (File open error) [26171] search_gdbm: cannot open ! (File open error) [26171] <19618198171.20040331162341@naumen.ru>: address: ilya NDBM behavior is similar. Needless to say, DBTYPE=btree with Berkeley DB4 works fine. > If that does not help, perhaps 'make clean; make' is in order ? This I've done very first. I am learning, although slowly ;) Eugene ROUTEROPTIONS="-dkn 4" ROUTERDIRS=router1:router2:router3:router4 ROUTERNOTIFY=/var/spool/postoffice/.router.notify SMTPOPTIONS="-sve -l /var/log/zmailer/smtpserver" SCHEDULEROPTIONS="-l /var/log/zmailer/scheduler -S -H" SCHEDULERDIRHASH=2 ... DBTYPE=gdbm DBEXT=.gdbm DBEXTtest=.gdbm
This is a digitally signed message part