On 09/07/10 11:45, Steve Polyack wrote: > On 09/07/10 11:09, Eduardo Júnior wrote: >> So, reload command is sufficient and the jobs in execution will >> no be lost? >> >> Thanks, >> > Correct, running jobs will not be lost and their execution will not be > stopped when you use the reload command.
*USUALLY*. > However, keep in mind John's > comment about testing the config with 'bacula-dir -t' first - a config > error will result in the director crashing when you issue the reload > command. Past experience has shown that while a reload is *usually* safe, *multiple* reloads on the same running Director session are not always safe. Occasionally, a Director that has had a large number of reloads without being restarted (particularly reloads while jobs are running) will lose a buffer or a memory pointer somewhere and crash. So, just out of prudence, if you have to reload more than once or twice, it's a good plan to restart your Director at the next opportunity you get to do so cleanly. -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 [email protected] [email protected] [email protected] Renaissance Man, Unix ronin, Perl hacker, Free Stater It's not the years, it's the mileage. ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
