On 10/07/2015 04:26 PM, Damjan Georgievski wrote:
if it's a failed service, you might need systemctl reset-failed
Thanks! That did the trick!
Łukasz
if it's a failed service, you might need systemctl reset-failed
On 7 October 2015 at 13:43, Łukasz Michalski wrote:
>
>>> ● vboxvmservice@A.service - VBox Virtual Machine A Service
>>> Loaded: loaded (/etc/systemd/system/vboxvmservice@.service; enabled;
>>> vendor preset: disabled)
>>> A
● vboxvmservice@A.service - VBox Virtual Machine A Service
Loaded: loaded (/etc/systemd/system/vboxvmservice@.service; enabled;
vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2015-10-01 12:02:49 CEST; 4
days ago
Main PID: 15101 (code=exited, status=0/SUCCESS)
How
On 6 October 2015 at 10:35, Łukasz Michalski wrote:
> Hi,
>
> I have template service for VirtualBox:
>
> [root@serenity amag_kghm]# cat /etc/systemd/system/vboxvmservice@.service
> [Unit]
> Description=VBox Virtual Machine %i Service
> Requires=systemd-modules-load.service
> After=systemd-modules
On 10/06/2015 12:58 PM, Guus Snijders wrote:
> A reboot is probably the quickest way to get rid of this "ghost"
> entry.
Maybe it's enough to systemctl disable vboxvmservice@A.service.
Op 6 okt. 2015 10:35 schreef "Łukasz Michalski" :
>
> Hi,
>
> I have template service for VirtualBox:
>
> [root@serenity amag_kghm]# cat /etc/systemd/system/vboxvmservice@.service
[...]
> On of service from this template failed and I removed it.
> Now systemctl status vboxvmservice@* shows:
>
> ● v
6 matches
Mail list logo
