on one of our AIX VIO LPARs I can not remove hdiskpower devices, which seemed to presented to the VIO in an incorrect way and behaviour (not all paths can be seen, pseudo device name is unknown etc.)
Therefor I decided to deattach the hdiskpower device from PowerPath controll by:
1. powermt remove <hdiskpowerXX> ---> did not work
then directly via:
3. rmdev -Rdl <hdiskpowerXX> --> i got this message:
rmdev: 0514-516 Device configuration database lock service timed out.
Please retry the command later.
Is there any way out of this mass, without rebooting the VIOS LPAR?
Sincerely
Tomek
Moderator's Comments:
edit by bakunin: please use CODE-tags for for commands, terminal output and file content you present. Actually this is a rule here and you have accepted it. Thank you.
Hi intelligent beings,
I am trying to write a script that
1. Accepts the following arguments:
store_number
div_number
user_id
div_code
2. Will read from a configuration file to get the Database
3. Use the div_code to determine which value to retrieve from the configuration file
... (1 Reply)
Hi Everyone,
I want to know which database (Oracle,SQL,Informix...) are installed on Unix Machine.
I have very limited experience on Unix Environment, :confused: So I have no idea of getting this information. But in windows we can get Service names using WMI. Is there any similar way of Doing... (5 Replies)
Hi,
I have a Solaris 5.6 having an Oracle database.Now this server is being accessed by a web service interface.I cannot see anything other than httpd daemons running on my server. There is a frequent problem of the stopping of these httpd daemons . Now i am asked to find the root case.I talked... (1 Reply)
Dear all
i have a sun SL500 tape library attached to my AIX box while issue the command cfgmgr i have the below issue
test>cfgmgr
cfgmgr: 0514-621 WARNING: The following device packages are required for
device support but are not currently installed.
devices.fcp.changer
please... (3 Replies)
I configured a WebDAV server using Apache. Here is my configuration:
DAVLockDB /var/www/DAVLock.db
<Location /majid>
AllowOverride None
Options +Indexes
DAV On
AuthUserFile
/var/www/users.db
AuthName Authentication
AuthType Basic
<Limit... (1 Reply)
In generally I use vsftp but I want to improve our security so I decide to use sftp instead of vsftp.
We know that ssh,scp and sftp are in openssh server.
How can I lock only sftp user to their home folder? And to prevent some users for sftp like root as such in vsftp daemon? (3 Replies)
Hello,
I was trying to install python on aix and it was taking too long and I closed the terminal.
Now when i issue the command rpm -qa instead of getting all the rpms installed I'm getting the following error.
root:stud -> $ rpm -qa
cannot get shared lock on database
rpmQuery: rpmdbOpen()... (2 Replies)
OS is redhat 7.
# nmcli dev
DEVICE TYPE STATE CONNECTION
virbr0 bridge disconnected --
eno16777736 ethernet disconnected --
eno33554960 ethernet disconnected --
virbr0-nic ethernet disconnected --
lo ... (1 Reply)
Discussion started by: tien86
1 Replies
LEARN ABOUT OPENDARWIN
pseudo
pseudo(4) File Formats pseudo(4)NAME
pseudo - configuration files for pseudo device drivers
DESCRIPTION
Pseudo devices are devices that are implemented entirely in software. Drivers for pseudo devices must provide driver configuration files to
inform the system of each pseudo device that should be created.
Configuration files for pseudo device drivers must identify the parent driver explicitly as pseudo, and must create an integer property
called instance which is unique to this entry in the configuration file.
Each entry in the configuration file creates a prototype devinfo node. Each node is assigned an instance number which is determined by the
value of the instance property. This property is only applicable to children of the pseudo parent, and is required since pseudo devices
have no hardware address from which to determine the instance number. See driver.conf(4) for further details of configuration file syntax.
EXAMPLES
Example 1: A sample configuration file.
Here is a configuration file called ramdisk.conf for a pseudo device driver that implements a RAM disk. This file creates two nodes called
"ramdisk". The first entry creates ramdisk node instance 0, and the second creates ramdisk node, instance 1, with the additional disk-size
property set to 512.
#
# Copyright (c) 1993, by Sun Microsystems, Inc.
#
#ident "@(#)ramdisk.conf 1.3 93/06/04 SMI"
name="ramdisk" parent="pseudo" instance=0;
name="ramdisk" parent="pseudo" instance=1 disk-size=512;
SEE ALSO driver.conf(4), ddi_prop_op(9F)
Writing Device Drivers
SunOS 5.10 15 Jun 1993 pseudo(4)
02-18-2016
