Now that debugging is working (see my patch in other thread), I have some more details:
a1-fd: filed.c:238 filed: listening on port 9102 a1-fd: cram-md5.c:52 send: auth cram-md5 <[EMAIL PROTECTED]> ssl=0 a1-fd: cram-md5.c:68 Authenticate OK Q2thJ6+M/8ICB4g41H+BoB a1-fd: cram-md5.c:114 sending resp to challenge: CntUXwlul4/h5VxUEw+vIC a1-fd: authenticate.c:196 cram_get_auth failed for Storage daemon a1-fd: job.c:208 Quit command loop. Canceled=1 The following is for a successful "status": a1-fd: cram-md5.c:52 send: auth cram-md5 <[EMAIL PROTECTED]> ssl=0 a1-fd: cram-md5.c:68 Authenticate OK px9B380ZWk+Pz/x+zm+NSD a1-fd: cram-md5.c:114 sending resp to challenge: Qj+noC+iaX/Gd4/pCE/TjB I will keep reading code ... but any hints on the "cram_get_auth failed for Storage daemon"? I found a similar thread (but I am using Linux) at: http://sourceforge.net/mailarchive/forum.php?thread_id=6871117&forum_id=8833 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
