In the good old days you are used ifdown and ifup and so you can bring up a network interface. Now you have systemd and you should use networkctl
networkctl list => show all interfaces
networkctl down eht0
shutdown interface
networkctl up eht0
bring up interface
https://manpages.ubuntu.com/manpages/kinetic/en/man1/networkctl.1.html
Systemd have loots of tools to analyses boot performance on your system. If you want this to display graphical then use this command.
We want to display the bluetooth stack.
systemd-analyze dot 'bluetooth*' | dot -Tsvg > blue.svg
If you want to see the complete boot sequence from systemd use this command.
systemd-analyze plot > complete_systemd_boot.svg
You have upgraded from Debian 7 to Debian 8 and you are usign syslog-ng.
You will be in a little bit in trouble with syslog-ng
You can check this with systemctl status syslog-ng.service
syslog-ng.service start request repeated too quickly, refusing to start
syslog-ng service is not starting.
Check your local config file search after ” unix-stream(“/dev/log”);”
People with custom syslog-ng configurations will most likely face upgrade problems due to the unix socket type mismatch between systemd and syslog-ng old configuration file:
- systemd creates /dev/log as
unix-dgram- syslog-ng < 3.2.5 expected /dev/log to be
unix-stream(configuration file)If you use ‘unix-stream (“/dev/log”)’ in one of your log messages sources, you will need to manually change it to ‘unix-dgram (“/dev/log”)’.
Found here
Konkretor Blog, IT Stuff and more 