I'd like to monitor interface state changes as emitted by networkd.
By monitoring the emitted signals though, it looks like the current
interface is either next to useless or I don't understand it at all.
For example, the PropertyChanged signal might have a path of
"/org/freedesktop/network1/link
On Mon, May 16 2016, Lennart Poettering wrote:
>> For example, the PropertyChanged signal might have a path of
>> "/org/freedesktop/network1/link/_33", however I have no clue what link
>> _33 actually refers to.
>>
>> In the node /org/freedesktop/network1/link/_33 there's nothing going
>> back to
On Mon, May 16 2016, Lennart Poettering wrote:
> That's actually the interface index formatted as integer
> string. However, since D-Bus does not allow object path components to
> start with a number it it is escaped with an underscored followed by
> the ASCII code of the character... Hence "3" bec
On Mon, May 16 2016, Lennart Poettering wrote:
>> Just as a curiosity though, is there some logic in the link numbers
>> given? All my links are _3[123]. Since I just need to emit some
>> notifications for the time being, knowing that _XY have the same
>> sequence as what is listed by networkctl wo
On Wed, May 18 2016, Christian Hesse wrote:
> Yuri D'Elia on Mon, 2016/05/16 21:30:
>> I'd like to monitor interface state changes as emitted by networkd.
>
> You may want to take a look at netlink-notify [0]. It does not use networkd
> at all but kernel's netlin
When systemd is generating log entries for some units, it writes the
human description in the syslog:
systemd[xy]: Starting GnuPG cryptographic agent...
systemd[xy]: Stopping GnuPG cryptographic agent...
systemd[xy]: Closing GnuPG cryptographic agent...
however, over time I've found this behavior
On Wed, Jan 11 2017, Reindl Harald wrote:
>> The description is fine for looking at the status of a service (as the
>> unit name is right there), but it does not help in the log, since I have
>> to go and look which unit has the same description (essentially, I have
>> to grep). The unit name is wh
On Wed, Jan 11 2017, Michael Biebl wrote:
> 2017-01-11 15:41 GMT+01:00 Yuri D'Elia :
>> The description is fine for looking at the status of a service (as the
>> unit name is right there), but it does not help in the log, since I have
>> to go and look which uni