search for: switchovers

Hello! I am in the middle of having a vanity toll-free DID set up. It's been 13 days now (9 business days). This is the first time I'm doing this, and I'm not sure of the process. There has been a very weird progression of changes on my number, from fast-busy, to a message saying that I'm calling from a phone with restrictions (no matter *what* line I call from), to a

The following code: cut(as.POSIXct("2009-11-01 04:00:00", tz="America/Los_Angeles"), "1 day") gives the error: Error in seq.int(0, to - from, by) : 'to' must be finite This is related to November 1st, 2009 being the switchover date from daylight savings time to standard time in the America/Los_Angeles time zone. In particular, in cut.POSIXt, the starting

Hi everyone, Here is the story. We are running Redhat Enterprise Linux 4, and were using Dovecot .99.x . At one point, we chose to switch from mbox to maildir (and still use Dovecot). After the switchover our users reported a bug when using Thunderbird: "A new behavior that I have observed a couple of times is that the new IMAP server confuses email headers with content. E.g., I have an

So far so good...other than a my-bad fubar with the permission on the index directory that kept DC from creating index dirs for the entering-for-the-first-time users, quickly noticed (thanks to the excellent logging) and corrected. Some questions 1) the max_mail_processes parm in dovecot.conf...is that *all* processes owned by dovecot? 2) I thought there was a parm to limit how many processes

Gents, I'm relocating mailboxes to a new server. Before switching over to a new server I ran syncing a few times without any issues first I sync files with rsync from the old server to have a local copy, then I sync mailboxes with dsync /usr/bin/doveadm -Dv sync -u $MBOX -R "sdbox:/srv/vmail/temp/srv/srv.bgoperator.ru/${MBOX}:DIRNAME=DbOx-mAiLs" After switching over smtp

...it looks like the fallback works without rebuffering. I do see one problem -- when the main mountpoint stream restarts, the fallback continues to play. Once I stop the fallback mountpoint stream, the main mountpoint stream restarts, but only after client rebuffering Also, during the mountpoint switchovers, sometimes the meta-data is lost in the clients. thank you, Michael ________________________________ <p>On Friday 19 March 2004 08:00, Gnosis wrote: > I just was looking at the CVS nightly build of the icecast2\src\source.c > and see that the mountpoint fallback is now implement...

I have a customer that is using 250 gig drives for his business data. I have been using rsync to keep mirror copies of his data on a second machine. In the last 3 months I have lost 2 of four drives, the last one being the system drive. I have been doing a manual switchover. Each time rsync runs, I copy my samba conf files, passwd, shadow and group files from etc. Has anyone setup a HA

On May 23, 2009, at 12:04 PM, Nick Lewycky wrote: >> >> That sounds like a serious bug then: {} should be a first class value >> just like {i32}. > > Okay then. I've just posted a patch to llvm-commits which would do > that: > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20090518/077934.html Why not separate the two patches: making {} legal

Q1: My imap server has 4 interfaces, but only one is used for imap traffic. Can I do this: listen = 10.20.30.40:10143 (when imap.mycollege.edu is 10.20.30.40) Or is there even any benefit to doing this? Q2: Can I specify more than one port....during test eval, I've had the IT dept using port 1043 for listen....which I will, of course, change to 143 when DC goes production. So my

Apparently Tanya and I got dropped from svn commit privs. That is now fixed. The next issue is that John left his cvs convert script in his crontab (which I just removed). As such, *all svn commits that happened since the switchover have been lost*. Needless to say, this irritates me. John, will you please reapply all lost commits? You can find the diffs here:

Proposal: $ git tag -a r375505 186155b89c2d2a2f62337081e3ca15f676c9434b -m "Last SVN commit before switchover to github." $ git push origin r375505 Why? This makes "git describe" produce usable linear revision numbers that are a natural continuation of the SVN revision numbering. For example, a git describe on HEAD from earlier today gives: $ git describe

I just was looking at the CVS nightly build of the icecast2\src\source.c and see that the mountpoint fallback is now implemented (compared to the 2.0.0 release's source.c) I was hoping to use this feature to support a multi-home radio station that has a master mountpoint stream and offsite "guest" mountpoints. These guest mountpoints would attach on a scheduled based and,

I have a customer installation with an Adtran DS3 mux. The DS1's go into my Asterisk servers that run IVR/Call recorders. The DS3 provider is Qwest, and they tell me that they routinely drop the DS3 service to redundant back-up's and that this is a common practice that happens thousands of times to DS3 lines daily across the US without any service interruptions. They say that the

On 27.11.2014 20:39, Chris Matthews wrote: > I can look into it if I get access. Anton, any chance we can get Renato or Chris access to llvm.org to fix this? Tobias

Dear All, I am newbie to Linux Clustering, i have 2 standalone CentOS servers, i want to setup a cluster on those servers, to synchronize between each other, and to make a one as standby to the other, if a one fails the other will switchover. I will mostly use Apache, Mysql, and PHP. I have read the "Cluster Administration" document, i found that there are multiple methods to setup

Thanks for writing this up. I think it's a really important point which deserves discussion. Ultimately, I think it is a question as to whether to prioritize the easy switchover for existing out of tree forks, or to prioritize having the best conversion we can make. I feel very strongly that the latter should be the priority for the official repository conversion, and that, therefore, we

Chris Lattner wrote: > On May 23, 2009, at 12:04 PM, Nick Lewycky wrote: >>> That sounds like a serious bug then: {} should be a first class value >>> just like {i32}. >> Okay then. I've just posted a patch to llvm-commits which would do >> that: >> http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20090518/077934.html > > Why not

On May 23, 2009, at 1:47 PM, Nick Lewycky wrote: > Chris Lattner wrote: >> On May 23, 2009, at 12:04 PM, Nick Lewycky wrote: >>>> That sounds like a serious bug then: {} should be a first class >>>> value >>>> just like {i32}. >>> Okay then. I've just posted a patch to llvm-commits which would do >>> that: >>>

Markus <universe at truemetal.org> schrieb: > I don't think so. Most users will use the router provided by Telekom. These users do NOT use Asterisk on theis Telekom-line... I asked for someone using Asterisk on Magenta Zuhause... :) > Anyway, after 15 seconds of Google'ing for Magenta Zuhause and SIP, > maybe this will help you: I already know these links, and I

On Fri, 29 Jun 2007, Chris Lattner wrote: > The next issue is that John left his cvs convert script in his crontab > (which I just removed). As such, *all svn commits that happened since > the switchover have been lost*. Needless to say, this irritates me. This has all been fixed now. The tree should be fine, with no contents lost and with the same rev #'s as before. If you