Search results for query: *

actually i did use lslpp to see the specific fileset levels. it appears as far as oslevel is concerned nothing is down level 4.3.3 either.

i looked for that. the filesets that i would suspect (possibly mistakenly) such as bos.net.nfs.client, bos.net.tcp.client, etc, are at the same rev as that of my working nfs clients. oslevel == 4.3.3.0 oslevel -r == 4330-09 whats particularly irksome is the lack of any indication via log or...

mounting the share on the server itself works fine. the share is mountable and usable on other clients also. just this one particular client that has this problem. mounting does not produce errors. accessing the share does not produce errors, but hangs when you access the files or...

checked 1,2 and 3, no communications errors, no NFS client errors, no IP oriented errors. this client has the same problem with any NFS server. the client was originally running AIX 4.2.1. this problem arose after upgrading to 4.3.3.

Hello, Have an odd nfs problem. The client has no problem with mounting. The problem occurs when you access the remote fs. When you run commands like ls or find, the process hangs after partial output. Also, cannot umount the remote filesystem. Each attempt results in "error while...

Hello, having a problem with aix 5.1 (oslevel -r says 5100-04). have 2 18 gb drives in rootvg. want to mirror rootvg. understand that i need to use bosboot for the blv on the second disk (hdisk1). but when i run, bosboot -a -d /dev/hdisk1 i get the following error: bosboot: Boot image is...

Hi, have a host running aix 4.3.3. when any user other than root tries to print, the destination queue changes to down status and the job remains in the queue. have verified permissions and owner/group of related printer files and directories, and that /tmp is also writable. any ideas? thanks...

using the route command worked ok, so i simply added them to rc.net. thanks for the help.

Hello, Having a problem with aix 4.3.3 and hacmp 4.3.1. When cluster services are up, if i add a static route thru smit, i lose my service adapter, it appears to be down. The boot adapter then becomes active for the affected network. My nieve question is, should this work this way? Should...

thanks to all for useful and timely responses.

Hello all, am using an aix 4.3.3 installation. in the /etc/security directory is a file named failedlogin. we're interested in retrieving information about failed login attempts, but this failed login file is not ascii, and i have found no means by way of program or script for retrieving this...

In the file /etc/security/login.cfg you can set "herald" to the string you want to appear instead of "login:". example: herald = "Welcome to ABC Company's RS600\n\nlogin: " review /etc/security/login.cfg for more information.

Yegolev, I don't disagree. But I cannot find where in the system console login has been identified as False or where you would change it True.

Cannot login on console terminal. "login:" prompt appears but nothing you type is echoed back. No further interaction can be done. console is assigned to dumb terminal on tty0: (root)/> lscons /dev/tty0 the following appears in /etc/inittab...

the rmlvcopy worked when I used the pvid of the removed hard drive. Thanks for the advice. Only one small problem left, with the dumpdevice. When you attempt to assign the primary dump device, you get; (root)/var/adm/ras> sysdumpdev -p /dev/hd6 sysdumpdev: 0453-054 Unable to get physical...

hd5 was a bad example of the problem, because it is a special case for mirroring. hd1 (/home) is a good example. Currently I only have 1 valid copy of this lv on hdisk1. lslv hd1 shows there are 2 copies, because it's still configured for mirroring on the disk that was replaced. If I try to...

AIX 4.3.3 System originally had hdisk0 and hdisk1, both 18gb drives. All lvs on hdisk0 had a mirror copy on hdisk1. boot lvm was created on hdisk1 as well. Hdisk0 began reporting errors, IBM FE replaced hdisk0. System was booted from hdisk1. Now when I try to rebuild hdisk0, there...

Used smit update_all to upgrade from 4.3.1 to 4.3.3 modification level. Output from oslevel is still: 4.3.1 lslpp -l shows most filesets to be at least 4.3.3.0 or newer. Anybody know what could be wrong? Thanks. wab62