From owner-freebsd-bugs  Sat Oct  5 03:29:22 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id DAA07196
          for bugs-outgoing; Sat, 5 Oct 1996 03:29:22 -0700 (PDT)
Received: from magigimmix.xs4all.nl (magigimmix.xs4all.nl [194.109.6.25])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA07189
          for <freebsd-bugs@freefall.freebsd.org>; Sat, 5 Oct 1996 03:29:16 -0700 (PDT)
Received: from asterix.xs4all.nl (asterix.xs4all.nl [194.109.6.11]) by magigimmix.xs4all.nl (8.7.5/XS4ALL) with ESMTP id MAA03011; Sat, 5 Oct 1996 12:29:13 +0200 (MET DST)
Received: from tangram.xs4all.nl (uucp@localhost) by asterix.xs4all.nl (8.7.5/8.7.2) with UUCP id MAA08454; Sat, 5 Oct 1996 12:15:25 +0200 (MET DST)
Received: (from jh@localhost) by tangram.xs4all.nl (8.6.12/8.6.12) id VAA00503; Fri, 4 Oct 1996 21:23:24 +0200
Date: Fri, 4 Oct 1996 21:23:24 +0200
Message-Id: <199610041923.VAA00503@tangram.xs4all.nl>
From: Jan-Hein Buhrman <jh@tangram.xs4all.nl>
To: j@uriah.heep.sax.de
CC: freebsd-bugs@freefall.freebsd.org
In-reply-to: <199610031340.GAA27052@freefall.freebsd.org>
	(j@uriah.heep.sax.de)
Subject: Re: kern/1711: kernel logging of signaled processes should be optional
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>>>>> "J\"org" == J Wunsch <j@uriah.heep.sax.de> writes:

>  As nsayer@kfu.com wrote:
 
>> kernel logging of signaled processes ("pid 99, uid 0: exited on
>> signal 11 (core dumped)") _really_ should have an option to
>> disable. Really now. If you can comment the source to indicate
>> that some found it annoying (it certainly bugs the hell out of
>> me), you can put an #ifndef in to allow folks to have their
>> choice.
 
>  I would prefer a sysctl variable for this.

I really liked what rld (the dynamic linker/loader) did on SGI IRIS
systems (perhaps FreeBSD does the same thing, didn't check it :-):

If some shared libraries couldn't be found, an error message was just
shown on your terminal (via syslog), but if the process didn't have a
controlling tty, it was sent to /var/{log,adm}/{messages,SYSLOG} (also
via syslog).

I realize this example demonstrates just a feature of syslog, used in
a userland-proces.

However, to get a `similar' behaviour of this regarding `exit on
signals', the kernel could check if the concerning process is having a
controlling tty, and if not: generate a log-message like it does now,
and when the process _has_ a controlling tty: leaving the
responsibility (of e.g. reporting something) to whatever parent
process is managing it (like a shell does, for instance, saying
`Segmentation fault (core dumped)').

Regards,
-jh