similar to: [LLVMdev] Downtime for Installing New Certificate

Dear All, Some of you may have noticed that our SSL certificate expired about half an hour ago. We have a new SSL certificate, but we haven't had time to install it. I am going to attempt to install the new certificate. This will necessitate one server restart if I am successful and probably two if I'm not. Chances are that you will not notice any disruption, but if you're the

Dear All, The good news is that the new llvm.org SSL certificate is installed and appears to be configured correctly. The bad news is that some machines seem to recognize the intermediate SSL certificate (which is apparently used to sign the SSL certificates UIUC buys starting this year) while others do not. In particular, our internal Linux machines show no errors, while our Macs and

Dear All, The llvm.org server will be down for about 15 minutes starting at 10 am CST on Friday. Our IT people will be replacing a bad RAM module. If there's any serious problem with doing the RAM replacement at 10 am, please email llvmdev. I picked 10 am because I'd like the RAM module replaced ASAP, and I doubt 10 am tomorrow will be a problem. -- John T.

Any issues with permanently accepting the intermediate certificate, which I did this morning, when getting the message? Thanks in advance Garrison On Jun 29, 2011, at 12:13, John Criswell wrote: > On 6/28/11 3:56 PM, John Criswell wrote: >> Dear All, >> >> The good news is that the new llvm.org SSL certificate is installed and >> appears to be configured

On 6/28/11 3:56 PM, John Criswell wrote: > Dear All, > > The good news is that the new llvm.org SSL certificate is installed and > appears to be configured correctly. As a followup to this, I discovered that I was using the MacPorts version of the svn client on our Mac OS X system. Using the svn client in /usr/bin/svn seems to recognize the certificate just fine. The pattern that

John Criswell wrote: > Dear All, > > Some of you may have noticed that our SSL certificate expired about half > an hour ago. We have a new SSL certificate, but we haven't had time to > install it. > > I am going to attempt to install the new certificate. This will > necessitate one server restart if I am successful and probably two if > I'm not. > >

I testing Puppet 0.19.3. If we decide to use it, we''d deploy it across several thousand hosts. The method described for creating client certificates described in the documentation - running "puppetd --server <server> --waitforcert 60 --test" and "puppetca --sign <client>" - is not practical for our installation. I''ve tried creating

On 3/14/19 9:55 AM, Patrick Cernko via dovecot wrote: > [...] the way we have configured exim, it neither needs reload or > restart but reads the certificate file every time it has to use it. What happens if you goof off in the middle of an opeartion, temporarily putting a wrong file instead of the new certificate, and exim starts delivering the new broken certificate right away ? or

Dear LLVM Developers/Users, We will be performing some upgrades on llvm.org on Monday, June 24. The upgrades are scheduled to begin around 11:00 am Central Time and should take 3-4 hours. During most of this time, llvm.org services (LLVM web page, CVS repository, etc) will either be slow or unavailable. The machine will also be undergoing an IP address change due to some recent network

All, The server that runs the mailing lists will be down for maintenance starting Friday Dec 18th at 10:30PM PST. I do not expect a long downtime, but please keep this in mind if you see any issues with the lists during this period. I will send an email once I am finished. No other services should be affected. Thanks, Tanya

Any idea when it would be back up? We are in release crunch mode here. Not having access to the CVS server is a bit inconvenient. :-) Thanks, Evan On Jul 22, 2006, at 7:22 AM, John T. Criswell wrote: > Dear LLVM Developers/Users, > > We will be performing some upgrades on llvm.org on Monday, June > 24. The upgrades are scheduled to begin around 11:00 am Central > Time and

I'll be upgrading the SVN server on llvm.org this Friday from 9pm - whenever I am done. You will notice that all web and of course svn services will be down during this time. Thanks, Tanya

CVS isn't working for me still. Anyone else having problem? Evan On Jul 24, 2006, at 8:16 PM, John Criswell wrote: > Evan Cheng wrote: >> Any idea when it would be back up? We are in release crunch mode >> here. Not having access to the CVS server is a bit inconvenient. :-) > Indeed. > > I've fixed a minor problem with the OS upgrade, and CVS services >

The website isn't working for me. -bw On Jul 24, 2006, at 9:49 PM, Evan Cheng wrote: > CVS isn't working for me still. Anyone else having problem? > > Evan > On Jul 24, 2006, at 8:16 PM, John Criswell wrote: > >> Evan Cheng wrote: >>> Any idea when it would be back up? We are in release crunch mode >>> here. Not having access to the CVS server is

Just FYI, I will be upgrading to 1.7.1 (from 1.5.4). Thanks, Tanya On Oct 26, 2011, at 3:05 PM, Tanya Lattner wrote: > I'll be upgrading the SVN server on llvm.org this Friday from 9pm - whenever I am done. > > You will notice that all web and of course svn services will be down during this time. > > Thanks, > Tanya > _______________________________________________

Going down now. I'll send mail when its back up. -Tanya On Oct 26, 2011, at 3:12 PM, Tanya Lattner wrote: > Just FYI, I will be upgrading to 1.7.1 (from 1.5.4). > > Thanks, > Tanya > > On Oct 26, 2011, at 3:05 PM, Tanya Lattner wrote: > >> I'll be upgrading the SVN server on llvm.org this Friday from 9pm - whenever I am done. >> >> You will

On 3/14/19 9:32 AM, Yassine Chaouche via dovecot wrote: > The general answere here is try and see, as you could totally test it > on your own. The certificate is read at startup and put in memory for > the rest of the execution time. Dovecot won't monitor the file for > changes on disk, as this would waste CPU cycles and make dovecot only > slower for no reason. The process

Evan Cheng wrote: > Any idea when it would be back up? We are in release crunch mode here. > Not having access to the CVS server is a bit inconvenient. :-) Indeed. I've fixed a minor problem with the OS upgrade, and CVS services seem to be working again. You should be able to checkout and make commits (provided you have commit access, of course) using the LLVM CVS repositories.

Dear All, The LLVM network services (llvm.org web site, SVN server, etc.) will be offline starting at 10:30 am Central Time on Tuesday, March 8. We are moving the machine hosting these services to the server room where it will be a dedicated server machine from Tuesday henceforth. I expect the move will take less than 15 minutes. I will email the list about an hour before the move as a

Dear LLVMers, What: Potential Downtime of LLVM Web/SVN Server When: January 6, 2009 from 8:00 am Central time to 12:00 pm Central time (4 hours) Why: On January 6, 2009, some maintenance will be done on the heating/cooling system of Siebel Center (the building in which the LLVM web/SVN server is located). The cooling system will be turned off, and it's possible that temperatures may