syslogd & return code

[Jason Schoon]

Seems reasonable to me.  Although most things probably don't care about the
return code of programs (hence why this hasn't cropped up as a problem thus
far), EXIT_SUCCESS would be more accurate, especially across multiple
platforms I would think.



On 12/27/05, greg <ustrel at free.fr> wrote:
>
> hi all.
>
> I'm trying to make a custom distribution to be used for a network
> oriented embedded system.
> It is based upon an initng/busybox/udev combination.
>
> When shutting down, initng complains about syslogd returning 1
> A quick look at the code (busybox-1.1.0-pre1) , shows :
>
> #################################################
> static void quit_signal(int sig)
> {
>         logMessage(LOG_SYSLOG | LOG_INFO, "System log daemon exiting.");
>         unlink(lfile);
> #ifdef CONFIG_FEATURE_IPC_SYSLOG
>         ipcsyslog_cleanup();
> #endif
>
>         exit(TRUE);
> }
> #################################################
>
> This signal handler is connected to SIGINT, SIGTERM & SIGQUIT
>
> Should not we exit with EXIT_SUCCESS code instead of TRUE ??
>
> Regards,
> gregor
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/cgi-bin/mailman/listinfo/busybox
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.busybox.net/pipermail/busybox/attachments/20051227/0b400562/attachment-0001.htm