Request to change how warn/localmessages/messages logs are saved

[m0rbo]

This request is to ask that the messages log, /var/log/messages, is saved in full and standalone and to not be combined in the "messages.txt" file with /var/log/warn and /var/log/localmessages. I think it makes more sense to move warn and localmessages to a different file, or save them each in their own file.

I'm ok with keeping a combined file that includes warn and localmessages, but often we ignore those files because generally those log entries are also included in /var/log/messages.

I see the supportconfig logic checks if the size of the messages file is greater than 26M and if so, only grab 200,000 lines of that file, which seems sufficient at this time.

It's difficult/cumbersome/incommodious/time-consuming to jump down to the messages part of the combined file, having them as separate file would save time while reviewing logs.

[tuttipazzo]

Not all customer think to generate supportconfig when an issue occurs so you may not see any errors (depending on the problem) and you have to waste time looking through tail -1000 version of messages file only to ask for the whole file. Meanwhile they are breathing down you neck for resolution/status update.

[Thr3d]

I support the idea of moving warn/localmessages out of messages.txt to their own file. Over the years I have rarely looked at those and mostly find myself deleting them from messages.txt for my cases.

[roger-whittaker]

I would also welcome this change for the reasons given by others and also because if I grep for a string in messages.txt I will often get the same message twice: once from warn and once from messages.