Sponsored Content
The Lounge What is on Your Mind? PubNub Live Chat Beta Testing Post 303034247 by samthewildone on Monday 22nd of April 2019 07:55:35 PM
Old 04-22-2019
neo over there pouring his heart and soul into this. Who knows... this might be a goldmine of knowledge decades from now.
This User Gave Thanks to samthewildone For This Post:
 

4 More Discussions You Might Find Interesting

1. Solaris

Live Chat For Solaris?

Does anyone know of any online live chat discussion groups for Solaris? If so, please let me know... Thanks! Rob Sandifer (3 Replies)
Discussion started by: RobSand
3 Replies

2. What is on Your Mind?

A Quick Video Overview of PubNub Live Chat @UNIX.com (version 0.7614)

A number of people have asked me to make some videos, so I just got my first condenser microphone and so I can make some amateurish screen casts. I will try to do better in the future. A quick overview of PubNub Live Chat @unix.com The video is best is you set the Quality to HD 1080. The... (0 Replies)
Discussion started by: Neo
0 Replies

3. What is on Your Mind?

Live Chat (Alpha) in UserCP SF 0.7517

Interesting.... I am still working on the kinks for Live Chat here at unix.com using a publish-subscribe API from PubNub. Two days ago while working on it, a new user joined the live chat and asked about how to post a new thread in the forum. Then today, one of the members of the PubNub team... (23 Replies)
Discussion started by: Neo
23 Replies

4. What is on Your Mind?

Update: UserCP Screeching Frog 0.7641 - Changed Live Chat to Live Updates

Update: UserCP Screeching Frog 0.7641 - Changed Live Chat to Live Updates In this version of the UserCP, I have changed "Live Chat" to "Live Updates" by disabling the ability to post in the "live chat" area and changed the name to "Live Updates" The reason for this change is that experienced... (6 Replies)
Discussion started by: Neo
6 Replies
heart(3erl)						     Erlang Module Definition						       heart(3erl)

NAME
heart - Heartbeat Monitoring of an Erlang Runtime System DESCRIPTION
This modules contains the interface to the heart process. heart sends periodic heartbeats to an external port program, which is also named heart . The purpose of the heart port program is to check that the Erlang runtime system it is supervising is still running. If the port program has not received any heartbeats within HEART_BEAT_TIMEOUT seconds (default is 60 seconds), the system can be rebooted. Also, if the system is equipped with a hardware watchdog timer and is running Solaris, the watchdog can be used to supervise the entire system. An Erlang runtime system to be monitored by a heart program, should be started with the command line flag -heart (see also erl(1) . The heart process is then started automatically: % erl -heart ... If the system should be rebooted because of missing heart-beats, or a terminated Erlang runtime system, the environment variable HEART_COM- MAND has to be set before the system is started. If this variable is not set, a warning text will be printed but the system will not reboot. However, if the hardware watchdog is used, it will trigger a reboot HEART_BEAT_BOOT_DELAY seconds later nevertheless (default is 60). To reboot on the WINDOWS platform HEART_COMMAND can be set to heart -shutdown (included in the Erlang delivery) or of course to any other suitable program which can activate a reboot. The hardware watchdog will not be started under Solaris if the environment variable HW_WD_DISABLE is set. The HEART_BEAT_TIMEOUT and HEART_BEAT_BOOT_DELAY environment variables can be used to configure the heart timeouts, they can be set in the operating system shell before Erlang is started or be specified at the command line: % erl -heart -env HEART_BEAT_TIMEOUT 30 ... The value (in seconds) must be in the range 10 < X <= 65535. It should be noted that if the system clock is adjusted with more than HEART_BEAT_TIMEOUT seconds, heart will timeout and try to reboot the system. This can happen, for example, if the system clock is adjusted automatically by use of NTP (Network Time Protocol). In the following descriptions, all function fails with reason badarg if heart is not started. EXPORTS
set_cmd(Cmd) -> ok | {error, {bad_cmd, Cmd}} Types Cmd = string() Sets a temporary reboot command. This command is used if a HEART_COMMAND other than the one specified with the environment variable should be used in order to reboot the system. The new Erlang runtime system will (if it misbehaves) use the environment variable HEART_COMMAND to reboot. Limitations: The length of the Cmd command string must be less than 2047 characters. clear_cmd() -> ok Clears the temporary boot command. If the system terminates, the normal HEART_COMMAND is used to reboot. get_cmd() -> {ok, Cmd} Types Cmd = string() Get the temporary reboot command. If the command is cleared, the empty string will be returned. Ericsson AB kernel 2.14.3 heart(3erl)
All times are GMT -4. The time now is 01:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy