search for: untimed

Hi, I am wondering how rsync-3.0.6 react if it encounters ESTALE error while synching? If I remember correctly then the rsync-2.6.0 skipping that file/dir in case of ESTALE error. Jignesh. -------------- next part -------------- HTML attachment scrubbed and removed

...within webroot. The server creates a source thread > so that it interacts with the existing fallback mechanism. No timing > goes on with the data stream, and usual rules for fallbacks apply, ie > same format and same parameters. > a word of warning: the fallback files will be served untimed, i.e. as fast as the receiving end can process them. if it's a relay, then this will eat up your entire bandwidth. i've seen loads of 30+ mbit/s with just two relays. if all your clients are actual players, you will be fine, but even one wget will really warm your uplink :)

I can think of many people that use LLVM and maintain out of tree extentions that will likely never be incorporated into mainline. Maintaining out of tree intrnisics takes a fair amount of work and leads to the choice of using a single version of LLVM for a project (and thus have to manually incorporate bug fixes) or risk untimely breakage. I propose that the plugin be extended to allow plugable

Hi all My problem is that: With reference to http://backgroundrb.rubyforge.org/ 1---I have download backgroundrb from http://opensvn.csie.org/ezra/rails/backgroundrb to my vendor/plugin in my application folder. 2-- after that I used the command to run :-rake backgroundrb:setup -- trace From my application

Hello all, I was asked about a proper way to ensure powerfail shutdown of a blade server fed off an APC SmartUPS, which is monitored by all hosts over SNMP. In particular, they'd like to avoid the "untimely" return of utility power - when the OSes are already shutting down, and would stay down because the UPS is well-fed now and thus won't power off and later power on to boot

Hi, this relates to R-devel of 1999/July/18. I will outline what I had to change to get R to compile with cc then with gcc. Note that R compiled with cc works, R compiled with gcc is broken. --> Compile with cc: 1) Edit src/main/saveload.c: disable the undefine! With the #undef _XOPEN_SOURCE_EXTENDED the compilation dies an untimely death. (And the header files are not as badly broken

Use gem reservation helpers and direct reservation_object_* calls instead of ttm. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 36 ++++++++++++-------------- 1 file changed, 17 insertions(+), 19 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_ioctl.c b/drivers/gpu/drm/virtio/virtgpu_ioctl.c index 5cffd2e54c04..6db6a6e92dde

Use gem reservation helpers and direct reservation_object_* calls instead of ttm. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 36 ++++++++++++-------------- 1 file changed, 17 insertions(+), 19 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_ioctl.c b/drivers/gpu/drm/virtio/virtgpu_ioctl.c index 5cffd2e54c04..6db6a6e92dde

...er creates a source thread >> so that it interacts with the existing fallback mechanism. No timing >> goes on with the data stream, and usual rules for fallbacks apply, ie >> same format and same parameters. >> > > a word of warning: the fallback files will be served untimed, i.e. as > fast as the receiving end can process them. > if it's a relay, then this will eat up your entire bandwidth. i've seen > loads of 30+ mbit/s with just two relays. > > if all your clients are actual players, you will be fine, but even one > wget will really wa...

Hi All, I'm currently having a problem with video calls with 2 Windows Messenger clients through *. The video+audio call gets established ok, but after a random period, usually anywhere from 20 seconds to 3 minutes, (though usually under a minute), both video and audio gets disconnected. Just plain audio calls between WM through * work fine and don't have this problem. Using

Thank you to all who replied. I am very happy (for you guys anyway) to report that this was NOT infact caused by ext3, but rather a very very untimely memory failure that occured during my convertion from ext2 to ext3. It turned out that one of my PC2100 DDRs went south, and I'll be contacting Crucial to deal with that. Thanx again for all the help. benr. -----Original Message-----

Hi, I'm running the following command for a remote host backup: /usr/local/bin/rsync -a --delete --delete-excluded -v --timeout=120 -z --no-whole-file -partial --partial-dir .rsync-partial --exclude=/sys/* --exclude=/tmp/* --exclude=/stuff/distfiles/* --exclude=/stuff/sistema/* --exclude=/stuff2/ftp/* --exclude=/stuff2/backup/* --exclude=/home/ftp/* --exclude=/home/gentoo/* --exclude=/mnt/*

On Tue, Jun 18, 2019 at 03:58:15PM +0200, Gerd Hoffmann wrote: > Use gem reservation helpers and direct reservation_object_* calls > instead of ttm. > > Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> > --- > drivers/gpu/drm/virtio/virtgpu_ioctl.c | 36 ++++++++++++-------------- > 1 file changed, 17 insertions(+), 19 deletions(-) > > diff --git

Hello, useRs. I was monitoring the recent thread about the numerical (in)accuracy of the C pow function and the apparent mismatch between R and matlab. That particular problem has been addressed, but it seems there are many others awaiting. I'm wondering if there is advice for package writers & prospective R contributors about avoiding the most common sorts of numerical mistakes. Has

On Sun, Feb 2, 2014 at 8:58 AM, Lucas Stach <dev at lynxeye.de> wrote: > Am Samstag, den 01.02.2014, 18:28 -0500 schrieb Ilia Mirkin: >> On Sat, Feb 1, 2014 at 8:40 AM, Lucas Stach <dev at lynxeye.de> wrote: >> > Am Samstag, den 01.02.2014, 12:16 +0900 schrieb Alexandre Courbot: >> >> Add a clumsy-but-working FB support for GK20A. This chip only uses

Hello all, During discussion of https://github.com/networkupstools/nut/issues/1782 me and Greg uncovered a diametral difference of opinion about the verbosity of NUT programs in general, and of `upsmon -K` (checking for POWERDOWNFLAG during shutdown integration) in particular. To me as a sysadmin type often (in the past at least) having to troubleshoot the tails and ends of systems'

Hello all, During discussion of https://github.com/networkupstools/nut/issues/1782 me and Greg uncovered a diametral difference of opinion about the verbosity of NUT programs in general, and of `upsmon -K` (checking for POWERDOWNFLAG during shutdown integration) in particular. To me as a sysadmin type often (in the past at least) having to troubleshoot the tails and ends of systems'

Does anyone else have one of these on 24/7 running RHEL 5.4 or Centos 5.4 ?? That box mysteriously stops ( no crash data, it just stops) hours or days after boot, with or without X. Cntl-Alt-Delete reboots it without power cycling. The usual diagnostics (memtest and fsck) return no errors. Works great until it freezes. No evidence of kernel oops anywhere. If others report the same issues we

Hi Jim, On Tue, 18 Feb 2014, Jim Klimov wrote: > Hello all, > > I was asked about a proper way to ensure powerfail shutdown of a blade > server fed off an APC SmartUPS, which is monitored by all hosts over > SNMP. In particular, they'd like to avoid the "untimely" return of > utility power - when the OSes are already shutting down, and would > stay down

On Mon, 12 Apr 2005, Karl Heyes wrote: > My current work is on > http://mediacast1.com/~karl/testing/icecast-2.2-kh3pre.tar.gz Bugs: Relays ignore the hidden flag HUPing icecast puts icecast in a strange state where it doesn't actually take account of the conf changes, and also won't terminate on a TERM and needs a KILL - but it does still "work" otherwise. How is