Re: getting program.core, where and how?
Adam Vande More schrieb am 18.11.2009 16:52 (localtime): On Wed, Nov 18, 2009 at 9:34 AM, Harald Schmalzbauer < h.schmalzba...@omnilan.de> wrote: ... How can I find out what the working directory of the binary is? I guess the problem is missing write permissions there. Thanks, -Harry procstat -f Ahh :) Thanks a lot! -Harry signature.asc Description: OpenPGP digital signature
Re: getting program.core, where and how?
Matthias Apitz schrieb am 18.11.2009 16:59 (localtime): El día Wednesday, November 18, 2009 a las 04:34:18PM +0100, Harald Schmalzbauer escribió: ... How can I find out what the working directory of the binary is? I guess the problem is missing write permissions there. Core will be written to the working directory and not to the directory where the binary comes from. With ulimit(1) you can set the core file size, even to zero, and you can ask for the actual value. Thanks for the answer, that's what I assumend ;) But how can i find out what the working directory is? Thanks, -Harry signature.asc Description: OpenPGP digital signature
Re: getting program.core, where and how?
El día Wednesday, November 18, 2009 a las 04:34:18PM +0100, Harald Schmalzbauer escribió: > Hello, > > I have a daemon (compiled with -g) which is dying frequently, but I > can't get a core dump. > The daemon drops privileges and runs as restricted user after startup. > I gave the restricted user write permission to the directory where the > binary lives, but that hasn't helped. > The size should be really small, so I think ulimit is not the problem. > How can I find out what the working directory of the binary is? I guess > the problem is missing write permissions there. Core will be written to the working directory and not to the directory where the binary comes from. With ulimit(1) you can set the core file size, even to zero, and you can ask for the actual value. HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
getting program.core, where and how?
> How can I find out what the working directory of the binary is? I > guess the problem is missing write permissions there. find -name See "man find" for details; look particularly at the 'x' option. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: getting program.core, where and how?
On Wed, Nov 18, 2009 at 9:34 AM, Harald Schmalzbauer < h.schmalzba...@omnilan.de> wrote: > Hello, > > I have a daemon (compiled with -g) which is dying frequently, but I can't > get a core dump. > The daemon drops privileges and runs as restricted user after startup. > I gave the restricted user write permission to the directory where the > binary lives, but that hasn't helped. > The size should be really small, so I think ulimit is not the problem. > How can I find out what the working directory of the binary is? I guess the > problem is missing write permissions there. > > Thanks, > > -Harry > > procstat -f -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
getting program.core, where and how?
Hello, I have a daemon (compiled with -g) which is dying frequently, but I can't get a core dump. The daemon drops privileges and runs as restricted user after startup. I gave the restricted user write permission to the directory where the binary lives, but that hasn't helped. The size should be really small, so I think ulimit is not the problem. How can I find out what the working directory of the binary is? I guess the problem is missing write permissions there. Thanks, -Harry signature.asc Description: OpenPGP digital signature