Sponsored Content
Top Forums UNIX for Advanced & Expert Users Possible GUI to Command-Line Interface Translator? Post 302068612 by buffoonix on Sunday 19th of March 2006 05:40:37 PM
Old 03-19-2006
I think the tool RTM was referring to is SMIT or SMITTY.
I am not into AIX either but I have access to AIX boxes and occassionally am forced
to use SMIT.
Because of this I am not particular fond of AIX because you are forced to do certain sysadmin tasks with such a tool.
As far as I remember SMIT gives you the chance to view the CLI commands SMIT was using behind the scenes, which on the other hand is nice.
HP-UX has a similar tool which is called SAM.
Like SMIT SAM dumps the OS commands for your inspection.
But unlike SMIT SAM isn't at all mandatory for any sysadmin task
but rather just another option,
which is exactly what I expect from a decent Unix OS.
In fact there are some sysadmin tasks that can only be done on the command line on HP-UX.
But you shouldn't regard this as a drawback.
Generally on Unix systems the CLI offers you the greatest liberty to perform your tasks exactly the way that suit your needs and preferences best.
And for repetitive or complex tasks you always have the choice to script.
The GUIs lure you with the false promise to make system administration clicking easy.
But I haven't come across any GUI that really lives up to their expectation.
I would advise to get as much shell exposure as possible.
You could however start with a tool like SMIT, SAM, Yast or whatever comes with your Unix.
And keep reading the manpages.
What discerns the Unix guru from the average user is only the fact that the first has more often read manpages, howtos, whitepapers, comments in source code etc.
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to change the GRUB command line to graphical interface?

Hi, I am i new Unix linux user. I've installed the linux 9 and i uninstall it. the first time i install the linux, the GRUB show the graphical interface. But after i reinstall it again, the GRUB change to command line. I can't boot my comp now. What should I do? And i don't know how to deal with... (1 Reply)
Discussion started by: lee_chongeu
1 Replies

2. Linux

How change GRUB command line to graphical interface?

Hi, I am i new Unix linux user. I've installed the linux 9 and i uninstall it. the first time i install the linux, the GRUB show the graphical interface. But after i reinstall it again, the GRUB change to command line. I can't boot my comp now. What should I do? And i don't know how to deal with... (4 Replies)
Discussion started by: lee_chongeu
4 Replies

3. SCO

sco GUI interface

Why can I not login to the SCO GUI interface login screen? (1 Reply)
Discussion started by: qphillips
1 Replies

4. UNIX for Advanced & Expert Users

Developing a new command line interface

Hi, Is there any good/easy tool or library which assists in developing a command line interface for an application. The CLI should be able to provide custom commands, allow programming/scripting as well. For the latter case it could wrap a shell command and send it to BASH for processing. (2 Replies)
Discussion started by: redirect
2 Replies

5. Solaris

Command line Interface or GUI Interface not shown on solaris

Dear all, I am a newbie in solaris and I need your advice. I have a Solaris version 5.9 installed on Sunfire V240. I am able to ssh the machine from putty remotely. My problem is that I cannot see the display from KVM switch I have connected to it. I need also to be able to see the GUI... (2 Replies)
Discussion started by: mbouster
2 Replies

6. SCO

Change SCO - GUI or Desktop interface to DOS based interface

Hi all I have installed a demo version of SCO OpenServer 5.0.2, I finally found it is Desktop Interface, I would like to know how to change its interface to dos based interface? If you have any ideas, please tell me then. Thank you (2 Replies)
Discussion started by: TinhNhi
2 Replies

7. Solaris

Gui to command line

Hi, OS :- SUN I am asked to invoke table menu via command line , after that i need to select option in the table menu like REPORT, STATUS ... After login in to server , I am entering “yct”. It brings me a table with lot of option , I need to scroll down and then select “Report “ which... (3 Replies)
Discussion started by: bharats08
3 Replies

8. Solaris

How to start gui from Solaris command line?

Hi. I'm a Solaris newbie. I'm using Solaris SunOS Version 11.4.0.15.0 through Oracle VM VirtualBox Manager on Windows. When I start the VM, I get to a command line I can login to. I've tried using: /usr/dt/bin/dtconfig -e However, I receive error "No such file or directory". The... (3 Replies)
Discussion started by: SRD
3 Replies
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)
All times are GMT -4. The time now is 01:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy