similar to: update: sys_ftruncate call lasting 17 hours on ext3 filesystem from mutt

Several times recently my "mutt" email program has looped for hours at a time in the middle of a sys_ftruncate call. This happens when I use the "$" command to write changes out to my mailbox. It does eventually return from the call and everything seems to have worked ok. But in the meantime the CPU is pegged, $MAIL is locked so I can't receive new mail, and signals to

On December 2, 2018 7:29:38 PM GMT+02:00, raul <raulvior.bcn at gmail.com> wrote: >I have restored original configuration and enabled the ignorelb flag. I > >didn't point out in the original e-mail that after every poweroff the >battery percentage is reported at 40% instead of 100% and charges >slowly again to 100%. Maybe the UPS sends a LB event and shuts down

I have taken out the batteries and measured them with a multimeter. They put out 13V (they are rated 12V 9Ah). Putting them back again and disconnecting the UPS from the mains it is kept on, powering all the connected devices. The shutdowns only occur when the UPS is being monitored. Are you sure it's a battery problem? Do UPS perform further tests when they are being polled for data?

On Dec 1, 2018, at 3:45 PM, raul <raulvior.bcn at gmail.com> wrote: > > The UPS is connected to the following environment: > OS: Debian GNU/Linux 9.6 (stretch) > NUT version: 2.7.4-5 > Device output from lsusb: 0463:ffff MGE UPS Systems UPS > Model name: MGE EllipseMAX 1500 > URLs: >

On Dec 1, 2018, at 10:08 PM, raul <raulvior.bcn at gmail.com> wrote: > >> Also, given that the load is only 12%, double-check that the UPS is not configured for any power saving features that might cause the shutdown ("ECO mode" or similar). NUT does not get a notification for that event the way that it gets a normal LB shutdown notification. > > Are you referring

On Dec 2, 2018, at 7:55 PM, raul <raulvior.bcn at gmail.com> wrote: > > I have taken out the batteries and measured them with a multimeter. They put out 13V (they are rated 12V 9Ah). What sort of load did you have in parallel with the multimeter? (This is why Wolfy mentioned the light bulb: if the battery has developed excessive internal resistance, it will show proper voltages when

Hi everyone, I'm unable to make the account lockout to work properly. & this is driving me mad. I am running samba Version 3.0.23c-1.fc5 as a PDC with openldap 2.3.19 on a fc5 (all packages from yum). I was running a 3.0.21 with the same issue. I'm using as well the Idealx script to manage the LDAP. The fact: I have a very strange behavior. The domain policy have been setup with the

I have restored original configuration and enabled the ignorelb flag. I didn't point out in the original e-mail that after every poweroff the battery percentage is reported at 40% instead of 100% and charges slowly again to 100%. Maybe the UPS sends a LB event and shuts down immediatly as suggested in the manual. But the UPS powered off again. The variables reported by upsc can be found

> If there is no message to NUT, I would consider opening a trouble > ticket with Eaton. It is possible that there is a known issue and/or > a firmware upgrade. What kind of message to NUT? In the log (syslog) there is no other message registered. In nut.log only this appears: > Dec 1 08:10:54 openmediavault upsd[5284]: Data for UPS [ellipsemax] > is stale - check driver >

So I've got a PBX running with one Fritz card with the fcpci module and that works fine, but add another one and... kersplat... Kernel Panic. It boots fine with two cards, but panics as soon as the first fcpci.ko module is 'modprobe'd - I don't even get as far as modprobing the second. Any ideas on what's going on? Should I just back-up to an older version of the fcpci module

samba@samba.org schrieb: > SAMBA Digest 1925 > > For information on unsubscribing see http://samba.org/listproc/ > Topics covered in this issue include: > > 1) UNIX to PC > by Shaun Lennox <shaun@countyfair.co.za> > 2) Connect to exported filesystem from NT via a net use cmd > by "Xia Tian"

Hi All, Setup :- NAS device is running with 2.6.13 kernel and samba 3.0.32.I have connected a 4GB USB flash drive having FAT32.USB drive is available from the windows machine as connected shared drive. >From my windows machine when I am trying to copy the file (>1Gb) to shared USB drive(FAT32).it is giving error as shared USB drive is not reachable. File copy is working fine with small

Full_Name: Stephen Weigand Version: 1.9.0 OS: Mac OS X 10.3.4 Submission from: (NULL) (68.115.89.235) When running an iteratively reweighted least squares program R crashes and the following is written to the console.app (when using R GUI) or to stdout (when using R from the command line): Parameter 5 to routine DSTEIN was incorrect Mac OS BLAS parameter error in DSTEIN, parameter #0,

Ulrich offered to do it instead since I expect he can get it done much faster than me. Instead I'm doing SIToFP and UIToFP. Ulrich said he wasn't going to be able to get to it for a couple of weeks, but that was a week or two ago. Ulrich? -----Original Message----- From: Cameron McInally <cameron.mcinally at nyu.edu> Sent: Tuesday, October 01, 2019 10:21 AM To: Kristof Beyls

I have no example side effects in hand. But LLVM targets a bunch of architectures, and who knows what the future holds. So it may be prudent to not promise too much so as to leave ourselves an escape hatch. Doesn’t LLVM target some chips that have floating point instruction sets that are not IEEE compliant? Can we be certain that no new LLVM target will ever have to jump through hoops to avoid

I believe I have a config problem, but let me first explain what I'm trying to accomplish and then I'll dump all the logs, etc. w2k3 r2 domain server: hilbert.math.purdue.edu samba server: gram.math.purdue.edu realm: MATH.PURDUE.EDU domain: MATH Currently my entire environment is all Solaris, with users stored in LDAP and home directories shared via NFS. I am using Sun's Identity

Well, yes, they are different operations. And, yes, this needs to be corrected. This wasn’t my point. It’s a given. I was getting at the _declared_ absence of side effects and what promises we make to anyone using the new fneg instruction. Is this a promise we want to make? From: Cameron McInally <cameron.mcinally at nyu.edu> Sent: Wednesday, September 26, 2018 2:30 PM To: Kevin Neal

On 5/23/06, Michael Kiermaier <michael.kiermaier@gmx.net> wrote: > On Sunday 21 May 2006 23:31, Neal B. wrote: > > A picture is worth 1000 words, so here is a screenshot: > > > > http://img62.imageshack.us/img62/2783/fplayshot4yy.png > > Hi Neal, > > currently I am looking for a flac-player on Linux that understands internal > cue-sheets. So I am very

Hi List, Have just upgraded from 2.2.7 to 3.0.4 and have a problem with two shares that refuse to show. The other 6 shares appear fine. smb.conf is below - it's an old file from 2.0.x ;) There is a Samba PDC on the network too - 192.168.10.246 this does WINS etc, runs 3.0.1 I have tried; 1. Adding a new share - appears OK 2. Using browsable = yes on the two rogue shares 3. Showing one of

On Tue, Oct 2, 2018 at 12:09 PM Kevin Neal <Kevin.Neal at sas.com> wrote: > If we don’t have constrained intrinsics for some of the fp math > instructions then aren’t we risking non-strict optimizations? > So far we've only added constrained FP intrinsics for operations that have side effects (i.e. can trap). The quiet-computational sign-bit operations are special. They never