Sponsored Content
Full Discussion: SCO 5.0.7v VM Hardware
Operating Systems SCO SCO 5.0.7v VM Hardware Post 302921039 by stewartg on Tuesday 14th of October 2014 11:56:26 AM
Old 10-14-2014
SCO 5.0.7v VM Hardware

I run SCO 5.0.7v in ESXi 5.5 and am looking at ways to increase performance. I notice that the VM hardware is still set to 4 and wondered if there was an advantage in raising it or will this cause issues?
 

3 More Discussions You Might Find Interesting

1. SCO

Migrate SCO 5.0.6 to different hardware

hi Howto migrate SCO Unix 5.0.6 to different hardware? I'd like to try using Acronis. Which Acronis Version support SCO Unix 5.0.6? (14 Replies)
Discussion started by: ccc
14 Replies

2. Solaris

Hardware faulty, but which hardware?

Hi folk, I have this hardware faunty message, but dont know which hardware is this ? can you guide me ? --------------- ------------------------------------ -------------- --------- TIME EVENT-ID MSG-ID SEVERITY ---------------... (9 Replies)
Discussion started by: dehetoxic
9 Replies

3. SCO

Recommendation for hardware to run SCO OSR 5.0.7 natively

Looking for a modern server to run SCO OSR 5.0.7 without VM (native), h/w must have manufacturers warranty. Requirements would be to accommodate light loads of up to 15 users, app does not take more than 30 - 40 MB of RAM and data stored takes up to 15 - 20 GB, no internet connections... (3 Replies)
Discussion started by: migurus
3 Replies
PMPOST(1)						      General Commands Manual							 PMPOST(1)

NAME
pmpost - append messages to the Performance Co-Pilot notice board SYNOPSIS
$PCP_BINADM_DIR/pmpost message DESCRIPTION
pmpost will append the text message to the end of the Performance Co-Pilot (PCP) notice board file ($PCP_LOG_DIR/NOTICES) in an atomic man- ner that guards against corruption of the notice board file by concurrent invocations of pmpost. The PCP notice board is intended to be a persistent store and clearing house for important messages relating to the operation of the PCP and the notification of performance alerts from pmie(1) when other notification options are either unavailable or unsuitable. Before being written, messages are prefixed by the current time, and when the current day is different to the last time the notice board file was written, pmpost will prepend the message with the full date. If the notice board file does not exist, pmpost will create it. pmpost would usually run from long-running PCP daemons executing under the (typically unprivileged) $PCP_USER and $PCP_GROUP accounts. The file should be owned by root, and group writable by the $PCP_GROUP group. FILES
$PCP_LOG_DIR/NOTICES the PCP notice board file PCP ENVIRONMENT
The file /etc/pcp.conf contains the local values for PCP_ variables. UNIX SEE ALSO
logger(1). WINDOWS SEE ALSO
pcp-eventlog(1). SEE ALSO
pmie(1), pcp.conf(5) and pcp.env(5). Performance Co-Pilot PCP PMPOST(1)
All times are GMT -4. The time now is 04:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy