Re: libudev queue finished seqnums

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, May 8, 2011 at 20:32, Sebastian Wiesner
<lunaryorn@xxxxxxxxxxxxxx> wrote:
> I've got a question about libudev, concerning the function
> "udev_queue_get_seqnum_is_finished()". ÂAccording to the
> documentation, it returns a flag, indicating whether the given
> sequence number has already been processed. ÂIn my experiments
> however, I found this function to always return 1, even for sequence
> numbers which haven't ocurred yet. ÂThe attached test program gives
> the following output on my system:
>
> $ ./udev_queue_sequence_numbers
> current seqnum: 1662
> is previous seqnum finished? yes
> is current seqnum finished? yes
> is next seqnum finished? yes
>
> In my understanding, the last line should have said "no", because the
> number immediately folllowing the current sequence number has
> obviously not yet occurred.
>
> Am I missing something?

I guess, you need to read the function name as
_seqnum_is_not_active(). It will return true for all event numbers
currently not queued, including numbers larger than the currently
handled one.

Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel]     [Linux DVB]     [Asterisk Internet PBX]     [DCCP]     [Netdev]     [X.org]     [Util Linux NG]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux