[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]

Re: commented lines *not* being ignored in cf files

Bryan Stansell bryan@conserver.com
Tue, 5 Mar 2019 19:35:56 +0000 (UTC)

The comments should work as you expect.  Is there a chance you’re doing a “#include” multiple times in your configs?  Or maybe that console name is occurring in multiple config files?  (perhaps you already hunted for that)

I have test files and seen many instances where comments were working fine.  Hopefully hunting for "c118.sjc002” across your config files or even “fill.sjc002” will illuminate things.


> On Mar 5, 2019, at 9:04 AM, Lonni J Friedman via users <users@conserver.com> wrote:
> Hello,
> I'm running conserver-8.2.2 on a Linux server.  I have a number of
> '.cf' files which define the configuration for devices in different
> parts of the network.  My config files are auto-generated, which
> occasionally results in commented entries being generated for some
> hosts, and then another un-commented entry further down in the same
> file for the same host.  The man page states that any line that starts
> with a '#' symbol (minus the quotes) is treated as a comment, and
> ignored.  However, I'm seeing evidence that its not being ignored at
> all, as I keep getting errors complaining about 'overridden'
> definitions:
> [Tue Mar  5 16:35:09 2019] conserver (3117): ERROR: console definition
> for `c118.sjc002.fill' overridden
> [/apps/nco-conserver/etc/config/fill.sjc002.cf:164]
> In /apps/nco-conserver/etc/config/fill.sjc002.cf this host has the
> following references (each on a separate line):
> # console                       c118.sjc002.fill { type ipmi; master
>; host 0; }
>  console                       c118.sjc002.fill { type ipmi; master
>; host; }
> Am I misunderstanding how comments should work?
> thanks
> _______________________________________________
> users mailing list
> users@conserver.com
> https://www.conserver.com/mailman/listinfo/users