search for: releae

I have tried small ruby program like require ''rubygems'' require ''postgres'' db = PGconn.connect(''localhost'', 5432, '''', '''', ''prdjnj'',''postgres'', ''postgres'') res=db.exec("select * from users limit 300000") res.clear puts "After clear result

...or the icecast2 HTTP login would be a good idea > though, the other logins IIRC are best guesses to what the other > servers accept. If your talking about a icecast2-yellowpages-procotol-docu: I had the same impression that there is no current docu available and wrote one. But as soon as I releaed it via mailinglist somebody pointed me to a "hidden" document by Oddsock. It's at: http://www.oddsock.org/icecast2yp/spec.html Don't no why there is no link to it somewhere. Maybe because it's "not finished" yet. But I personally rate it quite helpful. Maybe it...

Just a note that the 3.3 development release notes (ftp://shorewall.net/pub/shorewall/development/3.3/shorewall-3.3.0/relea senotes.txt) have a typo under the Migration Considerations. <current> /etc/shorewall/accounging. </current> <fixed> /etc/shorewall/accounting. </fixed. Regards, - Craig.

For those who did not get the annoucement. CuteFTP is now claiming to support sftp as stated in the RFC. And at first glace it *SORTA* works.=) I can upload files, but the directory listings are broken (it does not display anything) and as a result download won't work (since cuteftp rquires the file to be in the directory listing to get). I'm going to back down a releas of

...ting to xen-44 and not xen-46) then a 'yum upgrade' > should replace all the needed packages. > > The actual path is here for the packages: > > https://buildlogs.centos.org/centos/6/virt/x86_64/xen-44/ > > Hopefully this helps. > I should have said .. 'just releaed for testing' :) I have been using this for 4 or 5 days with no issues in production, but it needs testing before final release :) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: OpenPGP d...

qxl expects that list_first_entry(release->bos) returns the first element qxl added to the list. ttm_eu_reserve_buffers() may reorder the list though. Add a release_bo field to struct qxl_release and use that instead. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/qxl/qxl_drv.h | 1 + drivers/gpu/drm/qxl/qxl_cmd.c | 6 ++----

The initial problem I was seeing after upgrade from 2.0beta5 to 2.0beta6 was error messages from my Android phone K9 client that dovecot was reporting -1 messages in various mailboxes. These mailboxes do have the special "Mail System Internal Data" message in them. In trying to get more information for debugging, I tried toenable rawlog using the same configuration I used successfully

>Hello everyone, > >I have added a new public LLD performance builder at >http://lab.llvm.org:8011/builders/lld-perf-testsuite. >It builds LLVM and LLD by the latest releaed Clang and runs a set of >perfromance tests. > >The builder is reliable. Please pay attention on the failures. > >The performance statistics are here: >http://lnt.llvm.org/db_default/v4/link/recent_activity > >Thanks > >Galina Great news, thanks ! Looking on results...

...ce all the needed packages. >>> >>> The actual path is here for the packages: >>> >>> https://buildlogs.centos.org/centos/6/virt/x86_64/xen-44/ >>> >>> Hopefully this helps. >>> >> >> >> I should have said .. 'just releaed for testing' :) >> >> I have been using this for 4 or 5 days with no issues in production, but >> it needs testing before final release :) > > Currently I've moved most of my servers onto the 4.4 kernel from xen > made easy and they've been stable. I have s...

Hello: I am wondering if KVM is ready for production for running a Windows Server 2003 32 bit guest. According to the RHEL 5.4 virtualization guide, there is supposed to be a virtio-win yum package, but that was not released. Instead, it looks like that is only available for RHN subscribers. Also, I saw this posting on the CentOS list: --- Quoted from CL Martinez There are freely

Thanks John for the super quick checkin. I was a little surprised here. Yesterday/today I spent some time trying to build poolalloc on my mac dev machine. Unfortunately, it failed to build [1]. Looks like the compiler can't find the header files under /usr/include/c++. I also tried to build on my linux box and saw the same problem. giri built successfully. Are you sure poolalloc builds on

