[collectd] Strange behavior of UnixSock plugin

[Jarle Bjørgeengen]

On Sat, 2008-12-20 at 12:33 +0100, Sebastian Harl wrote:
> Hi,
> 
> On Sat, Dec 20, 2008 at 11:23:43AM +0100, Florian Forster wrote:
> > On Sat, Dec 13, 2008 at 12:05:32PM +0100, Jarle Bjørgeengen wrote:
> > > > ---------------------------------
> > > >  $sock->putval (%identifier, time=> $time , \
> > > > values => [@vdisk_rates, at vdisk_lats])
> > > > ---------------------------------
> > > > 
> > > > and does not return, or output anything to the logfile. 
> > > > 
> > > 
> > > Is this intended behavior , or would it be sensible to return an error
> > > if trying to PUT data with a non existant type ? It would at least
> > > help detecting the problem faster :-) 
> > 
> > You're right, an error message would be appropriate here.. I'll take a
> > look.
> 
> This should have been fixed as a "side-effect" in commit a94f5335f7 [1]
> which has been released in 4.5.0. However, this fix is missing in the
> collectd-4.4 branch.

OK. It'll emerge down to EPEL in a future update then. 

Rgds Jarle Bjørgeengen