[PATCH] telemetry: lower log level on socket error

[Stephen Hemminger]

On Mon, 17 Jun 2024 15:52:09 +0100
Bruce Richardson <bruce.richardson at intel.com> wrote:

> > > 
> > > Would it be also worthwhile having the probing process wait a small amount
> > > of time or check for an input string before closing the socket? That should
> > > avoid the error message being necessary at all for the case described.  
> > 
> > If telemetry used abstract socket path instead this would not be a problem.
> > Using regular paths leads to races and problems with restart.
> > And all the stat and runtime check logic could go away.  
> 
> Are abstract paths not linux-specific? Also, would using abstract paths not
> mean that we need to implement some form of authentication on the
> connections? Right now, using real paths in the DPDK runtime directory, a
> regular user cannot connect to the telemetry of a process running as
> another user or as root.

Yes. But existing restart logic is brittle.