Re: [CentOS] BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]

2016-08-18 Thread JJB



2016-08-18 12:39 GMT-04:00 correomm :


This bug is reported only on the VM's with CentOS 7 running on on VMware
ESXi 5.1.
The vSphere performance graph shows high CPU consume and disk activity only
on VM's with CentOS 7. Sometimes I can not connect remotely with ssh
(timeout error).


I'm also seeing those errors in several servers, running under 5.5.
Currently investigating if this

has anything to do (the resource overcommit bit).


Does this happen (only) while taking or consolidating snapshots? The VM 
is suspended during these operations and the OS isn't too crazy about 
it, especially if you have slow storage.


Jack

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Bourne shell deprecated?

2016-04-27 Thread JJB

On 04/27/16 15:33, Jon LaBadie wrote:

The V1 shell was of course not Bourne's.

However Bourne's code was consider "unmaintainable" as he was an
algol coder, not a C coder.  He had numerous macros defined to
allow him to use his algol coding style with a C compiler.


So *that's* what it is!  I have a copy of the source (on paper). What a 
hoot!  I thought he was trying to make C look like shell code.


Jack

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Bourne shell deprecated?

2016-04-27 Thread JJB

On 04/27/16 15:18, Chris Adams wrote:

Once upon a time, JJB  said:

Interesting.  Back in 1980 we called /bin/sh the Mashey shell.  It
did not have command substitution or other things we now take for
granted.  Bourne did that for us.  So there's a version or two
missing in history...

Check the history here:

https://github.com/dspinellis/unix-history-repo



This history might be that of a particular lineage.  CB UNIX and PWB 
UNIX existed in the gap between 1975 and 1979.


https://en.wikipedia.org/wiki/CB_UNIX

Jack

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Bourne shell deprecated?

2016-04-27 Thread JJB



>The various *BSD's have & use the actual Bourne shell 
>
>

Which one? All the BSDs I know of use the Almquist Shell except for
OpenBSD which uses a patched version of the Public Domain Korn Shell


indeed, the man for sh(1) on freebsd 10.3 says (in part)

HISTORY
 A sh command, the Thompsonshell, appearedin Version 1 
AT&T UNIX. It
 was superseded in Version 7 AT&T UNIX by the Bourne shell,
which inher-

 ited the name sh.

 This version of shwas rewritten in 1989 under theBSD 
license after the

 Bourne shell from AT&T System V Release 4 UNIX.



Interesting.  Back in 1980 we called /bin/sh the Mashey shell.  It did 
not have command substitution or other things we now take for granted.  
Bourne did that for us.  So there's a version or two missing in history...


Jack
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] 2.6.18-92.1.6.el5xen -- 8GB missing?

2008-07-12 Thread JJB
Hello,

Last night I upgraded a server to CentOS 5.2.  The server has 16GB of
RAM.  Now that it's running 2.6.18-92.1.6.el5xen only 8GB is reported to
exist.

# cat /proc/meminfo
MemTotal:  8818688 kB
MemFree:   3730124 kB
Buffers:202004 kB
Cached:4086788 kB
SwapCached:  0 kB
Active:1551480 kB
Inactive:  2958196 kB
HighTotal:   0 kB
HighFree:0 kB
LowTotal:  8818688 kB
LowFree:   3730124 kB
SwapTotal: 8388600 kB
SwapFree:  8388600 kB
Dirty:7348 kB
Writeback:   0 kB
AnonPages:  220788 kB
Mapped:  46948 kB
Slab:   137404 kB
PageTables:  29012 kB
NFS_Unstable:0 kB
Bounce:  0 kB
CommitLimit:  12797944 kB
Committed_AS:   756072 kB
VmallocTotal: 34359738367 kB
VmallocUsed:  5004 kB
VmallocChunk: 34359733235 kB

However, dmesg appears to report something else:

# dmesg | grep Memory
Memory: 15506152k/15899468k available (2417k kernel code, 384480k
reserved, 1350k data, 176k init)

I looked in the messages file for complaints and didn't see anything
that strikes me as unusual.

How much memory is available?  Is this a known issue?


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos