search for: hiccough

I spoke a bit too soon about the upgrade being flawless. It turns out that one subsystem started failing after the upgrade, although it is not an out-of-the-box one. I've included the description here in case someone runs into something similarly weird (especially with scripts calling MySQL?) and because although I have a work-around, I'm not sure (but can guess) as to the actual cause

...ABC123456789>): DNS lookup for mailboxserver.domain.com took 1.550 s If you are seeing a warning that dans lookup took 1.5 seconds 5-6 times a day, why are you concerned? > I do not really understand how from time to time DNS queries are slow, Because from time to time, queries are slow. A hiccough in the line, the server is slightly busy doing something else. There?s a lot of bandwidth during those 1.5 seconds being used. It could be anything. If you were seeing hundreds of these warning, or if the times were over 5 seconds, then I?d worry. > I tried replicate this issue using dig to re...

Hello, I am running a dovecot and proxy server on two different virtual machines and on the dovecot proxy server I see around 5-6 times per day the following warning: Feb 03 16:15:12 auth: Warning: proxy(email at domain.com,xxx.xxx.xxx.xxx,<ABC123456789>): DNS lookup for mailboxserver.domain.com took 1.550 s I do not really understand how from time to time DNS queries are slow, I tried

...ere from 2 to 44 dropped frames out of 200 with ext3. (The worst ext3 numbers came while overwriting already existing files.) Zero dropped frames with XFS. Nadda. None. After the first few clear XFS tests I put extra load on the machine while the tests were running to see if that would make XFS hiccough - copying large files around internally, spawning CPU-eating programs. It didn't. Well... not until I threw a fork bomb at it, anyway. <smirk> But even then, it kept on chuggin' till the load average was somewhere over 900. Conclusion, clear as a bell: XFS for high-bandwidth data...

...ABC123456789>): DNS lookup for mailboxserver.domain.com took 1.550 s If you are seeing a warning that dans lookup took 1.5 seconds 5-6 times a day, why are you concerned? > I do not really understand how from time to time DNS queries are slow, Because from time to time, queries are slow. A hiccough in the line, the server is slightly busy doing something else. There?s a lot of bandwidth during those 1.5 seconds being used. It could be anything. If you were seeing hundreds of these warning, or if the times were over 5 seconds, then I?d worry. > I tried replicate this issue using dig to res...

...kup for mailboxserver.domain.com took 1.550 s > > If you are seeing a warning that dans lookup took 1.5 seconds 5-6 times a day, why are you concerned? > >> I do not really understand how from time to time DNS queries are slow, > > Because from time to time, queries are slow. A hiccough in the line, the server is slightly busy doing something else. There?s a lot of bandwidth during those 1.5 seconds being used. It could be anything. If you were seeing hundreds of these warning, or if the times were over 5 seconds, then I?d worry. > > >> I tried replicate this issue usi...

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20040920/0629df7b/signature-0001.pgp

I've been asked for ideas on building a rather large archival storage system for inhouse use, on the order of 100-400TB. Probably using CentOS 6. The existing system this would replace is using Solaris 10 and ZFS, but I want to explore using Linux instead. We have our own tomcat based archiving software that would run on this storage server, along with NFS client and server. Its a

..._defendable_ BOE on how long the task will take, but there is a significant probability that I will not have executable code that generates a correct assembly file. If someone else has already implemented something similar (or decided not to) and that project has shared lessons-learned, timelines, hiccoughs, anything, then that information could help me better communicate with my superordinates, perhaps manage their expectations, possibly add value to my implementation. If a similar project took two years, then my superordinates might be happier with what I'm able to accomplish in six weeks. Of...

-- Juergen Gross Principal Developer IP SW OS6 Telephone: +49 (0) 89 636 47950 Fujitsu Siemens Computers e-mail: juergen.gross@fujitsu-siemens.com Otto-Hahn-Ring 6 Internet: www.fujitsu-siemens.com D-81739 Muenchen Company details: www.fujitsu-siemens.com/imprint.html _______________________________________________

Thanks, no malloc or free equivalents either (no heap). So, there are no others (to your knowledge) who have built an LLVM backend for a platform with no “normal” stack? I found a presentation about some FPGA work (using LLVM) but it doesn’t seem to apply to my platform. Perhaps someone else on the mailing list will have come across this rarity? Thank you again for your time and