search for: worrisom

We finally seem to have worked most of the kinks out of our OCFS/RAC setup, and are running a mass import to clone our production database for testing. While this has been going on, I fired up ocfstool to check out the states of the various shared volumes. In several cases, I saw (in the File Listing tab) multiple entries for some directories and files at the filesystem root. The duplicate

Rsync people, Tell me if I'm wrong, but rsync seems to have a very serious race condition that would make it risky to transfer files into a directory writable by someone you don't trust if permissions are going to be granted to other people on those files. The rsync receiver creates a half-transferred file with 600 or 700 permissions; then the receiver writes the data and finalizes the

Hi guys, Sorry for the OT. For the last couple of weeks I notice that the static in my server room is worrisomely noticeable. I cannot see what may be causing it.... Care to share some of your experience what may be the cause and the remedy? Thank you.

.... The culprit is /usr/lib64/mozilla/plugins/librhythmbox-itms-detection-plugin.so It appears that whoever maintains the rhythmbox RPM has chosen not to package the browser plugin separately like it probably should be. So if I have the rhythmbox RPM installed, I have the plugin. This is rather worrisome because I can find no trace of the plugin in the Mozilla preferences panel, so if it is there it is very well hidden and if it really isn't there, it can't be disabled there. Is there some kind of blacklist file I can put in /usr/lib64/mozilla/plugins/ or ~/.mozilla/plugins/ to specifi...

...ows xp. I was testing one of my registration forms and it worked fine when mongrel_rails was run on the windows machine, but when mongrel was run on os x it kept throwing "ActionController::InvalidAuthenticityToken". I realized I had forgotten the <%= token_tag %>, but it''s worrisome that when the server was run on xp it took the form happily. What''s going on? Thanks! Abhik --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send e...

...ndler Carruth <chandlerc at google.com> wrote: > > Perhaps you're instead trying to say that with certain address spaces "noalias" (and by inference, "restrict" at the language level) has a different semantic model than other address spaces? While it's less worrisome than the first interpretation, I still don't really like it. > This sounds right. With the constant address space, anything you do is OK since it’s constant. Private address space is supposed to be totally inaccessible from other workitems, so parallel modifications aren’t a concern. The...

...second dc reported 5476 objects last dc (the one with all the fsmo roles, etc.)? reported 1406 objects! now all of them report 1406 objects. (drs replication obviously) ADUC, DNS, GPO manager all seem to have the requisite data. I THINK all the users and computers are there. but that reduction is worrisome. Was it all cruft? I have no way of knowing. Some reassurance or alarm would help. Ray

...<chandlerc at google.com> wrote: > >> >> Perhaps you're instead trying to say that with certain address spaces "noalias" (and by inference, "restrict" at the language level) has a different semantic model than other address spaces? While it's less worrisome than the first interpretation, I still don't really like it. >> > > This sounds right. With the constant address space, anything you do is OK since it’s constant. Private address space is supposed to be totally inaccessible from other workitems, so parallel modifications aren’t a...

...uth <chandlerc at google.com> wrote: >> >>> Perhaps you're instead trying to say that with certain address spaces "noalias" (and by inference, "restrict" at the language level) has a different semantic model than other address spaces? While it's less worrisome than the first interpretation, I still don't really like it. >>> >> This sounds right. With the constant address space, anything you do is OK since it’s constant. Private address space is supposed to be totally inaccessible from other workitems, so parallel modifications aren’t...

...rnel vmlinuz-3.10.0-229.1.2.el7.x86_64, among many other things. When I rebooted, I was asked to confirm (or renew, or some such) my license. My LICENSE ??? I was booting in text mode and the actions required were a) unfamiliar, and b) hard to understand. As I recall, I had to read the EULA - a worrisomely Microsoftian demand - and accept it. Of course, the terms were pretty benign. Then I had to continue. I can't remember the exact language. Of course, now when I reboot, all this cruft is gone. Is this a cute April Fool joke? If not, WTF is going on? -- David A. De Graaf DATI...

