On Monday 27 February 2006 15:41, David Boyes wrote: > > > We can call it "jobuid" ? > > > > Yes. That is really nice. It is exactly what I was looking > > for. Thanks. > > How about "jobseq" or "jobserial"? My first reaction to "jobuid" is "the > uid that this job runs under".
Since very few users are likely to use this form of the Id, I don't have any problem calling it jobuid -- it is just a question of documentation. As far as I know, there is no such thing as a uid when dealing with a job. There is a Bacula uid, but it isn't related. ... ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
