Yes, what i don't understand is why the Jobdefs don't work without a Client option. If Jobdefs can work for every job of every client, without putting the actual Clients on the Jobdefs option, why is there a Client option?
On Thu, 2006-08-03 at 12:18 +0800, Troy Daniels wrote: > Hi, > > > > Duarte Santos wrote: > > Hello, > > > > Is it needed to have 1 JobDefs for each Job? > > Why is there a "client" option in JobDefs, when i can map a JobDefs on > > each Job definition. > > > > Duarte Santos > > > > > > By definition, jobdefs is 'Job Defaults' and you set up defaults here > for all the jobs that reference it. > > You can have as few or as many as you want and/or need. > > You call it from your Job definition, and redefine any values that are > different from the defaults. Including the client option. > > This way you can keep your config simple by setting most settings in > your JobDef and just job specific settings in the Job. > > Hope this makes sense! > > Troy Daniels > Systems Administrator > iTouch Australia (Pty) Ltd. > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Mailscanner thanks transtec Computers for their support. ------------------------------------------------------------------------- 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
