News for hackers. Stuff that matters.
Re:Everything that uses configuration files should report wh... by patmcc on Sunday June 25, 2023 @11:53PM (#36475577)
>>>Some programs use a "last occurrence wins" approach, while other programs (e.g. sshd) use a "first occurrence wins" approach.

A bunch of applications at my job use a config-loading library that will fail on startup if the same option is set to two different value (on different lines). It's certainly frustrating at times...but it's also prevented a huge amount of ambiguity.

Re:Everything that uses configuration files should report wh... by wizofaus on Sunday June 25, 2023 @11:57PM (#36475598)
That would actually be my preference TBH. Failing quickly at startup is usually far better than unpredictable behaviour later on, particularly if it's a long-running service. Though I've always thought that the behaviour of tools when launched interactively by the user, vs launched via an automated background process should probably be different - it may well be that if a user/administrator isn't aware it failed on machine startup the consequences of it not being running at all are worse than an ambiguous configuration setting.
Re:Everything that uses configuration files should report wh... by fbdab103 on Sunday June 25, 2023 @11:56PM (#36475588)
I am incredibly torn on if this is brilliant or would have me cursing the developer's name.