udevd: clarify worker exit status

[elogind.git] / udev / sd-daemon.h

diff --git a/udev/sd-daemon.h b/udev/sd-daemon.h
index fdf3cc03548cce17bd94bb5811dd00edccbd761e..4b853a15bec92fa98785fdb6638cfd2d22f67dd9 100644 (file)
--- a/udev/sd-daemon.h
+++ b/udev/sd-daemon.h
@@ -185,7 +185,7 @@ int sd_is_socket_unix(int fd, int type, int listening, const char *path, size_t
      READY=1      Tells systemd that daemon startup is finished (only
                   relevant for services of Type=notify). The passed
                   argument is a boolean "1" or "0". Since there is
      READY=1      Tells systemd that daemon startup is finished (only
                   relevant for services of Type=notify). The passed
                   argument is a boolean "1" or "0". Since there is

-                  little value in signalling non-readiness the only
+                  little value in signaling non-readiness the only

                   value daemons should send is "READY=1".
 
      STATUS=...   Passes a single-line status string back to systemd
                   value daemons should send is "READY=1".
 
      STATUS=...   Passes a single-line status string back to systemd


@@ -206,7 +206,7 @@ int sd_is_socket_unix(int fd, int type, int listening, const char *path, size_t
                   fork off the process itself. Example: "MAINPID=4711"
 
   Daemons can choose to send additional variables. However, it is
                   fork off the process itself. Example: "MAINPID=4711"
 
   Daemons can choose to send additional variables. However, it is

-  recommened to prefix variable names not listed above with X_.
+  recommended to prefix variable names not listed above with X_.

 
   Returns a negative errno-style error code on failure. Returns > 0
   if systemd could be notified, 0 if it couldn't possibly because
 
   Returns a negative errno-style error code on failure. Returns > 0
   if systemd could be notified, 0 if it couldn't possibly because


@@ -252,7 +252,7 @@ int sd_notifyf(int unset_environment, const char *format, ...) _sd_printf_attr_(
   fine. You should NOT protect them with a call to this function. Also
   note that this function checks whether the system, not the user
   session is controlled by systemd. However the functions above work
   fine. You should NOT protect them with a call to this function. Also
   note that this function checks whether the system, not the user
   session is controlled by systemd. However the functions above work

-  for both session and system services.
+  for both user and system services.

 
   See sd_booted(3) for more information.
 */
 
   See sd_booted(3) for more information.
 */