similar to: odd uptime error message

I'm working with a FreeBSD user -- a teacher -- who's running KDE on a system on which she neither has nor wants root privileges. She wants to be able to mount and unmount floppies and ZIP cartridges from within KDE, using the standard KwikDisk utility (which, by the way, generates mount and unmount command that don't conform to FreeBSD syntax; however, it appears possible to fix this

Hey, folks, I've got an HP Proliant DL580 G5 throwing ECC errors. This is annoying, since a) it's all new as of a few months ago, and b) it's *fully* populated. The two things I need to figure out are a) *which* DIMM it is, and b) is it mirrored; if so, which *other* DIMM needs to come out until we get replacements from the OEM. Here's one of many, all identical, from dmesg:

I installed RHEL 5.8 x86_64 today. To my surprise, when I connect it using vnc viewer it does not start gnome-session automatically. The last line in .vnc/xstartup is twm& Before I removed RHEL 6.1 a few days ago, vncserver always starts gnome-session every time I open vncviewer. Is that related to RHEL version or vnc-server version? Best Regards, Yawei

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

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

Hi, We can give multiple domains to the following commands. But, the help messages of the commands are explained to be able to give a single domain. # xm vcpu-list vm1 vm2 Name ID VCPU CPU State Time(s) CPU Affinity vm1 1 0 0 r-- 1409.3 any cpu vm2 2 0 0 r-- 1255.8

We manage hypervisors (VMWare ESXi/vCenter, KVM, XEN, Hyper-V) by remote Libvirt API, in our case we need to get the host uptime via the same libvirt interface. Is there a way get this info now for all the aforementioned hypervisor types? The APIs virConnectGetSysinfo(), virNodeGetInfo() provide host info but it doesn't include the system uptime. The virNodeGetCPUStats() can returns CPU

--- tests/Makefile.am | 6 ++++ tests/test-info-conntime.sh | 65 +++++++++++++++++++++++++++++++++++ tests/test-info-time.sh | 68 +++++++++++++++++++++++++++++++++++++ tests/test-info-uptime.sh | 65 +++++++++++++++++++++++++++++++++++ 4 files changed, 204 insertions(+) diff --git a/tests/Makefile.am b/tests/Makefile.am index 5a65db7..abcce94 100644 --- a/tests/Makefile.am +++

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,

Hmm.. All the hp/ux of the 10.x era has that set in the configure.ac. - Ben ---------- Forwarded message ---------- Date: Tue, 9 Jul 2002 05:40:35 +1000 (EST) From: bugzilla-daemon at mindrot.org To: openssh-unix-dev at mindrot.org Subject: [Bug 345] New: w (uptime) command still indicates user is logged in after logout http://bugzilla.mindrot.org/show_bug.cgi?id=345 Summary: w

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

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

http://bugzilla.mindrot.org/show_bug.cgi?id=345 Summary: w (uptime) command still indicates user is logged in after logout Product: Portable OpenSSH Version: -current Platform: HPPA OS/Version: HP-UX Status: NEW Severity: minor Priority: P2 Component: Build system AssignedTo:

I know there has been better uptime than this reported, but I figured I'll share it anyhow: @pbx:~# uptime 18:39:07 up 621 days, 9:40, 2 users, load average: 0.00, 0.00, 0.00 pbx:~# cat /proc/cpuinfo processor : 0 vendor_id : CentaurHauls cpu family : 6 model : 10 model name : VIA Esther processor 1200MHz stepping : 9 cpu MHz : 1197.305 cache

On 9/28/19 3:02 PM, Richard W.M. Jones wrote: > --- > tests/Makefile.am | 6 ++++ > tests/test-info-conntime.sh | 65 +++++++++++++++++++++++++++++++++++ > tests/test-info-time.sh | 68 +++++++++++++++++++++++++++++++++++++ > tests/test-info-uptime.sh | 65 +++++++++++++++++++++++++++++++++++ > 4 files changed, 204 insertions(+) > > +# Test the info

Hello! I've noticed this problem two times now.. last time I fixed it by rebooting the (centos 5.1 x86 32b) xen host/dom0. Symptoms: - Already running domUs (debian 2.6.18-6-xen-686 32b PAE) continue running and working OK - Cannot start new domUs (debian 2.6.18-6-xen-686).. kernel bootup just hangs before running initrd. Same domU with the exact same xen domU cfgfile worked earlier.

Hi Is the keep alive activated on the phone? On Thu, Aug 11, 2016, 5:36 PM Dovid Bender <dovid at telecurve.com> wrote: > 1) Does it happen every time at the 5 minute work? > 2) Have you done a dump on the client side to see if the NAT device is > dropping the packets? > 3) Is the phone behind a load balance internet connection and is the RTP > port changing? > > >

Hi, I've got a Dell Latitude D830 running 7.1-PRERELEASE/amd64 which I've just csup'd to the -STABLE as of 5-Jan-2009, and after going thru' the std build+install; XOrg now comes up with a blank screen, sometimes interspersed with green dots. I did test out X prior to doing an installworld, and that came up with no problems. However, after doing an installworld, X is now broken.

On Mon, June 15, 2015 11:16 am, Pete Geenhuizen wrote: > Enable it in /usr/share/logwatch/default.conf/services/zz-runtime.conf Thanks a lot! Helps you to be aware that you definitely missed something important if you haven't the box rebooted during more than 45-60 days... Valeri > > Pete > > On 06/15/15 09:58, James B. Byrne wrote: >> CentOS-6.6 >> >> Can

CentOS-6.6 Can logwatch be configured to display the system uptime as part of the reporting prologue? If not then what would be the recommended way of including this information in a daily logwatch report? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne