Delinquent Half-Awake

Black Hole

May contain traces of nut
On the supposition that failure to enter the standby state is due to shut-down housekeeping becoming stalled, is there something we can do on the command line to find out where the stall is? For example: a command to list file activity or open files?
 
My standard recommendation
One way you can sometimes identify rogue files where the Humax is stuck trying to process them is to to issue in a command window
Code:
lsof -Fns | grep "\.ts" | sort -u
This lists inuse .ts files,
When the system is idle there shouldn't be any in use (apart from perhaps the TSR recording n/mnt/hd2/Tsr/0.ts)
If something is in use when system should be going to standby try renaming it to a different file extension, rebooting and trying to shutdown again

Not guarantees since there could be many causes of delinquency!

Zero length recordings are also implicated in delinquent events - to scan for them
Code:
 find "/media/My Video"  -size 0 -type f -name "*.ts" -follow
 
Last edited:
My standard recommendation


Not guarantees since there could be many causes of delinquency!

Zero length recordings are also implicated in delinquent events - to scan for them
Code:
 find "/media/My Video"  -size 0 -type f -name "*.ts" -follow
Just had do this for my own system!
lsof showed nothing in use but following scan for zero length recordings and deleting them the box has now fully shut down
 
Back
Top