Lnav – An advanced log file viewer for the small-scale
1–10 of 60 posts
Re: Lnav – An advanced log file viewer for the small-scale
#2Re: Lnav – An advanced log file viewer for the small-scale
#3Do we need lnav thread every 3 weeks?
Re: Lnav – An advanced log file viewer for the small-scale
#4Re: Lnav – An advanced log file viewer for the small-scale
#5Re: Lnav – An advanced log file viewer for the small-scale
#6Do we need lnav thread every 3 weeks?
Not everyone checks out daily HN to see all the reposts. Pulling numbers out of the air, I'd say that 5-10% of daily content on HN is a repost, should get used to it. Just hide it an carry on is what I would suggest.
Re: Lnav – An advanced log file viewer for the small-scale
#7Re: Lnav – An advanced log file viewer for the small-scale
#8Do we need lnav thread every 3 weeks?
Re: Lnav – An advanced log file viewer for the small-scale
#9It has a similar feature set (tail, syntax highlighting, SQL reporting) with a focus on accessing files remotely.
Re: Lnav – An advanced log file viewer for the small-scale
#10Does anyone have a trick for connecting to remote hosts as a non-root user but having it elevate to root to read the logs?
For logs managed by syslog daemons, most implementations allows you to set the owner and group of the log files. You could decide on a specific log group and add the desired dedicated user to this group.
In the end it is usually better to ship the logs to a dedicated machine/space/database.