Sponsored Content
Top Forums Web Development Which technology is used on this website? Post 302908622 by Akshay Hegde on Wednesday 9th of July 2014 06:57:27 AM
Old 07-09-2014
Go through

https://iosscripts.com/

its jQuery Plugins
This User Gave Thanks to Akshay Hegde For This Post:
 

6 More Discussions You Might Find Interesting

1. AIX

AIX Technology Level 9

Hi Guys I am currently running AIX 5.3 technology level 6 on a 570, but want to go up to level 9. However I am struggling to find on IBM's website the new features that it brings in, along with the commands for these new features. Can any one help me with this? Thanks (7 Replies)
Discussion started by: ryanbsc@gmail.c
7 Replies

2. AIX

Update technology level

Hello I update one lpar from TL03 to TL06 reboot and check with lppchk -v, errpt and everything looks fine then I commit my fileset and I update to TL08-04. The installation was ok. I reboot my machine again check with lppchk -v and errpt and its ok, but when I type oslevel -s I get this... (5 Replies)
Discussion started by: lo-lp-kl
5 Replies

3. Shell Programming and Scripting

Web Technology

Hi Experts, This may sound stupidity.....anyhow....let me ask the doubt, Even though shell is just a scripting language, can anyone tell me, whether web pages can be created with embedding some concepts. In any other scripting language, whether web pages can be created. If so, suggest me in... (6 Replies)
Discussion started by: kritibalu
6 Replies

4. What is on Your Mind?

What technology advancement you need ?

Though we got surplus amount of primary memory, and big HDD when comapared to 20 or 30 years back, and cloud computing... What other technology advancement you still need ? Note: Feel free to add more options to this poll. (21 Replies)
Discussion started by: thegeek
21 Replies

5. Red Hat

Clustering Technology Documentation

Hello, I'm new in this forum. I'll have a new project to change architecture for our servers. From one server where we found database oracle 9i and Oracle application ebs 11 installed in HPux to cluster that contain nodes in redhat. Can you give me a detailed documentation that... (1 Reply)
Discussion started by: Safi1982
1 Replies

6. What is on Your Mind?

Does anyone know what technology this logo belongs to?

It came in a template full of techy-related stickers for laptop (like Docker, K8s, BigData, RHEL, AWS, etc) but I have no clue what it represents. Any idea? https://i.imgur.com/7ILp105.png Thanks. (7 Replies)
Discussion started by: verdepollo
7 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)
All times are GMT -4. The time now is 03:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy