Use error_msg instead of fprintf(stderr
authorGlenn L McGrath <bug1@ihug.co.nz>
Thu, 28 Nov 2002 09:40:36 +0000 (09:40 -0000)
committerGlenn L McGrath <bug1@ihug.co.nz>
Thu, 28 Nov 2002 09:40:36 +0000 (09:40 -0000)
init/init.c

index 79ab78fc240f23d09e4d1395d7e1518744d5d753..bb1f383b3113173bab56bd3d443b9eaeb36a6811 100644 (file)
@@ -230,7 +230,7 @@ static void message(int device, char *fmt, ...)
        if (log_fd < 0) {
                if ((log_fd = device_open(log, O_RDWR | O_NDELAY)) < 0) {
                        log_fd = -2;
-                       fprintf(stderr, "Bummer, can't write to log on %s!\n", log);
+                       error_msg("Bummer, can't write to log on %s!", log);
                        device = CONSOLE;
                } else {
                        fcntl(log_fd, F_SETFD, FD_CLOEXEC);
@@ -253,7 +253,7 @@ static void message(int device, char *fmt, ...)
                        va_end(arguments);
                        close(fd);
                } else {
-                       fprintf(stderr, "Bummer, can't print: ");
+                       error_msg("Bummer, can't print: ");
                        va_start(arguments, fmt);
                        vfprintf(stderr, fmt, arguments);
                        va_end(arguments);