Sponsored Content
Full Discussion: VIO oem_setup_env user
Operating Systems AIX VIO oem_setup_env user Post 302316006 by funksen on Wednesday 13th of May 2009 07:38:19 PM
Old 05-13-2009
yep it's only for the padmin, but PS1 variable will not be overwritten when running oem_setup_env
 

10 More Discussions You Might Find Interesting

1. AIX

vio server and vio client

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)
Discussion started by: manoj.solaris
1 Replies

2. Shell Programming and Scripting

SSH Remote login to VIO's (padmin) and run oem_setup_env

Hello all, I have been trying to run commands that collect basic info from the VIO's The issue I am having is setting the env with the "oem_setup_env" after I login as "padmin". I usually do the following: ssh server command ssh root@server date , but I need to login set the env and... (0 Replies)
Discussion started by: dfezz1
0 Replies

3. AIX

VIO Redundancy

Hi Guys, I'm working on building a new 595 machine.. I'm try to achieve high availability for the VIO clients using 2 VIO servers, The ethernet part is satisfied using SEA failover, Now how do I achieve redundancy for the disks, its the servers internal disk attached to the scsi cards... ... (2 Replies)
Discussion started by: kkeng808
2 Replies

4. AIX

Vio Build

I am planning carving out dual VIO servers on a P750 based and would like to know how to allocate internal disks to the VIOS. This has 4 internal disks and I would to assign 2 disks to each VIO. This is what I was thinking of assigning . Any advise? vio1 U5802.001.9K8H757-P1-C1 PCI-E x8... (17 Replies)
Discussion started by: mk8570
17 Replies

5. AIX

sddpcm on vio

I have same lun (hdisk3) assigned to 2 vios server (dual vio server) and this is mapped to the client lpar. I have sddpcm on the VIO. On the VIOA, the attributes for fscsi1 and fscsi3 are set to fast_fail and dyntrk is set to yes Now, if I do a lqueryvg -Atp on the hdisk3, I get a "DISK... (4 Replies)
Discussion started by: mk8570
4 Replies

6. Red Hat

vio in linux

I am working in AIX. In a P series machine both aix and linux os can install.. specific command is there for aix to list out the vio servers details mapped in a frame(ie. lssrc "IBM.ManagementServer", like that..) is there any command is der to list out vio servers details in linux or how to find... (1 Reply)
Discussion started by: muralikrish
1 Replies

7. AIX

vio server ethernet to vio client ethernet(concepts confusing)

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)
Discussion started by: newtoaixos
1 Replies

8. AIX

VIO Server

Hi, I am facing an issue in vio server. When I run bosboot -ad /dev/hdisk0 I am getting an error trustchk: Verification of attributes failed: /usr/sbin/bootinfo : accessauths regards, vjm Please use code tags next time for your code and data. (8 Replies)
Discussion started by: vjm
8 Replies

9. AIX

Problems with VIO O/S 2.2.3

I hope someone has experienced this problem before and can help. I have a P730 (8231-E2D) which is fitted with 8 IBM SAS disks on 2 separate SISSAS controllers. The disk type is ST9146853SS (Seagate SAS 146Gb). The problem occurs when I try to install the VIO server software at 2.2.3. It... (3 Replies)
Discussion started by: johnf
3 Replies

10. AIX

Reboot VIO - OK?

We've got two datacenters and in every datacenter 2 VIOs. The VIO manages the I/O of the LPARs. So: Is it possible to reboot the VIO without shuting down an LPAR:wall: (4 Replies)
Discussion started by: DiViN3
4 Replies
newgrp(1)							   User Commands							 newgrp(1)

NAME
newgrp - log in to a new group SYNOPSIS
Command /usr/bin/newgrp [-| -l] [group] sh Built-in newgrp [argument] ksh Built-in *newgrp [argument] ksh93 Built-in +newgrp [argument] DESCRIPTION
Command The newgrp command logs a user into a new group by changing a user's real and effective group ID. The user remains logged in and the cur- rent directory is unchanged. The execution of newgrp always replaces the current shell with a new shell, even if the command terminates with an error (unknown group). Any variable that is not exported is reset to null or its default value. Exported variables retain their values. System variables (such as PS1, PS2, PATH, MAIL, and HOME), are reset to default values unless they have been exported by the system or the user. For example, when a user has a primary prompt string (PS1) other than $ (default) and has not exported PS1, the user's PS1 is set to the default prompt string $, even if newgrp terminates with an error. Note that the shell command export (see sh(1) and set(1)) is the method to export variables so that they retain their assigned value when invoking new shells. With no operands and options, newgrp changes the user's group IDs (real and effective) back to the group specified in the user's password file entry. This is a way to exit the effect of an earlier newgrp command. A password is demanded if the group has a password and the user is not listed in /etc/group as being a member of that group. The only way to create a password for a group is to use passwd(1), then cut and paste the password from /etc/shadow to /etc/group. Group passwords are antiquated and not often used. sh Built-in Equivalent to exec newgrp argument where argument represents the options and/or operand of the newgrp command. ksh Built-in Equivalent to exec to/bin/newgrp argument where argument represents the options and/or operand of the newgrp command. On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways: 1. Variable assignment lists preceding the command remain in effect when the command completes. 2. I/O redirections are processed after variable assignments. 3. Errors cause a script that contains them to abort. 4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a variable assignment. This means that tilde substitution is performed after the = sign and word splitting and file name genera- tion are not performed. ksh93 Built-in Equivalent to exec to/bin/newgrp argument where argument represents the options and/or operand of the newgrp command. On this man page, ksh93(1) commands that are preceded by one or two + (plus signs) are treated specially in the following ways: 1. Variable assignment lists preceding the command remain in effect when the command completes. 2. I/O redirections are processed after variable assignments. 3. Errors cause a script that contains them to abort. 4. They are not valid function names. 5. Words, following a command preceded by ++ that are in the format of a variable assignment, are expanded with the same rules as a variable assignment. This means that tilde substitution is performed after the = sign and field splitting and file name genera- tion are not performed. OPTIONS
The following option is supported: -l | - Change the environment to what would be expected if the user actually logged in again as a member of the new group. OPERANDS
The following operands are supported: group A group name from the group database or a non-negative numeric group ID. Specifies the group ID to which the real and effective group IDs is set. If group is a non-negative numeric string and exists in the group database as a group name (see getgr- nam(3C)), the numeric group ID associated with that group name is used as the group ID. argument sh and ksh only. Options and/or operand of the newgrp command. ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of newgrp: LANG, LC_ALL, LC_CTYPE, LC_MES- SAGES, and NLSPATH. EXIT STATUS
If newgrp succeeds in creating a new shell execution environment, whether or not the group identification was changed successfully, the exit status is the exit status of the shell. Otherwise, the following exit value is returned: >0 An error occurred. FILES
/etc/group System group file /etc/passwd System password file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: /usr/bin/newgrp, ksh, sh +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ |Standard |See standards(5). | +-----------------------------+-----------------------------+ ksh93 +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Uncommitted | +-----------------------------+-----------------------------+ SEE ALSO
login(1), ksh(1), ksh93(1), set(1), sh(1), Intro(3), getgrnam(3C), group(4), passwd(4), attributes(5), environ(5), standards(5) SunOS 5.11 2 Nov 2007 newgrp(1)
All times are GMT -4. The time now is 08:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy