I'm not an HP-UX SysAdmin and work with Linux Systems a bit more but I have a question about the logging level for the snmpdm. We don't specify or modify anything so we're probably taking the default? What is the default?
I see in the man page these options are available:
Thanks in advance for any info. I've posted on another forum to no avail and have researched but cannot find the answer.
Moderator's Comments:
Code tags for code please.
Last edited by Corona688; 06-18-2014 at 04:45 PM..
How can i restart the console getty without rebooting the system on HPUX 11.0
Normally it will be stated by ps -ef | grep getty
console 0:00 /usr/sbin/getty console console
many thanx (4 Replies)
WARNING - /usr/sbin/fsck not found. Most likely the mount of
/usr failed or the /usr filesystem is badly
damaged. The system is being halted.
Either re-install the system of boot with -b
option in an attempt to recover
Anyone help me on restoring this without having to reinstall. it is a... (8 Replies)
I noticed in my cron log file for my solaris 8 servers the rc=1. I imagine that is return code and something did not process. Does anyone know what that is, is there fix or the implications of leaving it?
Thank you
> CMD: && /usr/sbin/rtc -c > /dev/null 2>&1
> root 22049 c Fri Dec 19... (1 Reply)
please tell pre-requisite steps to activate cron. i activated the cron but it not executing the script which i set in crontab entry.through root user i passed the service crond start it get start.but when i go to etc/init.d and passed crond stop command.it gets crond: can't lock /var/run/crond.pid,... (2 Replies)
I thought I would document this error since its not documented very well. The package or file may be different but the idea is the same.
$ sudo yum updateLoaded plugins: langpacks, presto, refresh-packagekit, versionlock
Setting up Update Process
Resolving Dependencies
--> Running... (0 Replies)
Hello.
I am currently on HPUX and migrating to Linux RHEL 6.4
This program on hpux:
/usr/sbin/userdbset
is puzzling me on linux.
Does anyone know the equivilent program forked or used on linux.
This program is mentioned in our user reset script.
here is a strings of the... (2 Replies)
Dear Expret,
Help me about my issue,
I trying add new disk to volume Group but error:
step add new disk to volume group.
1. ~Change a Volume Group
Add a Physical Volume to a Volume Group
Remove a Physical Volume from a Volume Group
Reorganize a Volume Group... (6 Replies)
Dear Concern,
We have observed that following command stuck/does not work in some RedHat nodes. Please advise us to troubleshoot the issue.
/usr/sbin/hpacucli ctrl all show
Note: HP Array Configuration Utility CLI for Linux 64-bit
With Best Regards,
Md. Abdullah-Al Kauser (3 Replies)
Discussion started by: makauser
3 Replies
LEARN ABOUT OSF1
vollogcnvt
vollogcnvt(8) System Manager's Manual vollogcnvt(8)NAME
vollogcnvt - Logical Storage Manager BCL-to-DRL logging conversion utility
SYNOPSIS
/usr/sbin/vollogcnvt [-g diskgroup]
OPTIONS
Limits the conversion of logging subdisks to volumes in the specified disk group.
DESCRIPTION
The vollogcnvt script is a migration tool for Logical Storage Manager (LSM) administrators who are currently using the block-change logging
(BCL) feature. Beginning with the Version 5.0 release of Tru64 UNIX, the BCL feature of LSM is being replaced with the dirty-region logging
(DRL) feature.
The vollogcnvt script attempts to convert volumes with BCL enabled to volumes with DRL enabled. If called without specifying a disk group,
vollogcnvt attempts the BCL-to-DRL conversion for all volumes across all disk groups.
If logging cannot be re-enabled in the DRL scheme, a warning is sent to the console.
For volumes whose BCL subdisks will not work in the DRL scheme, logging is disabled.
Log subdisks that cannot be converted to DRL will be disassociated from its volume only if at least one of the log subdisks for that volume
could be converted. Otherwise, the configuration will not change and logging will be disabled. Those volumes that could not be converted,
for example all of its log subdisks are too small, will have logging disabled.
At system startup, the vollogcnvt script runs automatically and logs such errors to binlog and sends mail to root. This happens at each
reboot until the DRL is manually converted or when logging is disabled. If the script runs at startup or manually, warnings are sent to
the console.
For details and guidelines on using DRL, refer to the Logical Storage Manager guide.
SEE ALSO binlogd(8), dia(8), volintro(8)vollogcnvt(8)