Bug description
On the https://psutil.readthedocs.io/en/latest/ page, there are 'terminate my children' links to the https://psutil.readthedocs.io/en/latest/#terminate-my-children section which appears to not exist anymore.

This is not an issue in 5.3.0 (https://psutil.readthedocs.io/en/release-5.3.0/#terminate-my-children).

It would be really useful if the project would have a bindep.txt file which mentions system packages required for building the code.

Details at https://docs.openstack.org/infra/bindep/readme.html -- I mention that there is nothing specific to OpenStack about bindep tool.

System Details:

• Operating System: MacOS
• Persepolis Version: 3.1
• How do you install Persepolis? DMG
  1
  
  2
  
  3

Debian package should live in separate repository instead of separate branch to make gpb usage earlier.

Is there any chance that you will create a printable version of this docs as it would be very useful if it is distributed on my college tech club and my fellow linux geekmate. Thanks

(...)

Having said that, I can see how _acquire_ implies a transition of some kind, so perhaps it'd be better to just change the docs (solo5.h) to say that you're only allowed to call it once per handle?

Originally posted by @mato in Solo5/solo5#402

Hi,
Could you please help me understand what I'm missing:

Python 3.6.9
[GCC 8.3.0] on linux

from pyroute2 import ethtool
etht = ethtool.Ethtool()
ERROR:root:Generic netlink protocol ethtool not found
ERROR:root:Please check if the protocol module is loaded

and looks like this happens specifically in this place

_with_nl.is_nlethtool_in_kernel()
ERROR:root:Generic netlink p

These are the kernel options required that are missing from the latest vagrant box kernel:

• CONFIG_BRIDGE_NETFILTER
• CONFIG_NETFILTER_XT_MATCH_IPVS
• CONFIG_IP_NF_TARGET_REDIRECT
• CONFIG_EXT3_FS_XATTR
• CONFIG_VXLAN
• CONFIG_NF_NAT_TFTP
• CONFIG_NF_CONNTRACK_TFTP
• CONFIG_AUFS_FS
• `

The manpage gives a brief example of using mdnsctl to publish a service. The example is perhaps a little too brief.

From the name, and from the (of course, only roughly standardised) behaviour of other fooctl tools on various unixes, I expected that the mdnsctl publish command would communicate with the running daemon, adjust its configuration, and exit. The manpage, and its publish