How to reactivate user with command(no SAM)


 
Thread Tools Search this Thread
Operating Systems HP-UX How to reactivate user with command(no SAM)
# 8  
Old 11-11-2007
thanks alot 411seeker, I trying man modprpw for many options.


arm_naja
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. HP-UX

Display SAM user list at the command line

Hello, I've been doing Linux and AIX administration for years, but I'm very new to HPUX. We have an old audit process which involves someone manually using sam to generate user lists. I'd like to kill that old process with fire... But... After working a bit in the morning to try and pull... (3 Replies)
Discussion started by: Celt1977
3 Replies

2. Linux

Reactivate an account

Hello, I had this issue today. One of my co-workers accounts was looked due to inactivity. The passwd -u command didn't work. So I did what I posted below. I don't think this the proper way to do this. What is the right to reactivate an account in Linux? After I changed the inactivity to never he... (2 Replies)
Discussion started by: bitlord
2 Replies

3. Shell Programming and Scripting

root user command in shell script execute as normal user

Hi All I have written one shell script for GPRS route add is given below named GPRSRouteSet.sh URL="www.google.com" VBURL="10.5.2.211" echo "Setting route for $URL for GPRS" URL_Address=`nslookup $URL|grep Address:|grep -v "#"|awk -F " " '{print $2}'|head -1` echo "Executing ... (3 Replies)
Discussion started by: mnmonu
3 Replies

4. HP-UX

Getting command (command line) from SAM?

Hi I hope this is easy and sorry if I am using the wrong HP terms. I am looking for a way to glean the command line information from a process I run in SAM? In AIX I can just select any options I want for particular process and hit F6 and the command line is shown on the screen for use in... (3 Replies)
Discussion started by: KmJohnson
3 Replies

5. HP-UX

Adding user to a group without SAM

How can I add a user to a specific group without using SAM? I know I can user modprpw -G, but that will overwrite any groups the user is in with the ones I specify. I need to assume that I do not know what groups the user is already in, so I can't put them in the modprpw command. I just need... (2 Replies)
Discussion started by: paqman
2 Replies

6. HP-UX

Where are SAM user templates stored?

Hey, new here, so be nice! I'm trying to write a little script to automate the user creation process on one of our boxes. But I would like to be able to use the templates that we have set up in SAM. Is the information in these templates stored in a file somewhere, that I can reference in my... (5 Replies)
Discussion started by: paqman
5 Replies

7. UNIX for Dummies Questions & Answers

How to reactivate expired account in Linux as a root user

I am an administrator of a Red Hat Enterprise Linux system. Now one account expired. I wonder how to reactivate the account. Thanks (2 Replies)
Discussion started by: cy163
2 Replies

8. HP-UX

help on sam

hi, any idea how to get more info on the usage, unix equivalent of sam in hp-ux? thanks (7 Replies)
Discussion started by: yls177
7 Replies
Login or Register to Ask a Question
samlog_viewer(1)					      General Commands Manual						  samlog_viewer(1)

NAME
samlog_viewer - a tool for viewing and saving the SAM logfile SYNOPSIS
mmddhhmm[[cc]yy]] mmddhhmm[[cc]yy]] user] ofile] [file] DESCRIPTION
The command enables the viewing of part or all of the SAM logfile (or another file containing data in the same format) at varying levels of detail. This tool is run by SAM whenever the option is chosen. It can also be run independently of SAM, in either interactive or nonin- teractive mode. The command executes in either interactive or noninteractive mode, depending on the options given. In noninteractive mode, filters the source file and writes the resulting data either to stdout or to a destination file. In interactive mode, displays a graphical user inter- face enabling you to try different combinations of filtering, save one or more versions of the source file to other files, scroll back and forth among the logfile entries, etc. Under no circumstances is destructive to the contents of the SAM logfile (or whatever source file is specified by file). The contents of the source file are filtered and displayed (or output) according to the settings of the available filters. Multiple instances of can be run simultaneously without harmful effects. Filters supports three types of filters: level of detail, date/time, and user filters. These filters can be used in combination to provide highly selective logfile viewing. The level of detail filters control how much detail is displayed. The SAM logfile may contain entries of many different types. The entry types currently supported are: summary, detail, verbose, error, and note. The level of detail filters display some or all of these entry types, depending on which filter is chosen. The level of detail filters are: Displays only the higher level messages. These include summary, error, and note (warnings, other entries worthy of special attention) entry types. Includes level of detail, and adds detail log entries. If no level of detail is specified, this is the default. Includes level of detail, and adds verbose log entries. Displays only the literal commands that were executed. These commands may include HP-UX commands as well as SAM commands and scripts. The date/time filters are used to ask for entries written since a specific date/time, before a specific date/time, or both. The user filters are for viewing only those entries written by a particular user. If invoked with the option, its argument is used as the user whose entries should be shown. If user filtering is selected by the option, displays only entries made by that user and disallows any changes to the user filtering. This is useful for allowing nonprivileged users to run and see only those entries that pertain to them. Otherwise, allows the user filtering to be changed, or completely disabled, from its interactive filtering screen. Options The following options enable you to set up filtering and other attributes. If runs interactively, these attributes may also be set and modified in the various supported menus and displays. The available options are: The option sets the start date/time filter to the date/time given by its argument. The date/time is specified in the same way as it is for the command (see date(1)): mm Month specified as a two digit number (e.g., dd Day specified as a two digit number. hh Hour specified as a two digit number (24-hour clock form). mm Minute specified as a two digit number. cc Century minus one. cc is optional when specifying the year. yy The last two digits of the desired year. If this is not specified, the current year is used. To specify a year in two digits, the valid ranges are 70-99 (20th century) and 00-37 (21st century). To specify a year in four digits, the valid range is 1970-2037. If no start time is given, the beginning of the log is used as the start time. The option sets the end date/time filter to the date/time given by its argument. The date and time is speci- fied as described above for the option. If no end time is given, then an end date/time of infinity (no end time) is used. The option sets the desired level of detail. One of the letters must be specified as the required argument. The level of detail is set as follows: If the option is not specified, the level of detail is used by default. The option sets the user filter to the user name or user ID specified by user. Only entries logged by this user are displayed. If the option is omitted, entries logged by all users are displayed by default. The option causes the filtered output to be written to the output file ofile. The option implies the option described below. If ofile is the output is written to stdout. If is omitted, the output is written to either stdout (if is specified) or to the interactive display (if is omitted). The option enables automatic timestamping. If specified, each log entry is tagged with the time of day at which it was written. Timestamping is disabled by default. The option forces noninteractive behavior. If specified, runs noninteractively, using the default or specified values for all supported options and source/destination files. file Specifies the name of the file from which log data is read. The format of the data in the specified file must be the same as that used for raw SAM logfile data. If omitted, the SAM logfile is read. If file is stdin is read and runs noninteractively. If given, file must be the last argument specified on the command line. EXAMPLES
Capture the current contents of the SAM logfile using default filtering, and put into the file The following example does the same thing: View only the commands executed by SAM on behalf of user between 8am June 5, 1994 and 10pm August 14, 1994, and view the data interac- tively: Noninteractively read data from stdin, timestamp it, and save the result in a file called Do the same as above, but instead have the data appear on stdout: or FILES
SAM logfile. Archived version of created when the logfile is automatically trimmed by SAM when its size becomes too large. Its contents are included in the log entries read by Temporary files used by SEE ALSO sam(1M). samlog_viewer(1)