>>>>> On Mon, 25 Jul 2022 15:50:15 +0000, Bill Arlofski said: > > On Monday, July 25th, 2022 at 08:54, Martin Simmons <mar...@lispworks.com>= > wrote: > > > > You could try running bacula-fd with debugging output. Unfortunately, > > it doesn't include timestamps, but you can do it like this: > > Hey Martin, Not sure if this is recent or not, but: > ----8<---- > $ /opt/comm-bacula/sbin/bacula-fd -? > Copyright (C) 2000-2022 Kern Sibbald. > > Version: 13.0.0 (04 July 2022) > > Usage: bacula-fd [-f -s] [-c config_file] [-d debug_level] > -c <file> use <file> as configuration file > -d <n>[,<tags>] set debug level to <nn>, debug tags to <tags> > > -dt print a timestamp in debug output <--= > -- TimeStamps > > -f run in foreground (for debugging) > -g groupid > -k keep readall capabilities > -m print kaboom output (for debugging) > -P do not create pid file > -s no signals (for debugging) > -t test configuration file and exit > -T set trace on > -u userid > -v verbose user messages > -? print this message. > ----8<----
Thanks, I didn't know that. So this will be simpler: bacula-fd -dt -d50,scheduler -f -v ...your normal bacula-fd args... __Martin _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
