On 3/8/18 12:07 PM, Darrick J. Wong wrote: > On Mon, Feb 12, 2018 at 02:47:14PM -0600, Eric Sandeen wrote: >> On 2/5/18 5:22 PM, Darrick J. Wong wrote: >>> From: Darrick J. Wong <darrick.wong@xxxxxxxxxx> >>> >>> Record the output of an interactive session in the system log so that >>> future support requests can get a better picture of what happened. >>> >>> Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx> >> >> I really want to log things, but I'm conflicted about spamming syslog. >> I'm wondering if a generic /var/log/xfs.log would be good, and it could >> eventually log all xfs-related administrative actions and outcomes with >> a libfrog library helper... I don't know how non-syslog log files are >> handled in general, does everybody just roll their own? >> >> I'm inclined to leave this one out of 4.15 for now while I/we think >> about the big picture here. > > New idea: we won't flood syslog with the gory details of everything that > happened. Instead we syslog right after we've decided that yes we will > check this filesystem, and syslog again at the end to report what we > found. Sounds good to me. -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
