similar to: Problem: rsync hangs

rsync 2.5.0 still has a bug where it hangs under some circumstances. The hang is beyond my abilities to track down. I'll keep trying, though, but here are details in case they're of use to anyone else: - Code configured & built on Solaris 2.5.1. - Same binary run on Solaris 2.5.1 (client) and 2.8 (server). - Using rsh transport, but also fails with ssh - Does not fail with

I have been using PXELINUX for a few years now to boot our school's PCs. For a while I've had the school logo and blank background fill the screen to make it look more professional, but that means I can't see the hardware address or IP address a machine gets. Is there a way to insert the hardware address somewhere on the screen other than when PXELINUX first starts up and blurts

While builds and validations of R-1.6.2beta_2002-12-20 were successful on several systems, there were a few failures: ------------------------------------------------------------------------ Apple Darwin 6.2 (MacOS 10.2.2) with gcc-3.2.1: gcc -dynamiclib -flat_namespace -undefined suppress -o .libs/libgslcblas.0.0.0.dylib sasum.lo saxpy.lo ... isamax.lo izamax.lo xerbla.lo -lc -install_name

Hi everybody. I''m a newbie on RoR. I have some experiencie developing in PHP or Java, but I''m just starting with RoR. A few days ago I signed up to the (gs) Grid Service on Media Temple. This is my very first experience deplying RoR on a production enviroment. Until now I just used the WebRick server on developement. Well, the problem I''m having is that after

I am unable to get a my Draytek working with our Asterisk server. I can make/recieve calls but get no audio. I have tried the various codecs at the Vigor end but still getting nothing. I looked at sip debug (below) but am new to Asterisk and don't really know what I am looking for. Asterisk works fine with XLITE so I know my installation is ok. Sip read: INVITE

flight 16260 xen-4.2-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/16260/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-i386-i386-xl 5 xen-boot fail REGR. vs. 16228 test-i386-i386-xl-qemuu-winxpsp3 5 xen-boot fail REGR. vs. 16228 test-i386-i386-win 5

flight 12043 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12043/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12031 test-amd64-i386-rhel6hvm-intel 7 redhat-install fail REGR. vs. 12031 test-amd64-i386-xl-winxpsp3-vcpus1 7

On 02/01/18 14:07, Stephan Bosch wrote: >> I can see 21:21:38 is when the below errors showed up with the above >> 21:21:38 timestamps: >> >> Dec 29 21:21:38 >> lmtp(recipient at domain.net)<17187><UA2fMEQiR1ojQwAAUXb6+w>: Error: >> program `/usr/sbin/sendmail' was forcibly terminated with signal 15 >> Dec 29 21:21:38 >>

Op 12/30/2017 om 6:47 AM schreef tony: > On 2017-12-29 18:35, tony wrote: >> I did some more digging around and found this is reproducible on >> multiple hosts running the same version of Dovecot/Pigeonhole/Postfix. >> The problem resurfaces on any host to an account with enabled >> Vacation/OOO response. The Vacation/OOO reply filter was created in >>

On 2018-01-02 16:37, tony wrote: > On 2018-01-01 17:26, Peter wrote: >> On 02/01/18 14:07, Stephan Bosch wrote: >>>> I can see 21:21:38 is when the below errors showed up with the above >>>> 21:21:38 timestamps: >>>> >>>> Dec 29 21:21:38 >>>> lmtp(recipient at domain.net)<17187><UA2fMEQiR1ojQwAAUXb6+w>: Error:

On 2017-12-29 18:35, tony wrote: > I did some more digging around and found this is reproducible on > multiple hosts running the same version of Dovecot/Pigeonhole/Postfix. > The problem resurfaces on any host to an account with enabled > Vacation/OOO response. The Vacation/OOO reply filter was created in > Roundcubemail, but has been fine for years. One thing to note is in >

On 2018-01-01 17:26, Peter wrote: > On 02/01/18 14:07, Stephan Bosch wrote: >>> I can see 21:21:38 is when the below errors showed up with the above >>> 21:21:38 timestamps: >>> >>> Dec 29 21:21:38 >>> lmtp(recipient at domain.net)<17187><UA2fMEQiR1ojQwAAUXb6+w>: Error: >>> program `/usr/sbin/sendmail' was forcibly

We need to write the irq number to GICC_DIR on the physical cpu that previously received the interrupt, but currently we are doing it on the pcpu that received the maintenance interrupt. As a consequence if a vcpu is migrated to a different pcpu, the irq is going to be EOI''ed on the wrong pcpu. This covers the case where dom0 vcpu0 is running on pcpu1 for example (you can test this

c/s 25336:edd7c7ad1ad2 introduced the concept of a bogus vector, for in irqs delivered through the i8259 PIC after IO-APICs had been set up. However, if supurious PIC vectors are received, many "No irq handler for vector" log messages can be seen on the console. This patch adds to the bogus vector logic to detect spurious PIC vectors and simply ignore them. _mask_and_ack_8259A_irq()

I tried to get icecast2 and BLAMO Error: Failed to spawn GNU rlog on '/cvsroot/icecast-1.1//Makefile.in,v' '/cvsroot/icecast-1.1//acconfig.h,v' '/cvsroot/icecast-1.1//commandline.c,v' '/cvsroot/icecast-1.1//commandline.h,v' '/cvsroot/icecast-1.1//commands.c,v' '/cvsroot/icecast-1.1//commands.h,v' '/cvsroot/icecast-1.1//config.h.in,v'

On 11/02/2015 03:16 PM, Paolo Bonzini wrote: > On 26/10/2015 10:56, Andrey Smetanin wrote: >> Hyper-V SynIC is a Hyper-V synthetic interrupt controller. >> >> The test runs on every vCPU and performs the following steps: >> * read from all Hyper-V SynIC MSR's >> * setup Hyper-V SynIC evt/msg pages >> * setup SINT's routing >> * inject SINT's

On 11/02/2015 03:16 PM, Paolo Bonzini wrote: > On 26/10/2015 10:56, Andrey Smetanin wrote: >> Hyper-V SynIC is a Hyper-V synthetic interrupt controller. >> >> The test runs on every vCPU and performs the following steps: >> * read from all Hyper-V SynIC MSR's >> * setup Hyper-V SynIC evt/msg pages >> * setup SINT's routing >> * inject SINT's

Hi, folks. I'm senior online editor at CIO.com, and I'm working on an article for which I'd very much like your help. There's often a lack of communication between techies and top company management. Maybe they don't want to hear about problems; perhaps you give them technical details that are far more granular than they want to know. But dealing with spam is a topic

The behaviour of default ISRs as provided by the BIOS varies wildly between platforms. Some will simply iret, some will send EOI, some will send EOI and disable the interrupt at the PIC, some will crash the machine due to single-bit errors in the ISR address. When PXENV_UNDI_ISR_IN_START returns PXENV_UNDI_ISR_OUT_NOT_OURS, send the EOI ourselves rather than risking the unpredictable behaviour

I'm following along in the guide, trying to make printer drivers available from Samba. But when I right-click on a printer in Windows XP and select the "properties" tab, it's disabled: http://tinypic.com/usermedia.php?uo=BMeeHijW2w%2FyTvDsjpQbEQ%3D%3D So how do I enable this so the client can upload the drivers? So far I have tried: * Add the name of the user as "printer