search for: bizarrely

I get these BIZARRE results from wilcox.test() When INCREASING the number of samples i get INCREASED p-values. When increasing the number of samples further, the p-values goes down again. This seems really bizarre! Can anyone explain why this is so?! Example: > w <- wilcox.test(c(1:40),(c(1:40)+100)) > w$p.value [1] 1.860340e-23 > w <- wilcox.test(c(1:50),(c(1:50)+100)) >

Is there any rational explanation for the bizarre seq() behavior below? > seq(2,8.1, lenght.out=3) [1] 2 3 4 5 6 7 8 > help(seq) > seq(2,8,length.out=3) [1] 2 5 8 > seq(2,8.1,length.out=3) [1] 2.00 5.05 8.10 Except maybe that it is early in the morning :) Best regards, Ryszard Ryszard Czerminski AstraZeneca Pharmaceuticals LP 35 Gatehouse Drive Waltham, MA 02451 USA 781-839-4304

Ok, I've been trying to figure out why my A@H won't answer the lines when I can call out and the panel shows the call coming in - well something bizarre has happened. I set up inbound routing to ring my extension if a call comes in - and my extension rings but when I pick it up I get a dial tone. The whole time after I answer I hear the phone I originated the call on just ring and ring

I set up a Centos5 box at work a week or two ago. Today I had this bizarre, repeatable problem: fire up firefox 3.5.1, browse to centos.org, go to the wiki, click the HOWTO button at the top of the page, and either at that point, or a moment later when clicking the link for the RAID documents, KABOOOOMMM!!! X dies and you return to a login prompt. I did it at least three times. Not nice when I

Ok, I've been trying to figure out why my A@H won't answer the lines when I can call out and the panel shows the call coming in - well something bizarre has happened. I set up inbound routing to ring my extension if a call comes in - and my extension rings but when I pick it up I get a dial tone. The whole time after I answer I hear the phone I originated the call on just ring and ring

Try checking your /var/log/messages for OOM killer log lines. If your machine is running low on memory the oom killer will start killing high memory usage programs. Grant ________________________________________ From: CentOS <centos-bounces at centos.org> on behalf of Fred Smith <fredex at fcshome.stoneham.ma.us> Sent: Tuesday, 6 August 2019 10:57 AM To: centos at centos.org Subject:

OK. I give up. I'll ask a stupid question. How do I get the $!#@*$ signif stars line printed by summaries to not look extremely bizarre in the latex produced by Sweave? For example, see p. 7 of http://www.stat.umn.edu/geyer/aster/library/aster/doc/tutor.pdf I can see what the problem is. R emits non-ascii characters (as it is supposed to do), Sweave puts them in the tex file, and

On Tue, Aug 06, 2019 at 01:54:56AM +0000, Grant Street wrote: > Try checking your /var/log/messages for OOM killer log lines. If your machine is running low on memory the oom killer will start killing high memory usage programs. > > Grant we have watched top while it runs and there's no evidence of a memory shortage. > ________________________________________ > From: CentOS

Fred Smith wrote: > > Hi all! > > I'm stuck on something really bizarre that is happening to a product > I "own" at work. It's a C program, built on CentOS, runs on CentOs or > RHEL, has been in circulation since the early 00's, is in use at > hundreds of sites. > > recently, at multiple customer sites it has started just going away. > no core

On Mon, Aug 05, 2019 at 08:57:45PM -0400, Fred Smith wrote: > Hi all! > > I'm stuck on something really bizarre that is happening to a product > I "own" at work. It's a C program, built on CentOS, runs on CentOs or > RHEL, has been in circulation since the early 00's, is in use at > hundreds of sites. > > recently, at multiple customer sites it has

On Mon, Aug 05, 2019 at 08:57:45PM -0400, Fred Smith (fredex at fcshome.stoneham.ma.us) wrote: > Hi all! > > I'm stuck on something really bizarre that is happening to a product > I "own" at work. It's a C program, built on CentOS, runs on CentOs or > RHEL, has been in circulation since the early 00's, is in use at > hundreds of sites. > > recently,

Hello, I have following code in a helper: def custom_ajax(link, options) target = "target_" + options[:target_id] loading = "loading_" + options[:target_id] visible = "visible_" + options[:target_id] #options[:url] = {:inline => 1 }.merge(options[:url]) test = {:inline => 1 }.merge(options[:url]) link_to_remote( link, {

Hi Timo et al. I've been trying to track down why Dovecot recalculations of maildirsize are so wildly different (lower) than what Maildrop comes up with. I think I've found some bizarre behavior in Dovecot -- this is in beta9 as well as CVS from yesterday. It appears Dovecot isn't looking at /Maildir/cur ... /Maildir/new and /Maildir/tmp. It is, however, looking at

...| 134.225.241.1 134.225.241.8 [ vimes ] [ carrot ] 134.225.242.2 134.225.242.8 | | --------------------------------- morpork-net 134.225.242.0/24 I played an MP3 on carrot directly off a share on vimes and looked at the lights on my hub. Bizarrely, I saw the ankh transmit light on vimes flashing and the morpork light on carrot flashing. Doing a netstat -rn on both machines, I saw a connection active from vimes-morpork -> carrot-ankh... I'm sure the reason for the asymmetric path will now be obvious! Both the interfaces on carrot...

I am using the 1.0beta3 vorbis plugin with XMMS. XMMS segfaults immediately when asked to load any .ogg file. Well, usually it segfaults immediately. On occasion you can get out of the file selection box; then it segfaults when it tries to scroll the playlist. Once it started playing a file and then crashed after the first ten seconds. More bizarre still, if I run XMMS under GDB (in hopes of

Before I relate the actual problem, some context. Callcentre environment, a few users testing a new digital dialer... 1. Agents are using Grandstream ATA HT486 and a small analogue dialpad with a headset. 2. SIP connection to Asterisk-1.2b1 3. IAX2 connection to ITSP provider. The call is initially set up in the following way. 1. Agent calls into a meetme conference room and subseqently stays

On Thu, Aug 08, 2019 at 05:06:06PM +0000, Young, Gregory wrote: > Is this on both EL6 and EL7? If only EL7, it could be control groups causing the issue. The idea of cgroups is to prevent zombie processes, but if you need your program to spawn another process then restart itself while the other process continues to run, you need to launch it in a different control group, or the shutdown of the

https://bugzilla.netfilter.org/show_bug.cgi?id=860 Summary: Bizarre "cannot use" error inconsistent with command line Product: iptables Version: 1.4.x Platform: arm OS/Version: other Status: NEW Severity: normal Priority: P5 Component: iptables AssignedTo:

OK, this one is really strange, and I'm not sure where to go with it. Here's the setup ... Main box is running Debian testing/sarge with samba 3.0.5. Earlier it was 3.0.4 and 3.0.2. Very generic installation for home, acting as a file server for several XP Pro boxes, and everything has been running swimmingly. Using USER security, with users logging in to the XP boxes with the same ID

On Mon, Aug 12, 2019 at 10:16:35AM +1000, Jobst Schmalenbach wrote: > On Mon, Aug 05, 2019 at 08:57:45PM -0400, Fred Smith (fredex at fcshome.stoneham.ma.us) wrote: > > Hi all! > > > > I'm stuck on something really bizarre that is happening to a product > > I "own" at work. It's a C program, built on CentOS, runs on CentOs or > > RHEL, has been