Hi,
Ludovic Courtès writes:
> Hi Maxim & Attila,
>
> Maxim Cournoyer skribis:
>
>> Ludovic Courtès writes:
>
> [...]
>
> When a service is stopped at the time of reconfigure, it is immediately
> replaced and then started.
>
> Replacing works by unregistering the old instance fr
Hi Maxim & Attila,
Maxim Cournoyer skribis:
> Ludovic Courtès writes:
[...]
When a service is stopped at the time of reconfigure, it is immediately
replaced and then started.
Replacing works by unregistering the old instance from the registry and
registering a new one
Hi Ludovic,
Ludovic Courtès writes:
> Hi,
>
> Maxim Cournoyer skribis:
>
>> Ludovic Courtès writes:
>
> [...]
>
>>> When a service is stopped at the time of reconfigure, it is immediately
>>> replaced and then started.
>>>
>>> Replacing works by unregistering the old instance from the registry
Hi,
Maxim Cournoyer skribis:
> Ludovic Courtès writes:
[...]
>> When a service is stopped at the time of reconfigure, it is immediately
>> replaced and then started.
>>
>> Replacing works by unregistering the old instance from the registry and
>> registering a new one. As a side effect, you
Hi Ludovic,
Ludovic Courtès writes:
> Attila Lendvai skribis:
>
>> i turn off some services using `herd disable`. then i do a `guix
>> system reconfigure`, and these services get enabled and started.
>>
>> i would expect the enabled/disabled state to be preserved across
>> reconfigures.
>
> Wh
Attila Lendvai skribis:
> i turn off some services using `herd disable`. then i do a `guix system
> reconfigure`, and these services get enabled and started.
>
> i would expect the enabled/disabled state to be preserved across reconfigures.
When a service is stopped at the time of reconfigure,
i turn off some services using `herd disable`. then i do a `guix system
reconfigure`, and these services get enabled and started.
i would expect the enabled/disabled state to be preserved across reconfigures.
if it's not easily feasible in the current architecture, then feel free to
close this.
