Revision history [back]

I understand power consumtion reasons to change kernel scheduling if the device is locked (black screen).

I like to run simple shell commands or scripts via ssh connection also if the device is locked. But "sleep 1" could delay for a minute or longer in locked state. Also "vmstat 1" or "top" seem to hang.

But if I'm pinging the device from outside every second I generate regular interrupts and the above commands don't hang.

How to avoid this power saving feature for shell commands. Any links or hints from MER or NEMO sites?

I understand power consumtion reasons to change kernel scheduling if the device is locked (black screen).

I like to run simple shell commands or scripts via ssh connection also if the device is locked. But "sleep 1" could delay for a minute or longer in locked state. Also "vmstat 1" or "top" seem to hang.

But if I'm pinging the device from outside every second I generate regular interrupts and the above commands don't hang.

How to avoid this power saving feature for shell commands. Any links or hints from MER or NEMO sites?

I understand power consumtion reasons to change kernel scheduling if the device is locked (black screen).

I like to run simple shell commands or scripts via ssh connection also if the device is locked. But "sleep 1" could delay for a minute or longer in locked state. Also "vmstat 1" or "top" seem to hang.

Login with ssh could take more than 2 minutes! And you shouldn't scp files during locked state without charger connected. It would take ages ...

But if I'm pinging the device from outside every second I generate it generates regular interrupts interrupts/events and the above commands don't hang. hang.

How to avoid this power saving feature for shell commands. Any links or hints from MER or NEMO sites?

I understand power consumtion reasons to change kernel scheduling if the device is locked (black screen).

I like to run simple shell commands or scripts via ssh connection also if the device is locked. But "sleep 1" could delay for a minute or longer in locked state. Also "vmstat 1" or "top" seem to hang.

Login with ssh could take more than 2 minutes! And you shouldn't scp files during locked state without charger connected. It would take ages ...

But if I'm pinging the device from outside every second it generates regular interrupts/events and the above commands don't hang.

How to avoid this power saving feature for shell commands. Any links or hints from MER or NEMO sites?