> On 28 Jan 2022, at 15:33, Robert-André Mauchin wrote:
>
> Hello,
>
> I'm sorry, this is entirely my fault. I provided symlinks for the binaries,
> but didn't think of the systemd unit files symlinks. The services files were
> added or modified to take into account environment files which
On 1/28/22 14:18, Barry Scott wrote:
On 28 Jan 2022, at 12:28, Tomasz Torcz wrote:
On Fri, Jan 28, 2022 at 12:01:43PM +, Barry Scott wrote:
I just had to fix a number of my servers that use node exporter.
The service name has been changed. Why was this done and did no one
think about
> On 28 Jan 2022, at 12:28, Tomasz Torcz wrote:
>
> On Fri, Jan 28, 2022 at 12:01:43PM +, Barry Scott wrote:
>> I just had to fix a number of my servers that use node exporter.
>>
>> The service name has been changed. Why was this done and did no one
>> think about the impact on users?
>
On Fri, Jan 28, 2022 at 12:01:43PM +, Barry Scott wrote:
> I just had to fix a number of my servers that use node exporter.
>
> The service name has been changed. Why was this done and did no one
> think about the impact on users?
This was done here:
On Friday, 28 January 2022 12:01:43 GMT Barry Scott wrote:
> I just had to fix a number of my servers that use node exporter.
>
> The service name has been changed. Why was this done and did no one
> think about the impact on users?
>
> In the worst case I had a server fail to reboot because I
I just had to fix a number of my servers that use node exporter.
The service name has been changed. Why was this done and did no one
think about the impact on users?
In the worst case I had a server fail to reboot because I had
Requires=node_exporter.service in the default target.
Barry
