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
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
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
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
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
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
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
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
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
LEARN ABOUT DEBIAN
sam_overview
SAM_OVERVIEW(8) Corosync Cluster Engine Programmer's Manual SAM_OVERVIEW(8)
NAME
sam_overview - Overview of the Simple Availability Manager
OVERVIEW
The SAM library provide a tool to check the health of an application. The main purpose of SAM is to restart a local process when it fails
to respond to a healthcheck request in a configured time interval.
During sam_initialize(3), a duplicate copy of the process is created using the fork(3) system call. This duplicate process copy contains
the logic for executing the SAM server. The SAM server is responsible for requesting healthchecks from the active process, and controlling
the lifecycle of the active process when it fails. If the active process fails to respond to the healthcheck request sent by the SAM
server, it will be sent a user configurable signal (default SIGTERM) to request shutdown of the application. After a configured time
interval, the process will be forcibly killed by being sent a SIGKILL signal. Once the active process terminates, the SAM server will cre-
ate a new active process.
The Simple Availability Manager is meant to be used in conjunction with the cpg service. Used together, it is possible to restart a cpg
process that fails healthchecking during operation.
The main features of SAM include:
o A configurable recovery policy.
o A configurable time interval for health check operations.
o A notification via signal before recovery action is taken.
o A mechanism to indicate to the application the number of times an active process has been created by the SAM server.
o Both application driven health checking and event driven health checking.
Initializing SAM
The SAM library is initialized by sam_initialize(3). sam_initalize(3) may only be called once per process. Calling it more then once has
undefined results and is not recommended or tested.
Setting warning callback
User configurable signal (default SIGTERM) is sent to the application when a recovery action is planned. The application can use the sig-
nal(3) system call to monitor for this signal.
There are no special constraints on what SAM apis may be called in a warning callback. After time_interval expires, a SIGKILL signal is
sent to the active process to force its termination.
Registering the active process
The active process is registered with SAM by calling sam_register(3). This function should only be called one time in a process. After a
recovery action is taken, the new active process will begin execution at the next line of code in a user process after sam_register(3).
Enabling event driven healthchecking
Two types of healthchecking are available to the user. The first model is one where the user application healthchecks during its normal
operation. It is never requested to healtcheck, and if the active process doesn't respond within the time interval, the process will be
restarted.
A more useful mechanism for healthchecking is event driven healthchecking. Because this model is directed by the SAM server, It isn't nec-
essary to guess or add timers to the active process to signal a healthcheck operation is successful. To use event driven healthchecking,
the sam_hc_callback_register(3) function should be executed.
BUGS
SEE ALSO
sam_initialize(3), sam_finalize(3), sam_start(3), sam_stop(3), sam_register(3), sam_warn_signal_set(3), sam_hc_send(3), sam_hc_call-
back_register(3)
corosync Man Page 12/01/2009 SAM_OVERVIEW(8)