Hello,
I would like to share with you my opinion about the jobstatus.
For me the job status 'T' both for jobs completed OK and for jobs
completed OK with warnings is quite OK. Everything depends on question
on which the jobstatus 'T' has to give an answer. I think that the
question here is: "Did all required data is backed up?" Answer: Yes
('T') or No ('E', 'e', 'f'...).
It is the same story as a story about a guy that needed to travel from
city A to city B. The goal in this travel is to come from city A to
city B. Let's imagine that the guy started travel and he had some
problems during travel but at the end he came to city B. Does the guy
achieve what he needed?
The same can be with the job. It doesn't matter how many times
something goes wrong. The important for me is that data is consistent
and everything what I needed is backed up.
In my opinion, adding new 'W' jobstatus will introduce many problems
in applications related to Bacula, like monitor software plugins
(Nagios...), web interfaces (including mine Baculum), scripts written
internally by admins, close source software that uses Bacula, ...etc.
What do you think about it?
Best regards.
Marcin Haba (gani)
On 30 September 2016 at 21:19, Hankins, Jonathan
<jhank...@homewood.k12.al.us> wrote:
> My jobs that complete "OK -- with warnings" with JobErrors > 0 always have
> JobStatus 'T'.
>
> I posted about this in 2012:
> https://www.mail-archive.com/bacula-devel@lists.sourceforge.net/msg07612.html
>
> No replies to that post. It looks like there was a commit in 2013:
> http://www.bacula.org/git/cgit.cgi/bacula/commit/?id=36b7c10b7fc787ab7b075f0b2521f7b20605ae6e
> that disabled this functionality, because there was code that needed to be
> updated to say (JS_Terminated || JS_Warning). Not sure if this was ever
> done? It looks like the DB gets 'T' stored as well, even though there are
> changelog comments indicating that the DB code has been updated to say
> "JobStatus IN ('T', 'W') where necessary.
>
> The committed code/comment above doesn't seem to be in bacula anymore, and I
> am wondering if JobStatus = 'W' is supposed to be implemented yet?
>
> It would be nice to be able to easily tell from the status command that a
> job had warnings, instead of having to look through the job logs.
>
> Is this something that could be implemented if I was able/willing to track
> down the necessary changes and make a patch?
>
> Thanks,
>
> -Jonathan Hankins
>
>
>
> This e-mail is intended only for the recipient and may contain confidential
> or proprietary information. If you are not the intended recipient, the
> review, distribution, duplication or retention of this message and its
> attachments is prohibited. Please notify the sender of this error immediately
> by reply e-mail, and permanently delete this message and its attachments in
> any form in which they may have been preserved.
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Bacula-devel mailing list
> Bacula-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-devel
>
--
"Greater love hath no man than this, that a man lay down his life for
his friends." Jesus Christ
"Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie
za przyjaciół swoich." Jezus Chrystus
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