...ces in the memory model. I'm not very comfortable with that. Perhaps you're instead trying to say that with certain address spaces "noalias" (and by inference, "restrict" at the language level) has a different semantic model than other address spaces? While it's less worrisome than the first interpretation, I still don't really like it. > This comes back to the questions about how to handle address space alias > information which there was a long thread about a few months ago. There was > debate over address spaces as a language vs. a target concept, and...

On 12/10/2016 07:51, Aki Tuomi wrote: > Please make your patch, if possible, viahttps://github.com/dovecot/core > as pull request. I am not really git "schooled", but I shall look into that. Many Thanks for being open to a "non-gcc" compiler! Michael

On 09/20/2016 03:54 PM, Bob of Donelson Trophy via samba wrote: > All of us are having trouble with the "Anniversary update" to W10 > Version 1607. If you can roll back to previous Version 15?? (sorry can't > remember) that MIGHT correct your issue. No promises. It's definitely that update that caused the problem.

...destroy child objects > err:seh:setup_exception nested exception on signal stack in thread 0009 > eip 7ffd7ff0 esp 7fe95cfc stack 0x7f900000-0x7fa00000 > > and then the window pops up. > I've the same error under Debian sid with gcc4 > Jesse meant that should be something worrisome and thats why i should > post it here. > > He also said that might be related to GCC4. This is a gcc4-debian-wine pb. I've tried last night to compile with CC set to gcc3-3 and it worked without problem (if you negligeate the fact that I've forgotten to put opengl-dev lib on...

...again... My thought is that Linux ran out of memory (only 40MB physical, but 300MB of swap space). It did last 8 hours in full production use with 2.2.8, so I am not sure that it is an issue with 2.2.8 over 2.2.7. I rebooted, which took 3(???????) tries before LILO took charge. This is especially worrisome. Why would it not boot straight away? Is the above error possibly due to failing hardware? Brent Torrenga brent.torrenga@torrenga.com

...ind (although I'm sure there are a few left I'll tackle when there are reports), and the LNT numbers look *really* good. Here is the latest LNT run we got by flipping it on and back off: http://llvm.org/perf/db_default/v4/nts/3963 Most of this is very, very green. There are three somewhat worrisome regressions in execution time: 1) sse_expandfft -- when I build this, the binaries have no differences before and after 2) sse_stepfft -- ditto 3) matmul_f64_4x4 -- this one is interesting The last one represents the only real regressions I expect to see with the new pass. There is a helpful ind...

...tion? To summarize: a <- lmer(Response~Fixed Effects+(1|Subject)+(1|Item),data,binomial) b <- lmer(Response~Fixed Effects+(1|Item),data,binomial) a has a much better fit by any measure, and estimated scale around 0.85. b has a worse fit, but estimated scale around 1. Obvious? Interesting? Worrisome? Thanks, Dan

...not know enough to determine if it's a bug or security > issue. I don't see either of those. I just try to open a share in the Konqueror browser. I can see the Users folder, but nothing below it. > > Hope to have time later today to test further however, the situation is > worrisome. >

...hort *' to 'float *' e:\phonestack\engine\speex\nb_celp.c(875) : warning C4761: integral size mismatch in argument; conversion supplied e:\phonestack\engine\speex\nb_celp.c(1603) : warning C4761: integral size mismatch in argument; conversion supplied of these, the last two are not worrisome. but the first error is forcing a short pointer to a float. any clue as to what is going on? - farhan

...null. If you put it into a data section, it takes up 10k in the executable (unless Darwin has some unusual data section); it takes up no space at all in the BSS. So naturally we'd prefer to put it in the BSS... for a 1 byte string that doesn't really matter, though. The thing that seems worrisome that you're depending on choices that could be made arbitrarily; no matter where the string is, it normally doesn't change the semantics of the program. In certain situations, it could be a profitable transformation to, for example, put a string on the stack. If the runtime environment i...