 |
 |
Hi, I did that both by hacking the startup script and by changing things for xrootd user in The /etc/security/limits.conf file already and still could not get a core file. Will try again tomorrow Doug Sent from my iPad please excuse the typos and creative grammar On Oct 6, 2011, at 22:30, Andrew Hanushevsky <[log in to unmask]> wrote: > Hi Doug, > > You need to set the corelimit to unlimited but that has to be done in the init script. Quite odd. It may be that one of the shared libraries isn't quite right when starting it via service, sigh. > > Andy > > On Thu, 6 Oct 2011, Doug Benjamin wrote: > >> Hi, >> >> When I start xrootd from the /sbin/service xrootd start command (or obviously /etc/init.d/xrootd) >> It starts that then immediately will seg fault. No core file is left though. >> >> If xrootd is started outside of the daemon command (still the xrootd user), it starts up and does >> not core dump right away. >> >> Any ideas how I can capture the core for you. >> >> Doug >> >>