Howto receive fsnotify messages with libsmbclient.

[Stef Bon]

Yes, I already thought that it requires some (major?) changes.

Now it works without eventloop. When working with an eventloop, which
is handled by the app, things are going to be totally different than
the way things are
now.
If the eventloop is handled internally by libsmbclient however, it is
not that a big change I think.
But I do not have that great insight how libsmbclient works, so I
maybe wrong here.

The only thing required is a linking a callback defined by the app
using libsmbclient to be called when
a message is received from the server.

Stef

2012/9/3 Volker Lendecke <Volker.Lendecke at sernet.de>:
> On Mon, Sep 03, 2012 at 01:27:44PM +0200, Jelmer Vernooij wrote:
>> On Mon, Sep 03, 2012 at 01:17:53PM +0200, Stef Bon wrote:
>> > How is it possible to make a FUSE fs like mine read the socket/fd's
>> > used in libsmbclient?
>> > Jelmer said that using these fd's is not easy, since in theory the
>> > fd's may break down temporarly,
>> > and using them in a direct way is not the way libsmbclient is designed.
>> To clarify what I meant; I'm not convinced it is a good idea (or
>> necessary) to expose internals like fds to the user like this.
>> Actually exposing them is probably not hard.
>
> Agreed. Unfortunately I don't think there is a sane way to
> do the changenotify calls using the exported libsmbclient
> interface. We certainly do have the ability to do so using
> the tevent_req API, but this is a layer below libsmbclient
> and not exported publically. This is definitely something
> that would be very nice to have, but it's just not done yet.
>
> Sorry,
>
> Volker
>
> --
> SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
> phone: +49-551-370000-0, fax: +49-551-370000-9
> AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
> http://www.sernet.de, mailto:kontakt at sernet.de