Hello,
Starting a new thread for this subject.
I don't usually use bacularis to edit director or storage resources because
it strips out all the comments (baculum also does this, IIRC). I understand
why it does that, since it has to parse the configuration and by definition
the data after a # sign shouldn't be parsed. Still, this is the main thing
that prevents me from using bacularis to edit the director and storage
configuration files. Do you think there is any way to change the way
bacularis works to at least keep inline comments like this?
Job {
Name = "hostname" # This inline comment contains helpful information.
}
I do think that removing all comments from the configuration file is
actually a good feature in some contexts. Removing all the misc extra
default comments from the file is definitely helpful for an initial setup.
While those default comments are helpful when setting up bacula for the
first time, now that I'm deploying it in multiple places they're mostly
just in the way.
The comments that I leave in the configuration, though, I would very much
like to leave there. I know that a # character left by the developers looks
exactly the same as a # left by me, so I can understand that this is a
difficult problem to solve.
I thought that maybe we could use a special comment indicator in the file
to show bacularis that this is a comment to be left alone. One of the
problems is that bacula must also interpret whatever convention we select
as a comment so the configuration files remain parseable by bacula. Maybe
## could indicate 'keep this comment, and treat it as a comment' to
bacularis?
I understand that this is probably a big ask, and maybe far outside the
scope of what is reasonable for bacularis. Still, I thought I'd put it out
there and see what you think.
Regards,
Robert Gerber
402-237-8692
r...@craeon.net
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
