Questions[suspend](server)

Does anyone know where "Only allow a magic packet to wake this computer" setting has moved to in 2016-core?

This 2016-core server can be kept awake by continuous pings or if I let it suspend it can be woken by a Magic Packet but does not wake on ping or any other network packets.

On Server 2012 device manager for the NIC there are three check-boxes under the Power Management tab:

1).    "Allow the computer to turm off this device to save power"
2).    "Allow this device to wake the computer"
3).        "Only allow a magic packet to wake this computer"

I have identified that these are stored in the registry hive: HKLM\System\CCS\Control\Class{4D36e972-E325-11CE-BFC1...}\nnnn\PnPCapabilities (DWord)

Where:

24 - 1=off, 2=off, 3=off
16 - 1=on, 2=off, 3=off
0 - 1=on, 2=on, 3=off
256 - 1=on, 2=on, 3=on

I suspect that this setting is enabled by default, how do I disable it in Server-core?

I have a laptop that has been installed with ubuntu 20.04 that is being used as a server. Thus I want it to never suspend.

By default it automatically suspends when the lid is closed.

As I can only access it via ssh (and there is no X installed anyway) I need to disable it via the CLI.

Multiple sites suggest using

sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target

This does indeed stop the laptop from suspending while the lid is closed, but results in systemd-logind consuming 100% cpu and continuously logging the following: (multiple times per second)

 systemd-logind[514]: Suspending...
 systemd-logind[514]: Unit suspend.target is masked, refusing operation.
 systemd-logind[514]: Failed to execute suspend operation: Permission denied

Can anyone tell me how to properly disable suspending?

On a mis-configured or buggy network filer (NFS NAS) writing a large file can cause the filer to freeze.

For diagnostics I need to be able to:

1. Suspend (or in other words temporary freeze) all processes of a particular user
2. Resume the user

Basically, like a kill -s SIGSTOP and kill -s SIGCONT but for the entire user.

To do that, is there a way to temporary take away all CPU-time from a user in Linux?

I've seen it mentioned on Server Fault as well as in a Technet Blog that you should never pause or suspend a domain controller. While searching through Microsoft's documentation on the subject, I only find one instance where that would be bad. Microsoft's official support documentation states only that Domain Controllers shouldn't be suspended for more than the Tombstone period (which is 90 or 180 days) as that could cause lingering objects. Are there any other reasons why somebody wouldn't want to suspend a DC? I don't see how it could cause a USN Rollback. I'm sure there's another bad thing I could be missing. Thanks for your input.

I want to do a large disk transfer, which slows down responsiveness of my system.

What I want is a Unix command that will only run the command after I have been idle at the console for a few minutes. And if I come back half way in, it will suspend the job. Until I walk away from my computer.

Is there such a command, or software package?

[edit: The key part of this question is how to determine if there is console activity, to automatically suspend.]