search for: _close

...in compiling 0.9.10 with Cygwin? I'm getting the following error:- gcc -DHAVE_CONFIG_H -I. -I. -I../.. -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c istream-file.c istream-file.c:57: conflicting types for `_close' /usr/include/sys/unistd.h:148: previous declaration of `_close' istream-file.c:129: conflicting types for `_read' /usr/include/sys/unistd.h:153: previous declaration of `_read' make: *** [istream-file.o] Error 1 Thanks Tim

...arallel The VDDK plugin currently uses SERIALIZE_ALL_REQUESTS: $ nbdkit vddk --dump-plugin | grep thread max_thread_model=serialize_all_requests thread_model=serialize_all_requests The proposal is to use SERIALIZE_REQUESTS, with an extra mutex added by the plugin around VixDiskLib_Open and _Close calls. PARALLEL is not possible. > This is kind of ugly but simple, and it works great for the file > plugin - we get better > performance than qemu-nbd. > > But since we get low throughput even when we have 10 concurrent > handles for 10 different disks, I'm sure this will...

...ir un fichier" + +#~ msgid "Play / P_ause" +#~ msgstr "Lecture / P_ause" + +#, fuzzy +#~ msgid "Play or pause the file" +#~ msgstr "Permet de lire des fichiers Adobe Flash" + +#~ msgid "_About" +#~ msgstr "A _propos" + +#~ msgid "_Close" +#~ msgstr "_Quitter" + +#~ msgid "_File" +#~ msgstr "_Fichier" + +#~ msgid "_Help" +#~ msgstr "Aid_e" + +#~ msgid "_Open..." +#~ msgstr "_Ouvrir..." commit 1ae07d69d0d9877fffc65602a887a1c170e49ac0 Author: Stephane Loeuille...

...ausible. > > I think a better approach is to catch the error in the Rconn_printf > calls (as R-devel currently does), and also catch errors on > con->close(con). This one requires more changes to the source, so it > may be a day or two before I commit. I have testes it on file_close() and it works (cf. attached patch): > fc=file("/dev/full", "w") > write.csv("a", file=fc) > close(fc) Error in close.connection(fc) : closing file failed > > One thing I have to look into: is anyone making use of the fact that > the R-level clo...

...> > > $ nbdkit vddk --dump-plugin | grep thread > > max_thread_model=serialize_all_requests > > thread_model=serialize_all_requests > > > > The proposal is to use SERIALIZE_REQUESTS, with an extra mutex added > > by the plugin around VixDiskLib_Open and _Close calls. > > I'm not sure what is the difference between SERIALIZE_REQUESTS and > SERIALIZE_ALL_REQUESTS, SERIALIZE_ALL_REQUESTS serializes requests across all handles. SERIALIZE_REQUESTS serializes requests within each handle, but multiple parallel requests can happen to different han...

...///////////////// //Let's open the file in binary mode for reading. if (_topen(pFilePath, _O_RDONLY | _O_BINARY) == -1) { data.valid = false; return; } // Let's initialize the OggVorbis_File. if(ov_open(stdin, &vf, NULL, 0) < 0) { _close(0); data.valid = false; return; } ..... } -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/vorbis/attachments/20050524/5f9b613b/attachment.html

...: not found Checking for __chdir : not found Checking for chflags : not found Checking for _close : not found Checking for _closedir : not found Checking for __closedir : not f...

...better approach is to catch the error in the Rconn_printf >>> calls (as R-devel currently does), and also catch errors on >>> con->close(con). This one requires more changes to the source, so it >>> may be a day or two before I commit. >> I have testes it on file_close() and it works (cf. attached patch): >>> fc=file("/dev/full", "w") >>> write.csv("a", file=fc) >>> close(fc) >> Error in close.connection(fc) : closing file failed >> >>> >>> One thing I have to look into: is an...

I'm interested in building just the OpenSSH clients with MinGW. I figure that the OpenSSL libraries and just the ssh client should be relatively easy to build as they wouldn't require fork()/exec() and the like (well, ssh_askpass() uses fork()/exec(), but that's minor). The other clients, scp and sftp, will require #ifdef hacks so that they use the Windows spawn()/CreateProcess()

...y uses SERIALIZE_ALL_REQUESTS: > > $ nbdkit vddk --dump-plugin | grep thread > max_thread_model=serialize_all_requests > thread_model=serialize_all_requests > > The proposal is to use SERIALIZE_REQUESTS, with an extra mutex added > by the plugin around VixDiskLib_Open and _Close calls. I'm not sure what is the difference between SERIALIZE_REQUESTS and SERIALIZE_ALL_REQUESTS, but it sounds to me like we need PARALLEL. With parallel we will have multiple threads using the same vddk_handle, which can be thread safe since we control this struct. The struct can be: stru...

...A0[PATCH 26/31] Connection: handle_client returns err to client (via cli= ent_send_400) > =A0[PATCH 27/31] connection: more coments for remy > =A0[PATCH 28/31] Big Comments cleanup > =A0[PATCH 29/31] connection: client_setup, send 403 when we can for error > =A0[PATCH 30/31] connection: _close set everything to NULL on the way out > > [this might be a bug] > =A0[PATCH 31/31] source: make get_next_buffer try only 10 times and then = bail out > _______________________________________________ > Icecast-dev mailing list > Icecast-dev at xiph.org > http://lists.xiph.org/m...

Greetings, I noticed a while back someone posted a patch/plugin that allowed Dovecot to use compressed mbox files. I'm now wondering how far that would put us from having compressed maildir? I have a server with more CPU than disk space, and while I can buy more HDD space, my backup solution doesn't make that practical. It seems to me that when looking for a message file, if it

...error in the Rconn_printf >>>>> calls (as R-devel currently does), and also catch errors on >>>>> con->close(con). This one requires more changes to the source, so it >>>>> may be a day or two before I commit. >>>> I have testes it on file_close() and it works (cf. attached patch): >>>>> fc=file("/dev/full", "w") >>>>> write.csv("a", file=fc) >>>>> close(fc) >>>> Error in close.connection(fc) : closing file failed >>>> >>>>> &g...

...t vddk --dump-plugin | grep thread > > > max_thread_model=serialize_all_requests > > > thread_model=serialize_all_requests > > > > > > The proposal is to use SERIALIZE_REQUESTS, with an extra mutex added > > > by the plugin around VixDiskLib_Open and _Close calls. > > > > I'm not sure what is the difference between SERIALIZE_REQUESTS and > > SERIALIZE_ALL_REQUESTS, > > SERIALIZE_ALL_REQUESTS serializes requests across all handles. > SERIALIZE_REQUESTS serializes requests within each handle, > but multiple parallel req...

...;> I think a better approach is to catch the error in the Rconn_printf >> calls (as R-devel currently does), and also catch errors on >> con->close(con). This one requires more changes to the source, so it >> may be a day or two before I commit. > I have testes it on file_close() and it works (cf. attached patch): >> fc=file("/dev/full", "w") >> write.csv("a", file=fc) >> close(fc) > Error in close.connection(fc) : closing file failed > >> >> One thing I have to look into: is anyone making use of the fact...

...ot; command. When I looked at the file from the Win95 client it had the same old contents but you only saw the first 29 bytes. These kind of results occur in my own application, a new test application I wrote, and with WordPad and NotePad. My application does a simple _stat(), _open(), _read(), and _close() sequence. I'm absolutely positive that the file is being closed. After a while or trying to do "QuickView" on the file will cause it to be displayed with its proper contents. -- Charles Curley, Staff Engineer Computer Integrated Manufacturing Lockheed Martin Ocala Operations

...is to catch the error in the Rconn_printf >>>> calls (as R-devel currently does), and also catch errors on >>>> con->close(con). This one requires more changes to the source, so it >>>> may be a day or two before I commit. >>> I have testes it on file_close() and it works (cf. attached patch): >>>> fc=file("/dev/full", "w") >>>> write.csv("a", file=fc) >>>> close(fc) >>> Error in close.connection(fc) : closing file failed >>> >>>> >>>> One thing...

...physical_pos = 5816, header_size = {physical_size = 80, virtual_size = 84, lines = 0}, body_size = {physical_size = 4387, virtual_size = 4566, lines = 179}, flags = 72, context = 0x0} (gdb) print in *(input->real_stream) $9 = {iostream = {pool = 0xb9598, refcount = 1, close = 0x615a0 <_close>, destroy = 0x615a8 <_destroy>, set_max_buffer_size = 0x615e4 <_set_max_buffer_size>}, read = 0x61a20 <_read>, seek = 0x61b9c <_seek>, sync = 0x61cc4 <_sync>, stat = 0x61cd8 <_stat>, istream = {v_offset = 1387, stream_errno = 0, mmaped = 0, clo...

[NB: Adding PUBLIC mailing list because this is upstream discussion] On Mon, Aug 03, 2020 at 06:27:04PM +0100, Richard W.M. Jones wrote: > On Mon, Aug 03, 2020 at 06:03:23PM +0300, Nir Soffer wrote: > > On Mon, Aug 3, 2020 at 5:47 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > All this make sense, but when we upload 10 disks we have 10 connections > > but still we

...checking for syslog... no > checking for vsyslog... no > checking for syscall... no > checking for _dup... no > checking for _dup2... no > checking for _opendir... no > checking for _readdir... no > checking for _seekdir... no > checking for _telldir... no > checking for _closedir... no > checking for __dup... no > checking for __dup2... no > checking for __opendir... no > checking for __readdir... no > checking for __seekdir... no > checking for __telldir... no > checking for __closedir... no > checking for __getcwd... no > checking for _getcwd...