9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i vi .profile Set DATE `date +%m%d%Y%H%M`, but after logout/login, echo $DATE, it shows: Fri Mar 23 15:01:53 EDT 2012, i want to show: 032320121501
please ignore.
vi /etc/profile, and export DATE=`date +%m%d%Y%H%M`, worked fine now. (0 Replies)
Discussion started by: lawsongeek
0 Replies
2. Shell Programming and Scripting
Could you please explain me what is the difference between .login, .tcshrc ,.profile file . Can I keep .tcshrc file in two different location .Actually my problem is I have one server in which another server is mounted so I have two programs which refers to two different versions of java and I need... (1 Reply)
Discussion started by: maitree
1 Replies
3. Solaris
Greetings! I'm new here and excited to get aquianted with this site! Seems like a good source of knowledge!
Anyways, my first problem de'jour deals with the following....
We have dual monitors(top/bottom) for our system. The problem is that the solaris login window is split between the top... (7 Replies)
Discussion started by: ruberked
7 Replies
4. UNIX for Dummies Questions & Answers
Hey everyone,
I'am a little new here and experincing Unix for the first time. I was wondering if somone could help me with this question i'am a bit stuck on
Looking at the content of .profile login script
The .profile file is in your login directory. It is a startup script file... (1 Reply)
Discussion started by: worldsoutro
1 Replies
5. UNIX for Dummies Questions & Answers
Hello All,
My Problem is -> How can we get UNIX id from open mail authentication (Windows ID) in UNIX.
In following command we are using domain name, which may change in your reference.
As, if we use following command.
ypcat passwd | grep rohitp | cut -d: -f5 | cut -d, -f1
=> we get... (0 Replies)
Discussion started by: pandey.rohit
0 Replies
6. UNIX and Linux Applications
Dear experts ...
Please any one can describe the diffrence between this three
1) . cshrc
2) .profile
3) .login
cheers
syed (1 Reply)
Discussion started by: smuqtaderali
1 Replies
7. UNIX for Dummies Questions & Answers
I have modified the .profile in my profile and I don't see any effect.
Why the changes don't have effect?
I tried both on the account at a server where I have limited permissions as user and to my local pc (as user).
Is it the .profile overridden by some other file? It looks weird because I... (8 Replies)
Discussion started by: myle
8 Replies
8. UNIX Desktop Questions & Answers
Dear Friends
I'm using Hp-unix release b.11.11 and i'm facing a problem to login through telnet session. i can login only by user root but other users can not login.
but if i use x window application like (reflection X) all users can login with no problem.
please kindly advice me on how to... (0 Replies)
Discussion started by: hai_jab
0 Replies
9. UNIX for Dummies Questions & Answers
Hello again !
Thanks for response of my first question. there is my second quesiton why i have local.profile instead of .profile file ?
my all files in pwd shoes local. before any file.
is anybody can tell me about that ?
Thanks
Abid Malik (5 Replies)
Discussion started by: abidmalik
5 Replies
auth.adm(1M) auth.adm(1M)
NAME
auth.adm - activate, deactivate, or query about HP-UX Integrated Login
SYNOPSIS
tech_name [ tech_name ]
[ tech_name[:tech_name]... ]
[ tech_name:parameter=value[:parameter=value]... ]...
[
filename ]
DESCRIPTION
The command makes it easy to activate, deactivate or query about HP-UX Integrated Login.
During activation,
sets up a machine to obtain integrated login behavior using any of the following commands: and
saves the Integrated Login configuration, specified by
and arguments, in the file This configuration file specifies the authentication technologies used to authenticate users on a system. System
administrators can specify the technology for system login; where this login technology is unavailable, a fallback technology for system
login can also be specified. System administrators can also specify technologies for additional user authentications that will be done
after a user has successfully completed the system login phase.
Integrated behavior of and is obtained by replacing the current with one that specifies the behavior requested by the arguments. auth.adm
provides an option of enabling the nsswitch for DCE technology. The is updated with "dce" keyword if this option has been selected. In
this scenario the name service requests for user/group information will be obtained from DCE depending on the configuration.
After NSS switch is enabled, an option is provided to export the DCE user/group information to and via a cron job. program could also be
run manually to do this job.
Upon deactivation, restores files that were present on the system before Integrated Login was installed. It also removes the configuration
file.
When making a query,
reads the file and prints the result of the query to stdout or to filename specified by the argument.
All actions performed by
are logged into the file
ARGUMENTS
recognizes the following arguments:
activates HP-UX Integrated Login.
tech_name
an abbreviated name representing an authentication technology. Starting with the 10.0 release, the tech_name's supported
are:
for DCE Registry
for /etc/passwd and other HP-UX login technologies.
tech_name
specifies the technology used for system login.
tech_name
specifies the technology used for fallback login.
tech_name[:tech_name]...
specifies technologies used for additional authentications after a user has been successfully logged in to a system.
tech_name:parameter=value[:parameter=value]...
specifies configurable parameters applicable to a technology. Parameters for different technologies can be specified by
repeating the argument. Starting with the 10.30 release, the configurable parameters supported include the following:
Timeout (in seconds) on communications with a technology.
Default values for TIMEOUT are as follows.
180 seconds
ignored
Password expiration warning period (in days). If the user's password is due to
expire within the specified number of days, the user receives a warning message during login. This parameter
applies to DCE technology only. If this parameter is not specified, no warning is given.
Password force-change period (in days). If the user's password is due to
expire within the specified number of days, the user is forced to change the password before login is allowed.
This parameter applies to the DCE technology only. If this parameter is not specified, a password change is not
forced.
Enable DCE TGT to be forwardable. When forwarding a user's DCE TGT from machine A
to machine B, it enables the user from machine A to reuse its Kerberos credentials on machine B. A parameter
value is required, but its content is ignored. This parameter applies to DCE technology only.
deactivates HP-UX Integrated Login.
makes a query about the current Integrated Login configuration.
filename
prints result of a query to filename.
EXAMPLES
The following command activates HP-UX Integrated Login. The configuration is set to login the user upon successful password verification by
DCE. In the case where DCE is not available, a fallback for login via /etc/passwd or another HP-UX technology is configured. (Note that
this strategy is effective only if the HP-UX password and DCE password are identical.)
The following command activates HP-UX Integrated Login. The configuration is
set to login the user upon successful password verification by /etc/passwd or another HP-UX technology. After machine access has been
granted to the user, the configuration specifies that a DCE login should also be done.
RETURN VALUE
returns one of the following:
Successfully completed
Error(s) occurred
WARNING
If activation or deactivation fails to complete, the error(s) should be corrected and re-execution of the activation/deactivation should be
done. cannot deactivate a failed activation.
NOTE
auth.adm will restart the pwgrd daemon after the ilogin daemon is started, if it was already running.
AUTHOR
was developed by HP.
FILES
log file containing records of actions performed by
SEE ALSO
auth.adm(1M)
