Re: [mosquitto-dev] SIGUSR1 and SIGUSR2 return errors

[Jacob Lynn <abeboparebop@xxxxxxxxx>]

Ah, thanks for the clarification. It wasn't clear to me from the documentation that it was being sent to stdout.

On Wed, Sep 7, 2016 at 5:50 PM, Roger Light <roger@xxxxxxxxxx> wrote:

Hi Jacob,

The "error" isnt anything to worry about, it's just because the call
to poll() isn't protected against being interrupted by those signals.
I agree with the implication that it's a bit annoying though.

SIGUSR2 causes the subscription tree to be printed to stdout. If your
broker was started as a service or is daemonised then you won't see
that text at all.

Cheers,

Roger

On Wed, Sep 7, 2016 at 4:21 PM, Jacob Lynn <abeboparebop@xxxxxxxxx> wrote:
> Hi all,
>
> When I send a SIGUSR1 or SIGUSR2 to the mosquitto process, I see the
> following error message in the log:
>
> 1473261409: Error in poll: Interrupted system call.
>
> SIGUSR2 does not seem to produce the expected behavior. SIGUSR1 produces the
> expected behavior -- the mosquitto.db persistence file is written to disk.
>
> Restarting the broker did not solve the issue.
>
> Any ideas? In particular I'd like to use SIGUSR2 to see the subscribed
> topics for each user, for debugging purposes.
>
> Best,
> Jacob
>

> _______________________________________________
> mosquitto-dev mailing list
> mosquitto-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/mosquitto-dev
_______________________________________________
mosquitto-dev mailing list
mosquitto-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mosquitto-dev