search for: do_put

I''m heading out of town, but had a quick thought I wanted to share. Rather then using ambiguous named request helpers in controller specs like "do_request", I''ve been using more readable helpers like "post_create". For example... describe ProjectController do def post_create post :create, ... end before do end it "creates a new

...-command "print $1" | tee -a /mnt/autofs/logs/print/print.log It would output [2019/07/04 04:27:36, 0] libsmb/clidfs.c:232(do_connect) Domain=[BBLDTL] OS=[Windows Server 2012 R2 Standard 9600] Server=[Windows Server 2012 R2 Standard 6.3] [2019/07/04 04:27:36, 1] client/client.c:1883(do_put) putting file /mnt/autofs/output/bin/Default/j8989s2bdefault.ps as j8989s2bdefault.ps-11430 (546.7 kb/s) (average 546.7 kb/s) Now after upgrade of our Linux environment "redhatVersion": "Red Hat Enterprise Linux Server release 7.7 (Maipo)", "tomcatVersion&qu...

...02:20, 4] libsmb/clidfs.c:276(do_connect) tconx ok [2011/09/19 12:02:20, 3] lib/util.c:435(dos_clean_name) dos_clean_name [\\directory\filename] [2011/09/19 12:02:20, 3] lib/util.c:487(unix_clean_name) unix_clean_name [\directory\filename] [2011/09/19 12:02:20, 1] client/client.c:1872(do_put) putting file - as \ndirectory\filename Running timed event "tevent_req_timedout" 0xb80399a0 cli_push returned NT_STATUS_IO_TIMEOUT [2011/09/19 12:02:40, 1] client/client.c:1911(do_put) (100.3 kb/s) (average 100.3 kb/s) Some questions: a) can others reproduce this? b) is it...

