search for: smbcctx

Dear Gents, We are using libsmbclient smbc_getFunctionRead to read from a Microsoft DFS share. Before each 64k read there are a QUERY_PATH_INFO and a GET_DFS_REFERRAL which slow down the transmission. Is there a way to query these only once at the beginning of the transmission and cache it? system: 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) x86_64 GNU/Linux lib:

...smbclient has become increasingly difficult to accomplish, while also keeping the code organization such that it is easily readable. Towards the goal of maintaining ABI compatibility and also keeping the code easy to maintain and enhance, the API has been enhanced. In particular, the fields in the SMBCCTX context structure are no longer intended to be read/write by the user, and are marked as deprecated. An application that previously accessed the members of the SMBCCTX context structure will now encounter warnings if recompiled. This is intentional, to encourage implementation of the small change...

...smbclient has become increasingly difficult to accomplish, while also keeping the code organization such that it is easily readable. Towards the goal of maintaining ABI compatibility and also keeping the code easy to maintain and enhance, the API has been enhanced. In particular, the fields in the SMBCCTX context structure are no longer intended to be read/write by the user, and are marked as deprecated. An application that previously accessed the members of the SMBCCTX context structure will now encounter warnings if recompiled. This is intentional, to encourage implementation of the small change...

...smbclient has become increasingly difficult to accomplish, while also keeping the code organization such that it is easily readable. Towards the goal of maintaining ABI compatibility and also keeping the code easy to maintain and enhance, the API has been enhanced. In particular, the fields in the SMBCCTX context structure are no longer intended to be read/write by the user, and are marked as deprecated. An application that previously accessed the members of the SMBCCTX context structure will now encounter warnings if recompiled. This is intentional, to encourage implementation of the small change...

...smbclient has become increasingly difficult to accomplish, while also keeping the code organization such that it is easily readable. Towards the goal of maintaining ABI compatibility and also keeping the code easy to maintain and enhance, the API has been enhanced. In particular, the fields in the SMBCCTX context structure are no longer intended to be read/write by the user, and are marked as deprecated. An application that previously accessed the members of the SMBCCTX context structure will now encounter warnings if recompiled. This is intentional, to encourage implementation of the small change...

...smbclient has become increasingly difficult to accomplish, while also keeping the code organization such that it is easily readable. Towards the goal of maintaining ABI compatibility and also keeping the code easy to maintain and enhance, the API has been enhanced. In particular, the fields in the SMBCCTX context structure are no longer intended to be read/write by the user, and are marked as deprecated. An application that previously accessed the members of the SMBCCTX context structure will now encounter warnings if recompiled. This is intentional, to encourage implementation of the small change...

...smbclient has become increasingly difficult to accomplish, while also keeping the code organization such that it is easily readable. Towards the goal of maintaining ABI compatibility and also keeping the code easy to maintain and enhance, the API has been enhanced. In particular, the fields in the SMBCCTX context structure are no longer intended to be read/write by the user, and are marked as deprecated. An application that previously accessed the members of the SMBCCTX context structure will now encounter warnings if recompiled. This is intentional, to encourage implementation of the small change...

...share. Before each 64k read there are a QUERY_PATH_INFO and a > > GET_DFS_REFERRAL which slow down the transmission. Is there a way to > query > > these only once at the beginning of the transmission and cache it? > > Hmmm. This seems to be done inside : > > SMBC_read_ctx(SMBCCTX *context, > SMBCFILE *file, > void *buf, > size_t count) > > where it's doing: > > status = cli_resolve_path(frame, "", context->internal->auth_info, > file->srv->cl...

...and found that there are some "options". Currently supported options are "?mb=all", "?mb=any". Maybe new option like "?ip=x.y.z.t" can be added? However, with current code options and URL cannot be specified at the same time. Another idea is to put this into SMBCCTX structure... I can create a patch that add this functionality. What should be done for it to be applied upstream? What coding style/policy/etc should I follow? Do you see another solution for this problem? PS. Sorry for my terrible English. With best regards, Alexander.

...smbclient has become increasingly difficult to accomplish, while also keeping the code organization such that it is easily readable. Towards the goal of maintaining ABI compatibility and also keeping the code easy to maintain and enhance, the API has been enhanced. In particular, the fields in the SMBCCTX context structure are no longer intended to be read/write by the user, and are marked as deprecated. An application that previously accessed the members of the SMBCCTX context structure will now encounter warnings if recompiled. This is intentional, to encourage implementation of the small change...

...smbclient has become increasingly difficult to accomplish, while also keeping the code organization such that it is easily readable. Towards the goal of maintaining ABI compatibility and also keeping the code easy to maintain and enhance, the API has been enhanced. In particular, the fields in the SMBCCTX context structure are no longer intended to be read/write by the user, and are marked as deprecated. An application that previously accessed the members of the SMBCCTX context structure will now encounter warnings if recompiled. This is intentional, to encourage implementation of the small change...