similar to: OT: for those wondering on the stability

I never did solve my "puzzle" as to how to kill a Linux process that seems to be deadlocked in kernel space, but thought I would report to the list that the server did manage to stay up and continue to process several thousand calls per day: ast% uptime 11:49:37 up 1000 days, 16:30, 1 user, load average: 1.00, 1.00, 1.00 ast% Since for the past four weeks I have forced my poor

Hi, I have a 3d array as below, I want to make this array to a matrix of p=50(rows) and n=20(columns) with the coverage values . The code before the array is: library(binom) Loading required package: lattice pi.seq<-seq(from = 0.01, to = 0.5, by = 0.01) no.seq<-seq(from = 5, to = 100, by = 5) cp.all = binom.coverage( p = pi.seq, n = no.seq , conf.level = 0.95, method = "exact")

Hi all, I have 2 questions: 1)How do I calculate the mean on an imported txt file? I've imported the file below and that's what it looks like imported. How do I then calcuate the mean, median, or mode on the column LeafArea using the desktop R package? Any help would be greatly appreciated!! Thanks, Nat LeafType Leaflets LeafArea ShapeRatio LeafWeight LeafThickness 1 1

----- Original Message ----- From: "James Hogarth" <james.hogarth at gmail.com> To: "centos" <centos at centos.org> Sent: Tuesday, August 29, 2017 2:03:44 PM Subject: Re: [CentOS] Syncronize systemctl status with reality? On 29 Aug 2017 17:58, "Leroy Tennison" <leroy at datavoiceint.com> wrote: The particular issue is with puppetmaster (which

Disclaimer: Not a troll I'm curious as to this obsession with uptime is. All of the posts of this type are along the lines of "After X days, Y thing does not work but if I reload or reboot, it's OK" - so why not cron a reboot? Is it considered bad form or something like that? I reboot every night whether it is needed or not, not afraid to admit it, and everything works fine for

Hi, I just upgraded from 1.2 to 1.4. In 1.2, when I did a "show uptime" I used to see a second line telling me the time since the last reload. Has this been removed in 1.4? The following is the output of my two test boxes: Connected to Asterisk 1.4.18.1 currently running on voip2 (pid = 10605) Verbosity is at least 3 voip2*CLI> show uptime System uptime: 15 hours, 55 seconds

I'm having trouble reshaping a data.frame from long to wide. (I think that's the right terminology; feel free to educate me.) I've looked at the reshape function and package and plyr package, but I can't quite figure out how to do this after a dozen variations. I have a data.frame with more levels than this, but similar to: > tst K1 K2 K3 V1 V2 V3 1 10 D a 0.08 99

Now this is what I call uptime... minipbx*CLI> show uptime System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 seconds Last reload: 8 hours, 3 minutes, 51 seconds Bizarre bug? root at minipbx:~# asterisk -V Asterisk 1.4.37 root at minipbx:~# uname -a Linux minipbx 2.6.32-dockstar #2 Thu Nov 25 18:03:25 UTC 2010 armv5tel GNU/Linux root at minipbx:~# uptime 03:29:27 up 5 days,

Hi 2 all ! I have problems with concurrent filesystem actions on a ocfs2 filesystem which is mounted by 2 nodes. OS=RH5ES and OCFS2=1.2.6 F.e.: If I have a LV called testlv which is mounted on /mnt on both servers and I do a "dd if=/dev/zero of=/mnt/test.a bs=1024 count=1000000" on server 1 and do at the same time a du -hs /mnt/test.a it takes about 5 seconds for du -hs to execute: 270M

I came in this morning to find all the servers all locked up solid: # passenger-status ----------- General information ----------- max = 20 count = 20 active = 20 inactive = 0 Waiting on global queue: 236 ----------- Domains ----------- /etc/puppet/rack: PID: 2720 Sessions: 1 Processed: 939 Uptime: 9h 22m 18s PID: 1615 Sessions: 1 Processed: 947 Uptime: 9h 23m

Hello, I encountered the following bug when migrating a Linux-2.6.32.54 PV domain on Xen-3.4.3 between different hosts, whose uptime differs by several minutes (3 hosts, each ~5 minutes apart): When migrating from a host with lower uptime to a host with higher uptime, the VM looses it''s network connection for some time and then continues after some minutes (roughly equivalent to the

Sorry again for the only marginal relation to asterisk, but the issue does affect the voice performance I am experiencing, so I am soothing my guilt with that. Bet you don't see this every day: ast% uptime 13:48:08 up 981 days, 18:29, 1 user, load average: 1.08, 1.02, 1.01 ast% I *REALLY* want this machine to see 1000 days uptime, if for nothing other than bragging rights. Its been

Hi, I have done some debugging to find out the root cause of bug 1282, which has the following symptoms with paravirtualized guests: - after a live migrate, the time on the guest can jump - after a live migrate, the guest "forgets" to wake up processes - after a domU save, dom0 reboot and domU restore, the time is correct but processes are not woken up from sys_nanosleep The problem

Package: xen Version: 4.0.1-2 Severity: normal /proc/uptime shows idle bigger than uptime: dom0: % cat /proc/uptime 518389.91 944378.70 % one domU: % cat /proc/uptime 417536.22 764826.15 % another domU: % cat /proc/uptime 426960.17 795800.89 % This is normal on multicore / ht cpu, but this is old amd: % lscpu Architecture: i686 CPU(s): 1 Thread(s) per core: 1

#this is a daily series of precipitation data. I would like to condense it into weekly means. How can I do this #as a side note I would like to do this same thing to two years worth of fifteen minute interval data and make it into #a series of daily averages (there are 96 readings per day) #is aggregate the right function? or... y <- c(1.23, 0, 0, 0, 0, 0, 0, 0, 0, 0.27, 0, 0.29, 0, 0, 0,

Hi everyone, Apologies in advance, this will be a bit long but I'm hoping to get some guidance and hints on usual practices for using Samba4 AD DC as an Idm for W10 laptops that might be on the road elsewhere.. As much as I have been using samba for file serving, a Samba AD DC is something new to me. I built a small Samba AD DC infrastructure to serve UIDs and Passwords (4 VMs on 4 KVM

Sorry, forgot to change the subject on my first posting. I was reading a comment this morning about something Microsoft had published to the effect that there were vendors guaranteeing 99.9% uptime for NT. The guy who wrote the reply did the math for what that means, and the results are very interesting. Quote below: OK, now what does a 99.9% uptime guarantee mean? Well, it means that at

I've looked around at the API documents (I'm using python) and I know how to find the cpu active uptime of the domain, but that only increases if the domain is running something. Is there a way to determine when the domain was first launched, either as a date or uptime with idle uptime included? /Amy

Sorry, this is off topic to asterisk itself, but is about the list server. I had a power failure lastnight at home, where my email server resides, and my network was down for about 20 minutes, that was after 45 minutes of uptime on UPS. Since power was restored, around 9:45 PM EST on 2/16, I have not received a single post from the users, biz, or dev lists. Normally when this has happened

Hi, I'm wondering if this is normal asterisk behaviour: asterisk*CLI> sip show channels Peer User/ANR Call ID Format Hold Last Message Expiry Peer 10.12.0.2 (None) 3c2f7ff2975e-wp 0x0 (nothing) No Rx: PUBLISH <guest> 10.12.0.2 (None) 3c2f7f21b71b-9q 0x0 (nothing) No