Increase msg timeout

[ohadschn]

The msg docs say:

If no time limit is set, the message remains on the user's screen until the user sees the message and clicks OK

Unfortunately, that's wrong, and when /time isn't specified, the message actually disappears after about a minute (at least on my Windows 10 machine [1909]). This misses the entire point of the notification, which is to notify you when something went wrong while you were sleeping and the update was supposed to take place at 3 AM.

This change increases the time limit to 24 hours (86400 seconds), at which point the task would run again anyway (producing a new notification, ad infinitum until the user notices).

[ScriptTiger]

Good call! I think msg has changed a bit since the old days because I used to use it quite a lot while remoting into people's systems to change things and I'd leave a message just to ask them to restart when they get a chance or whatever. Maybe it's only if the msg dialog window becomes active that it times out a minute later? I might just test this later, sending messages to locked accounts or what have you. But obviously plenty of people walk away from their computers while everything is still logged in to get a quick bite to eat or take a piss, whatever, obviously despite best practices of locking/logging no matter how long one intends to be away, and this would obviously be a problem no matter what for many people.

But in any case, whether it does or doesn't work for some people, I don't see any harm in reinforcing a time limit. Thanks again! Microsoft has never been the best with docs...

[ohadschn]

Thanks :)