NOTICE: core_log: setid process, core not dumped
Barry Margolin
barmar at alum.mit.edu
Sat Oct 15 00:39:36 UTC 2005
In article <diodjf$119$1 at sf1.isc.org>,
"Sajed Naseem" <naseems at stjohns.edu> wrote:
> Oct 11 08:30:28 genunix: [ID 603404 kern.notice] NOTICE: core_log:
> named[3406] setid process, core not dumped:
> /var/core/core.named.3406.hostname.1003.27.1129033828
> Oct 14 08:26:47 genunix: [ID 603404 kern.notice] NOTICE: core_log:
> named[8418] setid process, core not dumped:
> /var/core/core.named.8418.hostname.1003.27.1129292807
As a security feature, if named is running setuid, it will not create a
core file when it crashes.
If you want to send the core file to the BIND developers so they can
debug the crash, you should run it without the -u named option.
--
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
More information about the bind-users
mailing list