Measure-command - using .seconds won't return number over 59. Bug or feature?


so i'm using measure-command bit log metrics different commands.  the commands i'm running take anywhere 1 second couple minutes, settled on wanting command times returned in seconds.  here basic sample piece of code outlines issue.

$time = (measure-command {start-sleep -s 65}).seconds
value of $time 5 if run command.  why isn't 65?  i had use .totalseconds("#") wanted, seems bug me.


unfortunately there 60 seconds minute 7 seconds late if ignore 2 minutes.  if don't more 60 "totalseconds" late in trouble.

\_(ツ)_/



Windows Server  >  Windows PowerShell



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group