...ot; ] }''') > + > + # eg. zero request. Just ignore it. > + def do_PATCH(self): > This must read content-length bytes from self.rfile. > + self.send_response(200) > + self.end_headers() > + > + # Flush request. Ignore it. > + def do_PUT(self): > This must read content-length bytes from self.rfile. Both bugs are hidden by the fact that this server close the connection at the end of the request. > + self.send_response(200) > + self.end_headers() > + > +def server(): > + server_address = ("...

...ction `string2group': nsswitch/winbindd_acct.c:225: warning: passing arg 1 of `next_token' from incompatible pointer type client/client.c: In function `do_get': client/client.c:695: warning: passing arg 4 of `cli_getattrE' from incompatible pointer type client/client.c: In function `do_put': client/client.c:1071: warning: passing arg 4 of `cli_getattrE' from incompatible pointer type utils/smbcontrol.c: In function `do_printnotify': utils/smbcontrol.c:423: warning: passing arg 3 of `notify_printer_byname' discards qualifiers from pointer target type rpcclient/cmd_lsar...

...TCH(self): > > > > > > > This must read content-length bytes from self.rfile. > > > > > > > + self.send_response(200) > > > + self.end_headers() > > > + > > > + # Flush request. Ignore it. > > > + def do_PUT(self): > > > > > > > This must read content-length bytes from self.rfile. > > > > Both bugs are hidden by the fact that this server close the connection at > > the end > > of the request. > > Also this is covered by the attached patch. > > &g...

...uest. Just ignore it. > > + def do_PATCH(self): > > > > This must read content-length bytes from self.rfile. > > > > + self.send_response(200) > > + self.end_headers() > > + > > + # Flush request. Ignore it. > > + def do_PUT(self): > > > > This must read content-length bytes from self.rfile. > > Both bugs are hidden by the fact that this server close the connection at > the end > of the request. Also this is covered by the attached patch. > > + self.send_response(200) > >...

...dy answered, so I have tracked down some stuff. (Someone recently noted the same bug on HPUX.) My Samba is 2.0.3. I am writing a file via smbclient from a slow (486) 2.2.4 Linux PC to a faster (P 200) 4.0SP4 WinNT PC (this does not happen with Win 95). The Samba code does the file transmission via do_put() in client.c, which function prints the above error if it returns a different value from what was passed inside it. In my case, the returned value is LARGER (69616) than the requested (65536). Weird. Now I am getting inside cli_write() in clientgen.c. AFAIU, MID is some kind of ID for packets sen...

...amba-3.0.2a/source LIBS = -lgen -lresolv -lsocket -lnsl LDSHFLAGS = -shared LDFLAGS = Compiling client/client.c client/client.c: In function `do_get': client/client.c:695: warning: passing arg 4 of `cli_getattrE' from incompatible pointer type client/client.c: In function `do_put': client/client.c:1071: warning: passing arg 4 of `cli_getattrE' from incompatible pointer type client/client.c: In function `remote_completion': client/client.c:2304: `PATH_MAX' undeclared (first use this function) client/client.c:2304: (Each undeclared identifier is reported only...

...local/kerberos/lib/libkrb5.so.3.2: warning: mktemp() possibly used unsafely; consider using mkstemp() Compiling client/client.c client/client.c: In function `do_get': client/client.c:699: warning: passing arg 4 of `cli_getattrE' from incompatible pointer type client/client.c: In function `do_put': client/client.c:1075: warning: passing arg 4 of `cli_getattrE' from incompatible pointer type Compiling client/clitar.c client/clitar.c:91: syntax error before `*' client/clitar.c:91: warning: data definition has no type or storage class client/clitar.c: In function `tar_parseargs...

Has any of you compiled the lastest Samba 3.0 RC2 on Sparc Solaris 9? Any idea about the warning messages in the text attachment ? Thanks.

...ure:2038: gcc --version </dev/null >&5 gcc (GCC) 3.4.1 The program errors read as follows- Compiling client/client.c client/client.c: In function `do_get': client/client.c:699: warning: passing arg 4 of `cli_getattrE' from incompatible pointer type client/client.c: In function `do_put': client/client.c:1075: warning: passing arg 4 of `cli_getattrE' from incompatible pointer type Compiling client/clitar.c client/clitar.c:91: error: parse error before '*' token client/clitar.c:91: warning: data definition has no type or storage class client/clitar.c: In function...

...internal': tdb/tdbutil.c:60: warning: passing arg 1 of `tdb_set_lock_alarm' discards qualifiers from pointer target type client/client.c: In function `do_get': client/client.c:699: warning: passing arg 4 of `cli_getattrE' from incompatible pointer type client/client.c: In function `do_put': client/client.c:1075: warning: passing arg 4 of `cli_getattrE' from incompatible pointer type utils/smbcontrol.c: In function `do_printnotify': utils/smbcontrol.c:431: warning: passing arg 3 of `notify_printer_byname' discards qualifiers from pointer target type rpcclient/cmd_sp...

...warning: passing arg 1 of `next_token' from incompatible pointer type Compiling sam/idmap.c ... Compiling client/client.c (6) client/client.c: In function `do_get': client/client.c:694: warning: passing arg 4 of `cli_getattrE' from incompatible pointer type client/client.c: In function `do_put': client/client.c:1070: warning: passing arg 4 of `cli_getattrE' from incompatible pointer type client/client.c: In function `do_host_query': client/client.c:2670: warning: passing arg 1 of `list_servers' discards qualifiers from pointer target type client/client.c: In function `mai...

...o request. Just ignore it. > def do_PATCH(self): > + self.discard_request() > self.send_response(200) > + self.send_header("Content-Length", "0") > self.end_headers() > > # Flush request. Ignore it. > def do_PUT(self): > + self.discard_request() > self.send_response(200) > + self.send_header("Content-Length", "0") > self.end_headers() > > + def discard_request(self): > + length = self.headers['Content-Length'] >...

...only zero support. + self.wfile.write(b'''{ "features": [ "zero" ] }''') + + # eg. zero request. Just ignore it. + def do_PATCH(self): + self.send_response(200) + self.end_headers() + + # Flush request. Ignore it. + def do_PUT(self): + self.send_response(200) + self.end_headers() + +def server(): + server_address = ("", imageio_port) + httpd = HTTPServer(server_address, RequestHandler) + httpd.serve_forever() + +thread = threading.Thread(target = server, args = [], daemon = True) +thread....

...ction `string2group': nsswitch/winbindd_acct.c:225: warning: passing arg 1 of `next_token' from incompatible pointer type client/client.c: In function `do_get': client/client.c:699: warning: passing arg 4 of `cli_getattrE' from incompatible pointer type client/client.c: In function `do_put': client/client.c:1075: warning: passing arg 4 of `cli_getattrE' from incompatible pointer type utils/net_lookup.c: In function `net_lookup_kdc': utils/net_lookup.c:212: warning: passing arg 3 of `krb5_locate_kdc' from incompatible pointer type utils/net_idmap.c: In function `net_id...

v1 was here: https://www.redhat.com/archives/libguestfs/2018-September/msg00121.html v2: - Rewrote patch 2 from scratch so it incorporates Nir's suggestions. - Add fake module to EXTRA_DIST. - Retested. Unfortunately I am no longer able to test the ordinary conversion path because ovirtsdk4 is incompatible with Fedora 29 / Python 3.7:

This adds a test of -o rhv-upload. Obviously for an upstream test we cannot require a working oVirt server. This test works by faking the ovirtsdk4 Python module, setting PYTHONPATH so that the fake module is picked up instead of the real module (if installed). However it's more complex than that because the nbdkit plugin also expects to talk to a working imageio HTTPS server. Therefore

Here''s a controller spec I wrote, it''s for a very simple RESTful controller (well, aren''t all RESTful controllers simple? :) I''ve created a couple spec helper methods to refactor some of the common code...for example, require_login_and_correct_user creates two specifications: one for when the user isn''t logged in, and one when the user is logged in but