System.Systemd.Daemon.Fd

Reexports

Definitions

notifyWithFd : Bool -> String -> Fd -> IO (Maybe ())

  Same as `System.Systemd.Daemon.notify`, but send along an `Fd`.
  Note that the caller must set the message, i. e. send @FDSTORE=1@
  to actually store the file descriptor. In most cases it is probably best
  to use 'storeFd' or the notify-functions from `System.Systemd.Daemon`.
  Equivalent to standard `System.Systemd.Daemon.notifyWithFD`.

Visibility: export

storeFd : Fd -> IO (Maybe ())

  Notify Systemd to store a file descriptor for us. This together
  with `getActivatedSockets` allows for zero downtime
  restarts and socket activation.
  Equivalent to standard `System.Systemd.Daemon.storeFd`.

Visibility: export

storeFdWithName : Fd -> String -> IO (Maybe ())

  Like `storeFd`, but associate the file descriptor with a name.
  Best used along with `getActivatedSocketsWithNames`.
  Equivalent to standard `System.Systemd.Daemon.storeFdWithName`.

Visibility: export

getActivatedSockets : IO (Maybe (List Fd))

  Return Just a list of file descriptors if the current process
  has been activated with one or more socket by systemd, Nothing
  otherwise.
  The file descriptors are in the same order as the sockets in the
  associated .socket file.
  The sockets will have their family, type,
  and status set according to the .socket file.
  Equivalent to standard `System.Systemd.Daemon.getActivatedSockets`.

Visibility: export

getActivatedSocketsWithNames : IO (Maybe (List (Fd, String)))

  Like 'getActivatedSockets', but also return the associated names.
  If a file descriptor has no associated name, it will be a generic
  one set by systemd.
  Equivalent to standard `System.Systemd.Daemon.getActivatedSocketsWithNames`.

Visibility: export