I think you're better off trying to rewrite from scratch or looking for a Windows version — Pekka. You'd basically have to rewrite it from scratch for Windows.
I just found this information that mentions a way to do it, but would that work correctly to replace the nix code here? Add a comment. Active Oldest Votes. Let me know how you get on. Improve this answer. DaveRandom DaveRandom Andrew Andrew 1, 1 1 gold badge 18 18 silver badges 29 29 bronze badges. Vlad S. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. I have a workaround for this issue. Clear the System Event Log.
There is some event that has occurred and has been logged to the System Event Log that causes an AppCrash event to occur. The failure only occurs when additional switches are used against a system that has some X event in the System Log. My guess is that the X event might be "The previous system shutdown at time on date was unexpected" is causing the issue where the additional events cannot be determined. I don't believe that is what is cusing. I have teo systems with crash records.
I just tested to see. The uptim utility reports as normal although it may not give an accurate number with crash records present. It is possible that teh event log can become corrupted.
Clearing it will fix this in most cases. Keep an eye on it. You may also have found an off case wher a mix of conditions does cause uptime to fail. There are numerous utilities claiming to give accurate uptime reports. I ssupect all have some fault or another. IMO, if the program finds any events, it should abort, because as soon as there are these events, it is impossible to determine the accurate up-time.
I think this makes the whole 'uptime' program academic, because surely you're really interested in the problem servers, the ones that do crash? Thanks for the input.
I concur that the events will impact the ablility to calculate availabilty. Since we are looking to calculate uptime as close as possible your point is well taken.
So, the workaround of clearing the logs on servers that fail to run the utility, puts the server back in a state where the calculation will be accurate. Using uptime. Since we are fortunate enough to rarely have "abnormal shutdowns" we can get a good sampling from this tool. We do not need the historical details of reboots beyond that. Note: In our cases, many servers have events "abnormal shutdowns" yet the tool still successfully runs albeit the availability statistics may be skewed.
We just needed a way to get the servers that were failing to to work again. Clearing the System Log worked for us. Just clear the logs, reboot the server, and run uptime. Hopefully, this will help some others looking to get uptime working again regardless of how accurate it may be perceived. Office Office Exchange Server. Not an IT pro? Script Center. Sign in.
United States English. Also, since many instances of these events are stored, we can query the history of uptimes! PowerShell has a few different ways you can retrieve uptime. You can either query WMI or use the Windows event log. You can see below you can use the WMIC syntax os get lastbootuptime to return the last time the server was started. The systeminfo command displays detailed configuration info about a computer and can be used to query system uptime. By using the built-in find command line tool you can parse the text to retrieve the data you need.
You do not have to download anything to leverage systeminfo , as it comes pre-installed with Windows. You can also quickly query uptime via Net Statistics or more commonly known as net stats. The net stats command returns general information about your session.
You can see below the Statistics since… line. This date indicates when the machine was started. This utility is perfect for quickly querying uptime on any Windows version. The major benefit of this tool is the convenience factor. If you find yourself using this many times per day you may want to consider this method.
After downloading the tool, extract uptime. Then open up a command prompt and simply type uptime.
0コメント