of course someone could have manipulated this command, but more obvious, bootinfo is a command with nice outputs for monitoring tools or configuration management databases, and these tools normally don't run as root user
so you might have changed the permission for this command, so it can be run as non root user (since most pvs on the vio server are not part of volume groups, lspv will not work, so you will most likely use bootinfo -s for example)
changing these attributes may lead to other errors in your environment
Hi,
I want to know wheather partition size for installation of vio client can be specified on vio server
example
If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Lucky me, someone has installed a server and got it running with the best intentions, but leaving me a headache. :wall:
We have a simple p520 with 4 disks. 2x145Gb & 2x300Gb. The smaller disk pair have been built into a VIO mirrored rootvg, and quite right too.
The other two disks form a... (3 Replies)
Hi
My vio client is getting its virtual Ethernet services from dual vio servers. What command if I execute on the vio
client will get me the names of the vio servers ? (2 Replies)
trying to put VIO server software into this p520, firmware upgraded to the latest and greatest..SF240_415_318 , I think
a few questions, on this practice AIX machine on AIX 7.1
VIO can only be installed if ASMI or HMC is running ???
if so, perhaps ASMI is much simpler, since I will need to... (2 Replies)
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Hi All,
I've been trying to create a new LPAR for some days now but I can't get the VIO server to recognize the new LPAR. This is what I did:
On HMC create new LPAR
On HMC create new virtual scsi adapter for LPAR in VIO profile
On HMC add new virtual scsi adapter for LPAR with DLPAR... (6 Replies)
Hi,
I would like to know installing vio server on local disk and mirroring rootvg,
if I am creating AIX VIO CLIENT(lpar),
and any of single local hard disk failuare.
will it affect lpars? will lpars able to boot.
what needs to be done? (1 Reply)
Hi,
I would like to know after the installation of vio server. how many logical network interfaces will be created on vio server if I am having two physical interfaces on vio server.
I am asking this question because I would like know to on the basis of logical network interfaces creation on... (0 Replies)
Want to run this by you all before opening a PMR with IBM Support.
It's been a few weeks since I have done this so I can't be 100% sure of how I think it worked in the previous version.
We upgraded our HMC's yesterday to 7.7.9 SP2 in hopes of fixing some issues we were having. Today I needed... (4 Replies)
Hello,
I would like to identify the blade or/and bladecenter from the hosted VIO server.
I prefer the "command line" solution. May be kdb.
Like, I want to ask the child about his father.
Thank you (1 Reply)
Discussion started by: x41
1 Replies
LEARN ABOUT OSF1
dop
dop(8) System Manager's Manual dop(8)NAME
dop - Allows a user to execute a privileged program without knowing the root password. The dop command also modifies the action database.
SYNOPSIS
/usr/sbin/dop [-n | -N] [ui:] action [args]
/usr/sbin/dop -a priv[,priv]... action [ui:]pathspec[,[ui:]pathspec]...
/usr/sbin/dop -a priv[,priv]... [ui:]pathspec
/usr/sbin/dop -d action
/usr/sbin/dop [-w | -W]
OPTIONS
Invokes a prompt asking the user if they want to run the command as a user or as root. The root password is required to run as root.
Attempts to run the action with the user privileges. Adds new actions to the dop database. Deletes an existing action from the dop data-
base. Writes a binary image without changing the source. Updates the actionlist from the dop action file and then executes the -w option,
which writes the binary image.
OPERANDS
Name of privileged program to invoke Arguments to pass to the application guarded by the privilege. Comma separated privilege list (see
sysman dopconfig) The fully qualified path name and arguments for the associated action.
When specified by a comma separated pathlist and arguments for multiple user interface domains (ui:), the first ui: argument speci-
fied is used as the default. If no action is specified, then the path base name is used. A run-time argument replaces the first
occurrence of asterisk as a word (for example *) in a string, or else they are ignored. Path arguments should be quoted per the cur-
rent shell. Optional. A user interface domain, typically one of X11, suit, java, menu, cui, or cli.
DESCRIPTION
The dop (Division of Privileges) command can execute an action after proper authentication from the privilege database file. For more
information, see the Security guide.
RESTRICTIONS
You must have root privileges to modify the privileges database.
EXAMPLES
The following example will add an action to the AccountManagement privilege. dop -a AccountManagement adduser_script /usr/sbin/adduser
The following example runs the action adduser_script for the AccountManagement privilege. dop adduser_script
The following example deletes the adduser_script action from the action database. dop -d adduser_script
FILES
Executable file. Executable file for adding or deleting permissions for users and or groups. dop database.
SEE ALSO
Commands: sysman(8)dop(8)