From: <bac...@li...> - 2005-06-14 15:32:58
|
The following bug has been CLOSED ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000339 ====================================================================== Reported By: shattered Assigned To: ====================================================================== Project: bacula Bug ID: 339 Category: Director Reproducibility: always Severity: minor Priority: normal Status: closed ====================================================================== Date Submitted: 06-10-2005 04:15 PDT Last Modified: 06-14-2005 08:32 PDT ====================================================================== Summary: list job=<job-name> does not work Description: The documentation suggests (on page 209) that console command "list job=<job-name>" will list records for a given job name. However, the code in db_list_job_records() does not handle this case. ====================================================================== ---------------------------------------------------------------------- kern - 06-14-2005 08:32 PDT ---------------------------------------------------------------------- I think the feature that you want to have is probably a good idea. However, the current code is not programmed for it, and you are confusing a Job, which is attached to a specific JobId and the name of a Job resource record. What you want is something that matches Name, not Job in the SQL database. The code as submitted will not work correctly. To make it work correctly, first, there needs to be some way to distinguish between the name of a Job resource (Name in the Job record) and the unique Job name (Job in the Job record) for a single Job. This needs to be done on the list job command. Second, I'm not sure if there is currently a way to list everything for a Job Name. A few other minor points: 1. It would be better to submit against the current CVS. 2. Your patch file doesn't seem to be quite standard. It would be best either to use "cvs diff -u" against the current CVS, or to do a diff -u old new 3. It would probably be simpler to simply submit the patch as an attachment to the bacula-devel list. I'm marking this as Not a bug, but would still like to see your fix, but with the above points in mind. If this is not clear, please ask on the bacula-devel list. Bug History Date Modified Username Field Change ====================================================================== 06-10-05 04:15 shattered New Bug 06-10-05 04:15 shattered File Added: bacula-list-job.patch 06-14-05 08:32 kern Bugnote Added: 0000962 06-14-05 08:32 kern Resolution open => not a bug 06-14-05 08:32 kern Status new => closed ====================================================================== |