search for: cache

...tp://lists.samba.org/archive/samba/attachments/20021011/d2594161/attachment.eml -------------- next part -------------- Script started on Fri Oct 11 16:28:55 2002 ]0;aroma:/home/huan/samba-2.2.5/sourcearoma> ./co[K[K[K[Ksudo tcsh ]0;aroma:/home/huan/samba-2.2.5/sourcearoma# ./configure loading cache ./config.cache checking for gcc... (cached) gcc checking whether the C compiler (gcc -O ) works... yes checking whether the C compiler (gcc -O ) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking whether gcc accepts -g... (cached) yes checking for a BSD compati...

...No output written to sshd make: *** [sshd] Error 1 Basically some problems with getspnam. I checked on internet and some solutions are to look in LIBS to -lgen, but from output it looks like it is looking in lgen. Is there some workaround? Here is output from configure: # ./configure loading cache ./config.cache checking for gcc... (cached) cc checking whether the C compiler (cc ) works... yes checking whether the C compiler (cc ) is a cross-compiler... no checking whether we are using GNU C... (cached) no checking whether cc accepts -g... (cached) yes checking host system type... i586-sco...

...onfigure:1206: checking whether gcc and cc understand -c and -o together configure:1264: checking that the C compiler understands volatile configure:1327: checking host system type configure:1348: checking target system type configure:1366: checking build system type configure:1400: checking config.cache system type configure:1665: checking for LFS support configure:1710: gcc -o conftest -O -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE conftest.c 1>&5 configure:1792: checking for inline configure:1832: checking how to run the C preprocessor configure:1912: checking for ANSI...

...ommands and the output. Essentially, I pre-built EGD, SSL, and ran: configure make make errors are listed at the bottom. Can anyone help me get this compiled on Solaris7? Steve sdn at sprintlabs.com ./configure --prefix=/common --sysconfdir=/etc/ssh --with-egd-pool=/common/bin/egd.pl loading cache ./config.cache checking host system type... sparc-sun-solaris2.7 checking for gcc... (cached) gcc checking whether the C compiler (gcc ) works... yes checking whether the C compiler (gcc ) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking whether gcc accepts -...

...es xfn auth_attr: files nisplus prof_attr: files nisplus project: files ----- "configure" I did like following /archive/samba/samba-2.2.5/source # ./configure --prefix=/usr/local/samba --exec-prefix=/usr/local/samba --with-acl-support --with-nisplussam --with-nisplus-home loading cache ./config.cache checking for gcc... (cached) gcc checking whether the C compiler (gcc -O ) works... yes checking whether the C compiler (gcc -O ) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking whether gcc accepts -g... (cached) yes checking for a BSD compati...

http://dovecot.org/tools/nfstest.c I wrote a test utility that tests different ways to flush NFS attribute cache and data cache. Please test in your NFS setup and show me the results, so I can make Dovecot v1.1 works well with NFS. Run the test several times (3 should be enough) to make sure the output stays the same, because the attribute cache flushes might incorrectly say "OK". And of course att...

Hi all, I still have problems with my nt authentication on linux. My problems start when compiling --with-pam This is the output, i can't figure out why i get the error. [root@squid source]# ./configure --with-pam loading cache ./config.cache checking for gcc... (cached) gcc checking whether the C compiler (gcc -O ) works... yes checking whether the C compiler (gcc -O ) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking whether gcc accepts -g... (cached) yes checking for a BSD compati...

...given the design of filters, because a background thread cannot access the next_ops struct which is only available during requests. Therefore we spread the work over the request threads. Each blk_* function checks whether there is work to do, and if there is will reclaim up to two blocks from the cache (thus ensuring that we always make forward progress, since each blk_* function can only add at most one block to the cache). --- filters/cache/nbdkit-cache-filter.pod | 71 +++++++++++ filters/cache/cache.h | 13 ++ filters/cache/blk.c | 163 ++++++++++++++++++++...

...given the design of filters, because a background thread cannot access the next_ops struct which is only available during requests. Therefore we spread the work over the request threads. Each blk_* function checks whether there is work to do, and if there is will reclaim up to two blocks from the cache (thus ensuring that we always make forward progress, since each blk_* function can only add at most one block to the cache). --- filters/cache/nbdkit-cache-filter.pod | 70 +++++++++++ filters/cache/cache.h | 11 ++ filters/cache/blk.c | 163 ++++++++++++++++++++...

