search for: thrashes

On Wed, 8 Feb 2017 15:59:16 -0600 Paul Klapperich via samba <samba at lists.samba.org> wrote: > I have a FreeNAS 9.3 server running Samba Version 4.3.6 and a bunch of > Windows and Linux clients. Everything's been running fine for a while > and nothing changed on the server. > > Recently (Jan 27th) some of the Archlinux clients updated from a 4.8.x > kernel to a 4.9.x

I have a FreeNAS 9.3 server running Samba Version 4.3.6 and a bunch of Windows and Linux clients. Everything's been running fine for a while and nothing changed on the server. Recently (Jan 27th) some of the Archlinux clients updated from a 4.8.x kernel to a 4.9.x kernel. Again, things ran fine. Then on Jan 30th around 2am the Archlinux clients using 4.9.x kernels and utilizing mount.cifs to

On Wed, 8 Feb 2017 20:15:05 -0600 Paul Klapperich via samba <samba at lists.samba.org> wrote: > Well that was easier than I thought. Here's the default config > provided by archlinux's samba package, but with "deadtime = 1" > included. With this config, shares mounted via mount.cifs thrash on > port 445 after a few minutes. I think the reconnect logic in the

Rsync thrashes my buffer cache when transfering large files. I see that some people worked on this problem about a year ago. Did they find a workable solution? I'm getting tired of everything slowing to zero while rsync grinds away. Josh Snyder -------------- next part -------------- HTML attachment scrub...

At some stage (possibly commit r17268) oggpack_writecopy started to fail with some strings longer than 256 bytes and all strings longer than 512 bytes. Also it thrashes the stack with very long strings. Lithopsian

Sent 12 hours ago and it never showed up (slightly reworded here). Sorry if this is a duplicate: --------------------------------------------- Scenario: a person selects an Auto Attendant option that fires off the Directory application (CVS circa 3/22). Three questions: 1) How do they escape if they didn't mean to go there in the first place (without having to hang up...)? Config of

...been more of a challenge then I expected. Anyway, from a Windows ME box, printing from applications happens quickly and transparently without a hitch. But, I have another client machine that is a Windows 2000 box. When printing a document from Word (or excel...), the Win 2000 box absolutely thrashes our network. The box itself becomes sluggish and Word becomes unuseable for 7 to 10 minutes. After that period of time, the document will print. But as you can imagine, that doesn't go over too well with the user of the Win 2000 box. During that time the utilization of our 100Mb network...

Very well. Here is the affected smb.conf. ------ [global] server min protocol = NT1 server max protocol = SMB3 interfaces = 127.0.0.1 10.0.0.8 bind interfaces only = yes encrypt passwords = yes dns proxy = no strict locking = no oplocks = yes deadtime = 15 max log size = 51200 max open files = 2830016 logging = file load printers = no

On 25/11/2014, isdtor <isdtor at gmail.com> wrote: > We recently started upgrading users' workstations to CentOS6. Now > we've come across an interesting issue: > ~user/.local/share/gvfs-metadata is filling up with tons of files. > Once there are around 69270 of them, no more are being created, and > the NetApp filer the user's home is on logs: > > Directory

Does R do its own swapping out to disk? I disabled Linux swapping and the system still gets stuck in Purgatory where there's little CPU activity but the disk goes like crazy. That's with R having almost the whole machine to itself and running a memory hungry compute only function. I've seen this behavior with other version numbers but I'm running R 2.0.0 under Fedora Core 3.

On Wed, 8 Feb 2017 16:43:53 -0600 Paul Klapperich via samba <samba at lists.samba.org> wrote: > Very well. Here is the affected smb.conf. > ------ > [global] > server min protocol = NT1 > server max protocol = SMB3 > interfaces = 127.0.0.1 10.0.0.8 > bind interfaces only = yes > encrypt passwords = yes > dns proxy = no > strict

I think it should be neither. Ugh... FreeNAS UI doesn't let me disable the Domain Logons setting for some reason, so I'll have to talk to them on that one and it seems they have no option for me to modify the server role. Thankfully I can edit smb.conf directly on the archlinux box where I was able to duplicate the issue. Setting sever role = auto, domain logons = yes doesn't fix the

okey doke. I have read the faq, I have browsed the samba web sites, and I did go through diagnose.txt and the other documentation but still... none of the win95 boxes on my network can see my samba server in the network neighborhood. usage of "net use x: \\server\share" seem to work fine on the client machines though as well as everything else in the diagnose.txt document. Could

>On Sunday 14 June 2009 14:09:33 Wesley W. Terpstra wrote: >> On Sun, Jun 14, 2009 at 10:50 AM, Florian Weimer<fw at deneb.enyo.de> wrote: >> > Is this really a problem for MLton? I think you only get less precise >> > alias analysis, and that's it. >> >> Correct. However, I want a fair comparison between LLVM performance >> and the native x86

We recently started upgrading users' workstations to CentOS6. Now we've come across an interesting issue: ~user/.local/share/gvfs-metadata is filling up with tons of files. Once there are around 69270 of them, no more are being created, and the NetApp filer the user's home is on logs: Directory ..../user/.local/share/gvfs-metadata/ reached the maxdirsize limit. Reduce the number of

Le 09/09/2017 ? 15:14, Robert Nichols a ?crit : > Every system that runs continuously for more that a few days will have > some pages that were used once when some long-running process started > and were never referenced again. Those pages will eventually migrate out > to swap, and that's the best place for them. Right now, I see that this > system has been up for 16 days and

I'm thinking about ways to improve the Xen balloon driver. This is the driver which allows the guest domain to expand or contract by either asking for more memory from the hypervisor, or giving unneeded memory back. From the kernel's perspective, it simply looks like a driver which allocates and frees pages; when it allocates memory it gives the underlying physical page back to the

I'm thinking about ways to improve the Xen balloon driver. This is the driver which allows the guest domain to expand or contract by either asking for more memory from the hypervisor, or giving unneeded memory back. From the kernel's perspective, it simply looks like a driver which allocates and frees pages; when it allocates memory it gives the underlying physical page back to the

So, as you all probably noticed, the APIs for creating constants have been moved (or in a specific cases, are about to be moved) from static methods on Constant to instance methods on LLVMContext. However, as was recently pointed out on llvm-commits and on IRC, this is no longer strictly necessary. Because types have contexts, all of the constant subclasses could be friended to

Well that was easier than I thought. Here's the default config provided by archlinux's samba package, but with "deadtime = 1" included. With this config, shares mounted via mount.cifs thrash on port 445 after a few minutes. I think the reconnect logic in the kernel's CIFS client is broken. Should I report this on the kernel mailing list? ----- # This is the main Samba