Re^2: Choosing a log level

Very good, thoughtful post (++). There's just one point which baffles:

needed but not necessary files

What should this convey? To me, "needed" pretty much implies "necessary" and vice-versa. If you could clear that up then you would have a great sequence of categories.

Comment on Re^2: Choosing a log level

Replies are listed 'Best First'.
Re^3: Choosing a log level by Discipulus (Canon) on Mar 29, 2017 at 08:46 UTC
well the words seem identical in their sense but what i meant was, for example, an output file that cannot be written. This might not be a fatal error: you may receive `ERROR: out.txt is in use and $0 cannot lock it` that is different from `FATAL cannot read the configuration you supplied even if it exists` So probably the best word is complementary instead of needed, thanks for the comment. L* There are no rules, there are no thumbs.. Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.	[reply] [d/l] [select]
Re^4: Choosing a log level by SuicideJunkie (Vicar) on Mar 30, 2017 at 15:07 UTC
I was pondering on this for a few minutes, and I might describe ERROR as "locally fatal" as compared to being "globally fatal" The current operation is impossible, but the application as a whole can continue operating.	[reply]


P is for Practical
	PerlMonks