os: Make sure that writing our pid to the lock file actually worked

There's no sense verifying that we can create the lock file and then ignoring the return value from write. Signed-off-by: Keith Packard <keithp@keithp.com> Reviewed-by: Jamey Sharp <jamey@minilop.net> Backport to nx-libs: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

os: Make sure that writing our pid to the lock file actually worked
b5cceb74 · Keith Packard · Mike Gabriel · bad0e8bd · b5cceb74
Commit b5cceb74 authored Jun 29, 2016 by Keith Packard Committed by Mike Gabriel Jul 05, 2016
Show whitespace changes
Inline Side-by-side

Showing with 3 additions and 1 deletion

utils.c nx-X11/programs/Xserver/os/utils.c +3 -1

No files found.
--- a/nx-X11/programs/Xserver/os/utils.c
+++ b/nx-X11/programs/Xserver/os/utils.c
@@ -411,7 +411,9 @@ LockServer(void)
  if (lfd < 0)
    FatalError("Could not create lock file in %s\n", tmp);
  (void) sprintf(pid_str, "%10ld\n", (long)getpid());
-  (void) write(lfd, pid_str, 11);
+  if (write(lfd, pid_str, 11) != 11)
+    FatalError("Could not write pid to lock file in %s\n", tmp);
+
 #ifndef __UNIXOS2__
 #ifndef USE_CHMOD
  (void) fchmod(lfd, 0444);