Replies: 1 comment
-
Sorry, didn't intend to format the praise above like that (forgot the markdown styles)... but now I feel it should stand as is :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
--
first off, thanks for this unbelievable piece of software! It's incredibly elegant, smart and well thought out and implemented!
I have a few production Windows servers that I sometimes need to check and was wondering what's the best way to accomplish that (speed wise). The servers are located 2000+km away and I'm connected over VPN.
I really like how the .zip (and I guess ssh also) implementation works. That is, it extracts the files to local /tmp and uses that going forward.
I'm using WSL2 on Windows to map the server drive like this:
sudo mount -t cifs -o username=<win_share_user>,domain=<win_domain> //WIN_SHARE_IP/<share_name> /mnt/win_share
Loading the logs takes reasonable amount of time, but further processing shows that lnav is still working through the network (haven't fully figured out when it does that though). But something like scrolling/filtering or searching can raise the network activity, thus slowing things down.
What would be the best way to browse these logs? SSH isn't currently set up on those servers (would that fix it?) and as I'm working in an enterprise, it might be hard to get these things set up.
If lnav could detect it's a slow drive or network or if it could be configured to save the logs locally for specific mounts, that would be really good I guess. And obviously if it could keep on monitoring the network drive for delta changes...
Thanks once again!
Beta Was this translation helpful? Give feedback.
All reactions