Just after boot:
● darkstat.service - LSB: start darkstat monitoring system at boot time
Loaded: loaded (/etc/init.d/darkstat; bad; vendor preset: enabled)
Active: active (running) since Wed 2019-09-04 15:56:16 CEST; 2min 30s ago
Docs: man:systemd-sysv-generator(8)
Process: 859 ExecSt
I never checked it just after a boot, but the process was always missing before
a "systemctl restart".
"systemctl start" definitely does not start the process.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
root@colm:~# systemctl start darkstat
root@colm:~# systemctl status darkstat
● darkstat.service - LSB: start darkstat monitoring system at boot time
Loaded: loaded (/etc/init.d/darkstat; bad; vendor preset: enabled)
Active: active (exited) since Mon 2019-08-26 23:49:16 CEST; 1 weeks 0 days
a
Yes, my bad, there is no bug in that expression.
Altough for some reason "systemctl restart darkstat" works while "systemctl
start darkstat" does not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183
Public bug reported:
---
# apt show darkstat
Package: darkstat
Version: 3.0.719-1
Priority: optional
Section: universe/net
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Rene Mayorga
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 169 kB
Depends: libc6 (>= 2.1
I can confirm that there is some regression going from grub2 2.00 to
2.02~beta2.
I have disk0 with traditional partition table and three partitions:
sda1 is Windows boot
sda2 is Windows system
sda3 is linux Mint root partition (with /boot inside it)
In the past I manually set up the Windows bootl
