I was seeing the issue similarly last night. I may need to create a command line entry dialog box for prompt is what I was thinking.
Dirk On Sat, 2009-07-18 at 18:51 +0200, Kern Sibbald wrote: > Hello Dirk, > > I have analysed the problem of bat getting confused when the Director sends > an > unexpected PROMPT -- in fact, as far as I can see, it is probably any prompt > that is not the MAIN_PROMPT or a PROMPT after a START SELECT. > > In most cases, such as a START SELECT, you go into a special dialog handler, > which then reads all the input lines, and responds to the Directory. > > In the case of a PROMPT not following a START SELECT, bat is in a wait state > and when the user enters a response in the command line a notification will > come in and ultimately call input_line(), which wll call consoleCommand() in > the Pager, and that is where everything goes wrong, because consoleCommand() > will then choose any available conn connection to send the user's response, > rather than the conn that was where the original PROMPT originated. Bottom > line: a prompt request comes in on conn=0 and the user's response will be > sent out on conn=1, which of course does not work. > > So, either we need some default handler for a PROMPT, or some other solution, > and unfortunately, I don't know how the m_conn stuff is handled well enough > to work out a solution. > > Best regards, > > Kern ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
