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 X11R4
runuser
RUNUSER(1) User Commands RUNUSER(1)NAME
runuser - run a command with substitute user and group ID
SYNOPSIS
runuser [options] -u user [[--] command [argument...]]
runuser [options] [-] [user [argument...]]
DESCRIPTION
runuser allows to run commands with a substitute user and group ID. If the option -u is not given, it falls back to su-compatible seman-
tics and a shell is executed. The difference between the commands runuser and su is that runuser does not ask for a password (because it
may be executed by the root user only) and it uses a different PAM configuration. The command runuser does not have to be installed with
set-user-ID permissions.
If the PAM session is not required then recommended solution is to use setpriv(1) command.
When called without arguments, runuser defaults to running an interactive shell as root.
For backward compatibility, runuser defaults to not change the current directory and to only set the environment variables HOME and SHELL
(plus USER and LOGNAME if the target user is not root). This version of runuser uses PAM for session management.
OPTIONS -c, --command=command
Pass command to the shell with the -c option.
-f, --fast
Pass -f to the shell, which may or may not be useful depending on the shell.
-g, --group=group
The primary group to be used. This option is allowed for the root user only.
-G, --supp-group=group
Specify a supplemental group. This option is available to the root user only. The first specified supplementary group is also used
as a primary group if the option --group is unspecified.
-, -l, --login
Start the shell as a login shell with an environment similar to a real login:
o clears all the environment variables except for TERM
o initializes the environment variables HOME, SHELL, USER, LOGNAME, PATH
o changes to the target user's home directory
o sets argv[0] of the shell to '-' in order to make the shell a login shell
-m, -p, --preserve-environment
Preserve the entire environment, i.e. it does not set HOME, SHELL, USER nor LOGNAME. The option is ignored if the option --login is
specified.
-s, --shell=shell
Run the specified shell instead of the default. The shell to run is selected according to the following rules, in order:
o the shell specified with --shell
o the shell specified in the environment variable SHELL if the --preserve-environment option is used
o the shell listed in the passwd entry of the target user
o /bin/sh
If the target user has a restricted shell (i.e. not listed in /etc/shells) the --shell option and the SHELL environment variables
are ignored unless the calling user is root.
--session-command=command
Same as -c , but do not create a new session. (Discouraged.)
-V, --version
Display version information and exit.
-h, --help
Display help text and exit.
CONFIG FILES
runuser reads the /etc/default/runuser and /etc/login.defs configuration files. The following configuration items are relevant for
runuser:
ENV_PATH (string)
Defines the PATH environment variable for a regular user. The default value is /usr/local/bin:/bin:/usr/bin.
ENV_ROOTPATH (string)
ENV_SUPATH (string)
Defines the PATH environment variable for root. The default value is /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin.
ALWAYS_SET_PATH (boolean)
If set to yes and --login and --preserve-environment were not specified runuser initializes PATH.
EXIT STATUS
runuser normally returns the exit status of the command it executed. If the command was killed by a signal, runuser returns the number of
the signal plus 128.
Exit status generated by runuser itself:
1 Generic error before executing the requested command
126 The requested command could not be executed
127 The requested command was not found
FILES
/etc/pam.d/runuser
default PAM configuration file
/etc/pam.d/runuser-l
PAM configuration file if --login is specified
/etc/default/runuser
runuser specific logindef config file
/etc/login.defs global logindef config file
SEE ALSO setpriv(1), su(1), login.defs(5), shells(5), pam(8)HISTORY
This runuser command was derived from coreutils' su, which was based on an implementation by David MacKenzie, and the Fedora runuser com-
mand by Dan Walsh.
AVAILABILITY
The runuser command is part of the util-linux package and is available from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils
/util-linux/>.
util-linux July 2014 RUNUSER(1)