...given the design of filters, because a background thread cannot access the next_ops struct which is only available during requests. Therefore we spread the work over the request threads. Each blk_* function checks whether there is work to do, and if there is will reclaim up to two blocks from the cache (thus ensuring that we always make forward progress, since each blk_* function can only add at most one block to the cache). --- filters/cache/nbdkit-cache-filter.pod | 50 ++++++++ filters/cache/cache.h | 13 ++ filters/cache/blk.c | 166 +++++++++++++++++++++++...

...given the design of filters, because a background thread cannot access the next_ops struct which is only available during requests. Therefore we spread the work over the request threads. Each blk_* function checks whether there is work to do, and if there is will reclaim up to two blocks from the cache (thus ensuring that we always make forward progress, since each blk_* function can only add at most one block to the cache). --- filters/cache/nbdkit-cache-filter.pod | 50 ++++++ filters/cache/cache.h | 6 + filters/cache/reclaim.h | 48 ++++++ filters/cache/blk....

I have a problem for specific mailbox. In mail.err file I see a lot: Nov 2 07:41:17 s1 dovecot: imap(artur at example.pl): Error: unlink(/var/vmail/example.pl/artur/Maildir/dovecot.index.cache) failed: No such file or directory (in mail-cache.c:28) Nov 2 07:41:17 s1 dovecot: imap(artur at example.pl): Error: Corrupted index cache file /var/vmail/example.pl/artur/Maildir/dovecot.index.cache: Broken MIME parts for mail UID 2356 in mailbox INBOX: Cached MIME parts don't match message d...

Patch 1 is the same as last time, except for a minor comment fix. Patch 2 should address everything that Eric mentioned in his review, and has been retested. Rich.

This patch series enhances the cache filter in a few ways, primarily adding a "cache-on-read" feature (similar to qemu's copyonread); and adding the ability to limit the cache size and the antecedent of that which is having a method to reclaim cache blocks. As the cache is stored as a sparse temporary file, reclaiming c...

Dear gluster experts, I search through glusterfs 3.3 source tree and can't find any fuse open option FOPEN_KEEP_CACHE related code. Does this mean that glusterfs 3.3 doen't support fuse keep cache feature? However I did find keep cache code in mainline. My question is: 1 does glusterfs 3.3 support page cache? 2 if not what is the best practice to improve performance if a file is frequently accessed by read esp...

...given the design of filters, because a background thread cannot access the next_ops struct which is only available during requests. Therefore we spread the work over the request threads. Each blk_* function checks whether there is work to do, and if there is will reclaim up to two blocks from the cache (thus ensuring that we always make forward progress, since each blk_* function can only add at most one block to the cache). Another large change is that the cache block size can no longer be fixed. We must use a block size which is at least as large as the filesystem block size so that FALLOC_FL...

The same as qemu's copyonread flag, this caches read requests. --- filters/cache/nbdkit-cache-filter.pod | 11 +++++ filters/cache/cache.c | 37 +++++++++++++-- tests/Makefile.am | 4 +- tests/test-cache-on-read.sh | 66 +++++++++++++++++++++++++++ 4 files changed, 114 insertions(+), 4 deletions(-...

v3 was broken by a bad rebase, so let's forget about that one. Compared to v2: - Patch 1 is the same except for a minor comment change. - Patch 2 splits the reclaim code into a separate file (filters/cache/reclaim.c) - Addressed Eric's comments from his review of v2. - Retested on Linux and FreeBSD.

The new cache=none mode is misleading since it does not avoid usage of the page cache. When using shared storage, we may get stale data from the page cache. When writing, we flush after every write which is inefficient and unneeded. Rename the cache modes to: - writeback - write complete when the system call re...

...gt; > > On 2 Nov 2018, at 20.58, Poliman - Serwis <serwis at poliman.pl> wrote: > > I have a problem for specific mailbox. In mail.err file I see a lot: > > Nov 2 07:41:17 s1 dovecot: imap(artur at example.pl): Error: unlink(/var/vmail/example.pl/artur/Maildir/dovecot.index.cache) failed: No such file or directory (in mail-cache.c:28) > Nov 2 07:41:17 s1 dovecot: imap(artur at example.pl): Error: Corrupted index cache file /var/vmail/example.pl/artur/Maildir/dovecot.index.cache: Broken MIME parts for mail UID 2356 in mailbox INBOX: Cached MIME parts don't match mess...