Signed-off-by: Giampaolo Rodola <g.rodola@gmail.com>

Signed-off-by: Giampaolo Rodola <g.rodola@gmail.com>

The function was exiting after one second due to a subprocess.TimeoutException

Fixes #1913

Signed-off-by: guille <guille@users.noreply.github.com>

This has always been cause of confusion, e.g. see:
https://github.com/giampaolo/psutil/pull/1727#issuecomment-698934643

Removed the reference to "physical" from dostrings, functions and test.
I still left it in the doc though, as it's more explanatory.

Signed-off-by: Giampaolo Rodola <g.rodola@gmail.com>

Signed-off-by: Giampaolo Rodola <g.rodola@gmail.com>

"seconds since the epoch" (value returned by `time.time()`) doesn't
depend on the local time zone. It is the same time instance around the
world. It is not in any particular time zone:

```python
import datetime as DT
import zoneinfo

local_time = DT.datetime.fromtimestamp(seconds_since_epoch)    # naive datetime object representing local time
utc_time = DT.datetime.utcfromtimestamp(seconds_since_epoch)  # naive datetime object representing utc time
la_time = DT.datetime.fromtimestamp(seconds_since_epoch, zoneinfo.ZoneInfo("America/Los_Angeles"))   # timezone aware dt
```

Here `local_time`, `utc_time`, `la_time` may correspond to different
clock times but it is exactly the same time instance.