Search results for query: *

You could write a script whick compares the first field in the passwd file with the relevant output from the last command

I don't know C programming, but to get over the passwd permissions problem, you could implement sudo Kind Regards

HP have a product called CIFS, which is based on SAMBA. http://www.hp.com/products1/unix/operating/hpuxcifs9000/ I understand the product is free, they change on support Kind Regards

You can set password ageing on a user-by-user basis from SAM. Choose Accounts for Users and Groups Users Click on the user you want to enable it for Actions Modify Click Modify Password Options On the drop-down menu choose Enable Password Ageing and fill in the boxes Alternatively, you can...

...PE Size (Mbytes) 4 Total PE 2046 Alloc PE 1463 Free PE 583 In this case 4*583=2332MB free You may also have disk(s) on your system which have not been assigned to volume groups. #ioscan -funC disk will tell you the...

The HP IT Resouce Centre has a comprehensive database for truobleshooting and knowledge trees etc. However, you need a support contract system handle to provide access to most of it. The link to the Europena HP ITRC is...

Have you tried www.docs.hp.com Regards

Use the traceroute command to determine at which point the problem lies. Use the netfmt command to consider in detail the latest nettl.log. i.e netfmt -s /var/adm/nettl.LOG00 | more Use netstat to look for errors. Kind Regards

Did the /etc/rc.log record any useful info following the panic, I wouldn't have thought so, but was a crash directory created in /var/adm/crash, if so does the INDEX file tell you any more. Can the dmesg or OLDsyslog.log tell you anything. Why don't you post the rc3.d script for us to test.

When you output to a device (cpio -o) you need to use the (>) and not the input (<).

1) I believe that the SAM backup log is /var/sam/log/br_log 2) To check the tape for the header use frecover -V /tmp/volumefile -f /dev/whatever your device is To check what was backed up on the tape frecover -I /tmp/indexfile -f /dev/whatever your device is Although the most correct way to...

I would use Ignite to extend /usr, you get an option when you boot off the recovery CD to set the sizes of the filesystems.

...Then you need to check if there is space available in the volume group to extend the logical volume. To check the volume group use vgdisplay -v vg** replacing vg** with the volume group name from earlier. The vgdisplay output will show you the available space left in the volume group that...

Because it is a 9.X patch, I doubt very much that you will find it available for download because the OS is two past being supported. I would beg the question as to why you need the patch and whether upgrading could be an option to get you over your difficulties. Maybe someone, could send you...

...and provided lvdisplay for vg01, but your commands are for vg00. 2) If you are extending vg00 to include three disks, wouldn't you want to implement Physical Volume Groups to take out the single point of failure, i.e mirror your current 2*18GB disks to the new 36GB disk. Good Luck Queenie

Hi Check the /etc/rc.log which records the progress of the startup scripts to check for more info. Also because you had to do a further reboot to get the ssytem back, the captured information would now be in OLDsyslog.log. Also check root's mail for further clues. Kind Regards

Hi I hate to jump to cause, however my gut feeling is that you have another device, probably a laptop that is configured with the same IP address and when it is plugged in the network, it causes problems like what you see here. #cd /var/adm look for the most recent log file of the form...

Make sure that you're not cd'd into the directory that you want to umount, also if you have used pfs_mount, you must use pfs_umount, or you'll end up with a stale nfs handle message and reboot will be the only option. Kind Regards

I have seen these messages before when directory permissions are not set correctly or when links are not in place. Kind Regards

This answer is extracted from HP web site Running the following command after having run lvextend: fsadm -b 262144 /opt produces the following error message: &quot;/dev/vg00/rlvol5 is currently XXXXX sectors, size will be increased.&quot; &quot;Attempt to resize /dev/vg00/rlvol5 failed...