On 10/9/11 12:12 AM, Jinwook Shin wrote: > Thanks John. I appreciate your help and I look forward to obtaining the code. > > A proper LLVM sub-project: No rush on this and please take your time. Thanks. Okay, I've created a new LLVM sub-project called Giri(*). It currently contains only the static backwards slicing pass. I'll add the dynamic slicing code to the project later.

Hi there, I have this build error on OpenBSD-4.4-current: llvm[3]: Compiling X86TargetAsmInfo.cpp for Release build In file included from /usr/ports/devel/llvm/w-llvm-2.4/llvm-2.4/lib/Target/X86/X 86TargetAsmInfo.cpp:14: /usr/ports/devel/llvm/w-llvm-2.4/llvm-2.4/lib/Target/X86/X86TargetAsmInfo.h: In constructor `llvm::X86TargetAsmInfo<BaseTAI>::X86TargetAsmInfo(const

The PIC16 is an 8-bit target but under the "LLVM IR and Core Improvements"heading it's called a 16-bit target. --John > ---------- Forwarded message ---------- > From: Chris Lattner <clattner at apple.com> > To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Date: Sat, 10 Oct 2009 15:14:21 -0700 > Subject: [LLVMdev] 2.6 release notes > Hi

On Mon, Jun 17, 2019 at 5:27 AM Christoph Hellwig <hch at lst.de> wrote: > > Hi Dan, Jérôme and Jason, > > below is a series that cleans up the dev_pagemap interface so that > it is more easily usable, which removes the need to wrap it in hmm > and thus allowing to kill a lot of code > > Note: this series is on top of the rdma/hmm branch + the dev_pagemap > releas

...yum upgrade' >> should replace all the needed packages. >> >> The actual path is here for the packages: >> >> https://buildlogs.centos.org/centos/6/virt/x86_64/xen-44/ >> >> Hopefully this helps. >> > > > I should have said .. 'just releaed for testing' :) > > I have been using this for 4 or 5 days with no issues in production, but > it needs testing before final release :) Currently I've moved most of my servers onto the 4.4 kernel from xen made easy and they've been stable. I have some indications of an issu...

...> >>>> The actual path is here for the packages: >>>> >>>> https://buildlogs.centos.org/centos/6/virt/x86_64/xen-44/ >>>> >>>> Hopefully this helps. >>>> >>> >>> >>> I should have said .. 'just releaed for testing' :) >>> >>> I have been using this for 4 or 5 days with no issues in production, but >>> it needs testing before final release :) >> >> Currently I've moved most of my servers onto the 4.4 kernel from xen >> made easy and they've...

...all && rm -rf /var/cache/yum yum upgrade yum upgrade yum distro-sync package-cleanup --orphans cd .. && rm -rf TMP I am not sure, what?s the deal with /usr/share/redhat-release\* files/symlinks, but they stood in a way, so I had to remove them. Also, the redhat-releae\* package could be -workstation, -server, -computernode, or -client. Any comments? Best, Mat?j -- https://matej.ceplovi.cz/blog/, Jabber: mcepl at ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 "Push to test." (click) "Release to detonate..." --...

On Mon, Aug 04, 2003 at 08:14:21AM +0200, Stefan Neufeind wrote: > > If your talking about a icecast2-yellowpages-procotol-docu: I had the > same impression that there is no current docu available and wrote > one. But as soon as I releaed it via mailinglist somebody pointed me > to a "hidden" document by Oddsock. It's at: > http://www.oddsock.org/icecast2yp/spec.html > > Don't no why there is no link to it somewhere. Maybe because it's > "not finished" yet. But I personally rate it...

...n 1.2.12 and latest zaptel modules. but i can see some IRQ conflicts on the server. iam uisng two TDM04B cards. according to my previous knowledge on asterisk verison 1.07 asterisk has given lot of erros when starting if you have assigned the same IRQ number to any other device. My question is new releae version 1.2.12 has resolved the IRQ issue ?? TDM04B cards can share IRQ with another device. or should it have a unique IRQ for porper performance. any drawbacks with using the shared IRQ ? i mean random call hangups../..echo..etc ( i can start my asterisk verison even with IRQ sharing..but earlie...