Bug 10126 - Option "--use-db=0" doesn't work in smbtad 1.2.6
Option "--use-db=0" doesn't work in smbtad 1.2.6
Status: ASSIGNED
Product: smbta
Classification: Unclassified
Component: smbtad
unspecified
x64 Linux
: P5 normal
: ---
Assigned To: Holger Hetterich
:
Depends on:
Blocks: 9538
  Show dependency treegraph
 
Reported: 2013-09-03 15:08 UTC by Alexander Prudnikov
Modified: 2014-04-08 12:33 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Prudnikov 2013-09-03 15:08:21 UTC
On Scientific Linux 6.1 I'm unsuccessfully trying to run smbtad 1.2.6 without DB. I've tried various flavors of the option, but nothing helped.
Below is my console output:

$ smbtad -U 0 -u -d 10
ERROR: drivername == NULL. Exiting.
Error connecting to the database.
please check syslog.

$ sudo grep smbta /var/log/messages
Sep  3 16:01:19 localhost kernel: smbtad[4674]: segfault at 2c ip 00007fb5f97b89cf sp 00007fff44983290 error 4 in libdbi.so.0.0.5[7fb5f97b3000+e000]
Sep  3 16:45:18 localhost kernel: smbtad[4841]: segfault at 2c ip 00007ff053f749cf sp 00007fffd4b9b780 error 4 in libdbi.so.0.0.5[7ff053f6f000+e000]
$ date
Tue Sep  3 17:04:18 CEST 2013

$ cat /etc/*-release
Scientific Linux release 6.1 (Carbon)
Comment 1 Holger Hetterich 2014-02-13 22:08:06 UTC
Ok, this is because smbtad doesn't write to the database with -U 0 but still runs the functions to connect to the DB at startup. This will block the 1.2.7 release tracker bug. Thanks for reporting Alexander a fix will is upcoming.
Comment 2 Holger Hetterich 2014-04-08 12:33:43 UTC
should be fixed with commit 77dd134f3e1dbe3ec2d80bdbf9ff8794a38a2ade to the devel branch, but I need to test it first..