sd_notify_ex v0.1.1 SdNotifyEx View Source

sd_notify for Elixir

see sd_notify(3), systemd.service(5)

Link to this section Summary

Functions

Returns a specification to start this module under a supervisor

Invoked when the server is started. start_link/3 or start/3 will block until it returns

send sd_notify by reserved socket

send sd_notify by new socket every time

Link to this section Functions

Link to this function buserror(err) View Source
buserror(String.Chars.t()) :: send_return_t()

Returns a specification to start this module under a supervisor.

See Supervisor.

Link to this function errno(err) View Source
errno(String.Chars.t()) :: send_return_t()
Link to this function extend_timeout_usec(usec) View Source
extend_timeout_usec(String.Chars.t()) :: send_return_t()
Link to this function fdname(name) View Source
fdname(String.Chars.t()) :: send_return_t()
Link to this function fdstore() View Source
fdstore() :: send_return_t()
Link to this function fdstoreremove() View Source
fdstoreremove() :: send_return_t()
Link to this function init(_) View Source
init(any()) :: {:ok, SdNotifyEx.State.t()} | {:stop, term()}

Invoked when the server is started. start_link/3 or start/3 will block until it returns.

args is the argument term (second argument) passed to start_link/3.

Returning {:ok, state} will cause start_link/3 to return {:ok, pid} and the process to enter its loop.

Returning {:ok, state, timeout} is similar to {:ok, state} except handle_info(:timeout, state) will be called after timeout milliseconds if no messages are received within the timeout.

Returning {:ok, state, :hibernate} is similar to {:ok, state} except the process is hibernated before entering the loop. See c:handle_call/3 for more information on hibernation.

Returning :ignore will cause start_link/3 to return :ignore and the process will exit normally without entering the loop or calling c:terminate/2. If used when part of a supervision tree the parent supervisor will not fail to start nor immediately try to restart the GenServer. The remainder of the supervision tree will be (re)started and so the GenServer should not be required by other processes. It can be started later with Supervisor.restart_child/2 as the child specification is saved in the parent supervisor. The main use cases for this are:

  • The GenServer is disabled by configuration but might be enabled later.
  • An error occurred and it will be handled by a different mechanism than the Supervisor. Likely this approach involves calling Supervisor.restart_child/2 after a delay to attempt a restart.

Returning {:stop, reason} will cause start_link/3 to return {:error, reason} and the process to exit with reason reason without entering the loop or calling c:terminate/2.

Callback implementation for GenServer.init/1.

Link to this function mainpid(num) View Source
mainpid(String.Chars.t()) :: send_return_t()
Link to this function ready() View Source
ready() :: send_return_t()
Link to this function reloading() View Source
reloading() :: send_return_t()
Link to this function send(data) View Source
send(iodata()) :: send_return_t()

send sd_notify by reserved socket

Link to this function send_by_new_socket(data) View Source
send_by_new_socket(iodata()) :: :ok | {:error, term()}

send sd_notify by new socket every time

Link to this function start_link(_ \\ []) View Source
start_link(any()) :: GenServer.on_start()
Link to this function status(str) View Source
status(String.Chars.t()) :: send_return_t()
Link to this function stopping() View Source
stopping() :: send_return_t()
Link to this function watchdog() View Source
watchdog() :: send_return_t()
Link to this function watchdog_usec(usec) View Source
watchdog_usec(String.Chars.t()) :: send_return_t()