search for: flockfil

...ient to successfully compile totally static executable. After up2dating my compile box to CentOS 4.3 I receive following errors when trying to link PHP statically: ... ....(cuted a lot of lines and minor warnings).... .... /usr/lib/libpthread.a(lockfile.o)(.text+0x0): In function `flockfile': : multiple definition of `_IO_flockfile' /usr/lib/libc.a(flockfile.o)(.text+0x0): first defined here /usr/bin/ld: Warning: size of symbol `_IO_flockfile' changed from 30 in /usr/lib/libc.a(flockfile.o) to 18 in /usr/lib/libpthread.a(lockfile.o) /usr/lib/libpthread.a(l...

Commit d02d9c9d used pthread_mutex to avoid interleaving output. However, the standard provides flockfile() for grouping related FILE* I/O that must not be interleaved; and that may be lighter-weight than rolling our own locking. Signed-off-by: Eric Blake <eblake@redhat.com> --- Pushing this one; as a related conversation on another mailing list reminded me about flockfile(). src/errors.c |...

....fc32.x86_64 libselinux-3.1-1.fc33.x86_64 libtasn1-4.15.0-1.fc32.x86_64 p11-kit-0.23.18.1-1.fc32.x86_64 pcre2-10.34-4.fc32.x86_64 (gdb) t a a bt Thread 9 (Thread 0x7fc4a9a1e640 (LWP 109871)): #0 0x00007fc4b9d32e5b in __lll_lock_wait_private () from /lib64/libpthread.so.0 #1 0x00007fc4b9d34115 in flockfile () from /lib64/libpthread.so.0 #2 0x000000000040a053 in nbdkit_debug (fs=0x41bada "starting worker thread %s") at debug.c:91 #3 0x00000000004081b7 in connection_worker (data=0x9ee9ff0) at connections.c:116 #4 0x00007fc4b9d293f9 in start_thread () from /lib64/libpthread.so.0 #5 0x0000...

FYI, looks like support for Racoon is ending. Does anyone have any experience with the version in ipsec-tools ? ---Mike >Racoon users, > >This is the announcement that the kame project will quit providing >a key management daemon, the racoon, and that "ipsec-tools" will become >the formal team to release the racoon. >The final release of the racoon in the

The patches following do indeed allow you to compile nbdkit.exe, but it does not actually work yet. I'm posting this experimental series more as a work in progress and to get feedback. Note this does not require Windows itself to build or test. You can cross-compile it using mingw64-* packages on Fedora or Debian, and test it [spoiler alert: it fails] using Wine. Rich.

...y.c | 2 +- .gitignore | 2 +- 10 files changed, 69 insertions(+), 17 deletions(-) diff --git a/configure.ac b/configure.ac index aa586997..8c0398fe 100644 --- a/configure.ac +++ b/configure.ac @@ -327,7 +327,6 @@ AC_CHECK_FUNCS([\ fdatasync \ flockfile \ funlockfile \ - get_current_dir_name \ mkostemp \ mlock \ mlockall \ @@ -340,6 +339,7 @@ AC_CHECK_FUNCS([\ dnl Replacement functions that we provide for some platforms. AC_CONFIG_LIBOBJ_DIR([common/replacements]) AC_REPLACE_FUNCS([\ + get_current_dir_name \ getdelim \ getline \...

...trict, fpos_t *restrict); extern int fseek(FILE *, long int, int); - extern int fsetpos64(FILE *, const fpos_t *); + extern int fsetpos(FILE *, const fpos_t *); extern long ftell(FILE *); extern void rewind(FILE *); extern void perror(const char *); @@ -2841,8 +2834,8 @@ extern void flockfile(FILE *); extern void funlockfile(FILE *); - extern int fseeko64(FILE *, off_t, int); - extern off_t ftello64(FILE *); + extern int fseeko(FILE *, off_t, int); + extern off_t ftello(FILE *); extern int ftrylockfile(FILE *); extern void funlockfile(FILE *); # 470 "/opt/lib/gcc/powe...

Our use of "%m" in various error messages is testament to the project's initial life on Linux - but other than Cygwin, I know of no other platforms supporting that glibc extension. We COULD audit the code and manually turn "%m" into "%s"/strerror(errno), but that's a lot of churn. Instead, let's fix the few outliers that can't be easily wrapped, then

On 2015-12-17 19:30, peter dalgaard wrote: > Presumably the file in question is one of > > Peter-Dalgaards-MacBook-Air:BUILD pd$ grep -r "^Package: tools" * > library/tools/DESCRIPTION:Package: tools > src/library/tools/DESCRIPTION:Package: tools > > so the first thing I'd do is to have a good look at those files and see if they got somehow corrupted. > >

...ULL)) + { + size_t s; + + gmtime_r (&tv.tv_sec, &tm); + s = strftime (timestamp, sizeof timestamp, "%F %T", &tm); + assert (s); + s = snprintf (timestamp + s, sizeof timestamp - s, ".%06ld", + 0L + tv.tv_usec); + } + flockfile (logfile); + fprintf (logfile, "%s connection=%" PRIu64 " %s ", timestamp, h->connection, + act); + if (id) + fprintf (logfile, "id=%" PRIu64 " ", id); + va_start (args, fmt); + vfprintf (logfile, fmt, args); + va_end (args); + fputc (&...

This is the previous 5/9 patch posted earlier today, split into reviewable chunks. This passes bisection with -x 'make && make check', but I didn't work very hard on the commit messages, so I refer you back to the original patch to explain how it works: https://www.redhat.com/archives/libguestfs/2020-March/msg00248.html Rich.

Here's what I'm currently playing with; I'm not ready to commit anything until I rebase my FUA work on top of this, as I only want to break filter ABI once between releases. Eric Blake (2): backend: Rework internal/filter error return semantics filters: Add log filter TODO | 2 - docs/nbdkit-filter.pod | 84 +++++++-- docs/nbdkit.pod

This is an incomplete port to Windows. Currently the server compiles and starts up successfully, but goes into an infinite loop when you connect to it. Nevertheless I think the approach is ready for feedback. This being Windows the changes go quite deep. Rich.

This creates libnbdkit.so as discussed in the following thread: https://www.redhat.com/archives/libguestfs/2020-March/thread.html#00203 test-delay-shutdown.sh fails for unclear reasons. This series starts by reverting "tests: Don't strand hung nbdkit processes" which is because several other tests fail randomly unless I revert this patch. I didn't investigate this yet so it

Since v1: - patch 1: check size limits - patch 2: better handling of default export name canonicalization - patch 3: support filters as well as plugins - patch 4: new - patch 5: rewrite sh parser, fix testsuite to actually work and cover more cases (now that libnbd.git is fixed) Eric Blake (4): server: Add exports list functions server: Prepare to use export list from plugin log: Add

----- Original Message ----- > From: "James Molloy via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Vaivaswatha Nagaraj" <vn at compilertree.com> > Cc: "LLVM Dev" <llvm-dev at lists.llvm.org> > Sent: Thursday, December 3, 2015 4:41:46 AM > Subject: Re: [llvm-dev] Function attributes for LibFunc and its impact on GlobalsAA > >

Since v1: add the blocksize filter, add testsuite coverage of the log filter, several fixes to the log filter based on what adding tests revealed I'm still working on FUA flag support patches on top of this; the patches should all be committed in the same release, as we want to minimize the number of releases that cause a filter ABI/API bump Eric Blake (3): backend: Rework internal/filter

This is a major rewrite compared to my v1 series, where I've tried a lot harder to ensure that we still accommodate building on Haiku (although I have not actually yet fired up a Haiku VM to try it for myself). I also managed to make the sh plugin fully parallel, on capable platforms. See also my question on patch 10 on whether I've picked the best naming convention. Eric Blake (17):

...am’ was not declared in this scope /usr/include/stdio.h:854: error: expected initializer before ‘__THROW’ /usr/include/stdio.h:870: error: expected initializer before ‘__THROW’ /usr/include/stdio.h:874: error: expected initializer before ‘__THROW’ /usr/include/stdio.h:882: error: variable or field ‘flockfile’ declared void /usr/include/stdio.h:882: error: ‘FILE’ was not declared in this scope /usr/include/stdio.h:882: error: ‘__stream’ was not declared in this scope /usr/include/stdio.h:886: error: ‘FILE’ was not declared in this scope /usr/include/stdio.h:886: error: ‘__stream’ was not declared in th...

After more than a month since v2 [1], I've finally got my FUA support series polished. This is all of my outstanding patches, even though some of them were originally posted in separate threads from the original FUA post [2], [3] [1] https://www.redhat.com/archives/libguestfs/2018-January/msg00113.html [2] https://www.redhat.com/archives/libguestfs/2018-January/msg00219.html [3]