similar to: Samba 4.16 sends files in bursts.

I have done some searching on the Internet, but not been able to find a solution to my problem. I hope you can help me with this. I have a server at home that runs on FreeBSD 10.3. The file system is ZFS. I have two ZFS pools: tank and fun. I share my ZFS file systems using Samba v4.6.2. When I add recycle bin functionality for a share like below, it work like a charm: [mac] path =

Hai, Now, i must say, i know nothing about freebsd or zfs. But try these in this order, check what you also use in you global config. vfs objects = zfs_space zfsac catia fruit recycle streams_xattr aio_pthread This should be Zfs and mac compatible. There was a bug which had todo with the loading order of the vfs modules. But if im wrong here, i hope someone on the list corrects me.

Hi From reeBSD 9.3-RELEASE amd64: Compiles ok Installs ok On startup 1: Error about new config settings (adjusted) On startup 2: doveadm(root): Error: net_connect_unix(/var/run/dovecot//stats-writer) failed: Connection refused It seems to work so far. I get messages from fetchmail being delivered to the mailbox, yet that stale error is there. Quick search did not showed any results. Not looked

Found the guide .... Can you remove last entry please ... works with TLSv1. Thanks and regards Goetz R. Schultz On 18/12/17 20:05, Goetz Schultz wrote: > Hi > > From reeBSD 9.3-RELEASE amd64: > > Compiles ok > Installs ok > On startup 1: Error about new config settings (adjusted) > On startup 2: doveadm(root): Error: >

Hi Odhiambo, I referred to this: "Not looked yet, but is there a guide for the ssl_min_version setting? Seems only to wok when I set "SSLv3" which I really don't want." Have found literally 10 minutes after the post was send - so ignore that bit. It is just that error error that creeps up. But not using stats, hence I assume that is fine then. Thanks and regards

Hi Goetz, I don't seem to understand what you mean by 'remove the last entry'. Do you mind clarifying please? On 18 December 2017 at 23:12, Goetz Schultz <email at suelze.de> wrote: > Found the guide .... Can you remove last entry please ... works with TLSv1. > > > Thanks and regards > > Goetz R. Schultz > > On 18/12/17 20:05, Goetz Schultz wrote:

Okay, I was hoping it has something to do with where I am stuck compiling. Could you kindly share your configure options? Mine which has always worked with Dovecot versions prior to 2.3 is refusing to work on FreeBSD i386. <cut> mv -f .deps/test_auth_cache-test-auth-cache.Tpo .deps/test_auth_cache-test-auth-cache.Po clang -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-auth

Apologies for bumping Joseph Tam's rather old thread, but I'm wondering if anyone has come up with a workaround/fix for this problem that iOS Mail.app clients (10.3.3, 11.0.3, 11.1?) continue to exhibit? Robert On 10/28/2016 at 03:49 PM, Joseph Tam wrote: > I frequently see this from my iPhone/iPad IMAP users: > > ????Oct 24 21:30:55 server dovecot: imap-login: Login:

On 30/11/17 03:03, Robert Giles wrote: >> David, >> >> I'd say that if you set the mail_max_userip_connections value to a >> large-ish number (300-400), your users likely won't notice an issue on >> their iOS 10.x and iOS 11.x devices.? It's more of an annoyance in the >> logs, and occasionally the iOS Mail app will show that it is stuck >>

"David.M.Clark" <david at davrom.com> wrote: > I have modified mail_max_userip_connections to 400 which made no difference. > > The end user customer actually had Apple remote into their device and > they were impressed that the end user knew their IMAP settings. They > tested it and during this connection time, it worked as expected with > send and receive

> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15: NV5 in another PC (secondary card in x86-64) made the systrem crash on boot, in nvkm_therm_clkgate_fini. -- Meelis Roos (mroos at linux.ee)

On Wed, Feb 14, 2018 at 9:35 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Wed, Feb 14, 2018 at 9:29 AM, Meelis Roos <mroos at linux.ee> wrote: >>> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15: >> >> NV5 in another PC (secondary card in x86-64) made the systrem crash on >> boot, in nvkm_therm_clkgate_fini. > > Mind

Actually this was brought up to me already, there's a fix on the mailing list for this I reviewed a little while ago from nvidia that we should pull in: https://patchwork.freedesktop.org/patch/203205/ Would you guys mind confirming that this patch fixes your issues? On Wed, 2018-02-14 at 18:41 +0100, Pierre Moreau wrote: > On 2018-02-14 — 09:36, Ilia Mirkin wrote: > > On Wed, Feb

On Thu, 22 Feb 2024 20:28:18 +0300 Michael Tokarev via samba <samba at lists.samba.org> wrote: > 22.02.2024 16:39, Arnaud FLORENT via samba: > >>> http://www.corpit.ru/mjt/packages/samba/focal/ > >> > >> Oh.? I did a cleanup of the files in there, and, among various > >> duplicates, also removed 4.16.? Maybe it was too soon :) > >> >

Hi we are using Michael repo on ubuntu focal 20.04 for 4.16 samba branch Thank Michael for sharing theses packages it looks that 4.16 branch is missing since 17/2 will this repository be restored or should we move to samba 4.17? http://www.corpit.ru/mjt/packages/samba/focal/

On Wed, Feb 14, 2018 at 9:29 AM, Meelis Roos <mroos at linux.ee> wrote: >> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15: > > NV5 in another PC (secondary card in x86-64) made the systrem crash on > boot, in nvkm_therm_clkgate_fini. Mind booting with nouveau.debug=trace? That should hopefully tell us more exactly which thing is dying. If you have a

Hi, I'm running a simple test from asterisk towards a public telco switch (AXE10) over E100P. Here is the test case: 1) 30 calls are setup simultainously, 20 sec ringing time. 2) no calls answers (just calling a vacant public tax office :=) 3) Each channel will continue on its own with the same proceedure: ring for 20 sec, then hangup, ring for 20 sec, and so on. Of course this leads to

Thanks for the reply and suggestion Robert. I have now set mail_max_userip_connections to 400 in 20-imap.conf to see if it makes any difference. Late yesterday the customer tested from his office, an older IOS 9 tablet and he had IMAP working in a matter of minutes, so is certainly an newer software version by Apple issue. On 30/11/17 03:03, Robert Giles wrote: > David, > > I'd

On 2018-02-14 — 09:36, Ilia Mirkin wrote: > On Wed, Feb 14, 2018 at 9:35 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > On Wed, Feb 14, 2018 at 9:29 AM, Meelis Roos <mroos at linux.ee> wrote: > >>> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15: > >> > >> NV5 in another PC (secondary card in x86-64) made the systrem