Future New Underground Membership Criteria Post: 303029202

Sponsored Content

The Lounge What is on Your Mind? Future New Underground Membership Criteria Post 303029202 by Neo on Wednesday 23rd of January 2019 06:07:23 AM

01-23-2019

Administrator

Quote:

Originally Posted by bakunin

.... Perderabo, for that matter, always had "UNIX daemon" before he would quit as admin and become "Administrator Emeritus".

bakunin

Hey Wolf,

I am not sure that Perderabo actually quit. He was having serious health problems back in the old days before he became "Administrator Emeritus" and he was rarely on the site until about three years ago; when he was active for a short time. Perderabo and I spoke a number of times years ago, and he was really worried about his health and was really sick.

Recently, I send him and email (again) to check on him, and did not get a reply. I worry that the worst may have happened to him. I surely hope not and will try to contact him again soon.

Neo

View Public Profile for Neo

Visit Neo's homepage!

Find all posts by Neo

3 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

Membership

what is the meaning of the types of membership and when am i a full member:confused: :confused: :confused:

2. Solaris

Group membership limit

On Solaris, a user is limited to being a member of a maximum of 16 groups. Could someone tell me where this limit comes from, i.e. is it NIS, or Solaris, or NFS that is imposing this limit? What is the work-around to remove this limitation?

3. Post Here to Contact Site Administrators and Moderators

monthly membership??

Hi, Do we have monthly membership (VIP) in our forum? if not, do we have any plans for it? Regards,

LEARN ABOUT DEBIAN

sam_start

SAM_START(3)					    Corosync Cluster Engine Programmer's Manual 				      SAM_START(3)

NAME

       sam_start - Start health checking

SYNOPSIS

       #include <corosync/sam.h>

       cs_error_t sam_start (void);

DESCRIPTION

       The  sam_start  function  is  used  to start health checking of application.  After calling this function, the active process needs to send
       healthchecks within the registered time interval by calling sam_hc_send(3).  If	event  driven  healthchecking  is  configured  by  calling
       sam_register(3), an internal thread will be created and send health check confirmations four times per time_interval.

       Application must be registered by calling sam_register(3) before this function can be called.

       An application can always stop health checking by calling the sam_stop(3) function.

RETURN VALUE

       This call return CS_OK value if successful, otherwise and error is returned.

ERRORS

       CS_ERR_BAD_HANDLE
	      component was not registered by calling sam_register(3) function.

SEE ALSO

       sam_hc_send(3), sam_stop(3), sam_register(3), sam_hc_callback_register(3)

corosync Man Page						    12/01/2009							      SAM_START(3)