Process dumps core, when started by SMF - fine when manually started

Question

Hi.
h2. Explanation
I compiled [Nagios 3.2.0|http://www.nagios.org/] manually, and created a SMF manifest and method file, based on the [OpenCSW supplied files for Nagios|http://www.opencsw.org/packages/nagios]. The method file is based on [what the Nagios guys supply|http://pastebin.ca/1577792] , but [changed a little|http://pastebin.ca/diff.php?id1=1577792&id2=1577793] .
When I enable the "application/nagios" service, it right away goes into maintenance state. In the /var/svc/log/application-nagios:default.log log file, there's consequently then this:
+ exit 0
[ Sep 24 13:17:10 Method "start" exited with status 0 ]
[ Sep 24 13:17:11 Stopping because process dumped core. ]
[ Sep 24 13:17:11 Executing stop method ("/opt/local/nagios-3.2.0/method/nagios stop") ]
+ test -r /lib/svc/share/smf_include.sh
[...]It died, because of "*Stopping because process dumped core.*"
If you have a look at the method file, you'll find that I dump the environment with env to a file. When I login as root and set the environment variables to exactly those values and remove any other additional variables, I can run the method / init script just fine; the nagios process doesn't core dump.
h2. Question
Why does the process dump core, when it's run by SMF?
Additional questoin:Where's the core dump? I did a "find / -name core" and found nothing. I also changed coreadm:
--($ ~)-- LC_ALL=C coreadm
     global core file pattern: /var/core/core.%f.%pAfter a reboot, there's nothing in /var/core (the directory exists).
I'm on Solaris 10 5/09 Sparc.
h2. Files
*[svccfg export nagios|http://pastebin.ca/1577787]*
*[Method file /opt/local/nagios-3.2.0/method/nagios|http://pastebin.ca/1577793]*

Answer 1

There's no such directory as "/var/crash":
--($ ~)-- ls -lad /var/c*
drwxr-xr-x    4 root     sys             4 Sep 21 14:03 /var/cache
drwxr-xr-x    2 root     sys             7 Sep 21 13:32 /var/cc-ccr
drwxr-xr-x    2 root     root            2 Sep 24 13:14 /var/core
drwxr-xr-x    2 root     sys             3 Sep 21 14:03 /var/cronGranted, since when I posted that question and now, I booted the NGZ numerous times. But in a default installation of Solaris 10, that directory isn't removed during shutdown/boot, if it exist. At least it exists on my other servers, even if it is empty (eg. like that, on a different server:
--($ ~)-- ls -laR /var/crash/
/var/crash/:
total 3
drwxr-xr-x    3 root     root          512 Mai 19  2006 .
drwxr-xr-x   56 root     sys          1024 Dez  7  2008 ..
drwxrwx---    2 root     adm           512 Sep 22  2008 winds06
/var/crash/winds06:
total 2
drwxrwx---    2 root     adm           512 Sep 22  2008 .
drwxr-xr-x    3 root     root          512 Mai 19  2006 ..So, I'd say that the coredump has never been stored in /var/crash.
Anyway - isn't /var/crash just used for crashdumps, when the whole machine goes down? According to [man filesystem(5)|http://docs.sun.com/app/docs/doc/816-5175/filesystem-5?a=view] , it is → "+Default depository for kernel crash dumps.+"
If coredumps aren't in /var/crash, aren't named "core*" and aren't stored in the directory specified by coreadm, where are they?
Converse: If no coredump is created, why does Solaris "speak" about a coredump being created?