-- [ Picked text/plain from multipart/alternative ] He wants to know when there is a connectivity issue and what time/date it occured
On 8/26/05, Clayton Macleod <[EMAIL PROTECTED]> wrote: > > I just gave you the simplest of the simplest. I'm not exactly sure > what you're trying to accomplish here. How is this timestamp going to > be of any use to you? What is going to issue your ping command? If > you're simply typing it in manually, well, look at a clock! ;) If > you're using some script or batch file to run the command then I just > gave you the commands to put in your script or batch file. I think > it's pretty safe to say that "ping -T" isn't really what you're > thinking it is, and isn't what you want. If you want to know what the > time was/is when you issue a command, the simplest way to do that is > to issue a command just before/after that displays the current > date/time. In win32 you can do that with the command I showed > earlier, a "echo.|time" will display the current time. In linux/*nix > you can display that with the "date" command. > > On 8/26/05, Alexander Kobbevik <[EMAIL PROTECTED]> wrote: > > I'm pretty lost when it comes to scripting. > > Basically I would like the "ping -t" command to have a timestamp in > front or > > between pings. > > > > I have searched for it on Google etc. But either they try to get paid > for a > > tool or it gets too complicated. > > I just need the simplest of simplest. > > > -- > Clayton Macleod > >get ye flask > You cannot get ye flask. > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds > -- _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
