Actually this a question for Matthew Wall. I'm using the cmon extension for
a while new, with success. Thank you for that.
However, recently I changed hardware for our weatherstation, which is now
running ubuntu server 16.04.
Since then, CPU_temp is no longer read out, and also neteth0rbytes an
On Tuesday, October 18, 2016 at 1:25:14 PM UTC-4, Eelco F wrote:
>
> Since then, CPU_temp is no longer read out, and also neteth0rbytes and
> tbytes are now longer written to the graphs. I think the latter must be due
> to ubuntu which calls eth0 enp0s25 now. This is due to systemd.
>
why must t
Thank you for your quick reply. I understand your frustration on systemd,
and was completely surprised myself to find out my network interface wasn't
called eth0 anymore...
However I can try to rename it, but I control the server remotely over ssh,
and don't want to break the connection off
On Tuesday, October 18, 2016 at 11:02:33 AM UTC-7, mwall wrote:
>
> On Tuesday, October 18, 2016 at 1:25:14 PM UTC-4, Eelco F wrote:
>>
>> Since then, CPU_temp is no longer read out, and also neteth0rbytes and
>> tbytes are now longer written to the graphs. I think the latter must be due
>> to ub
On Tuesday, October 18, 2016 at 3:29:48 PM UTC-4, Vince Skahan wrote:
>
> I've been on the other end of unpredictable ethernet naming, where some
> kernel updates changed which nic was eth0 vs. eth1 in an embedded system
> that I couldn't mess with. Something about PCI bus ordering changed, if I
