piping the PID of the watchdog process to cvmfs (queryable with cvmfs_talk)
do not use /proc//exe
optionally ignore x-directory hardlinks failures
Merge branch 'master' into fix_stacktrace
never drop root rights completely (might be needed for watchdog later on) - therefore watchdog is now deactivatable (then root permissions are dropped as before)
monitor tries to re-gain root permissions before attching gdb to the died cvmfs2 process
cosmetics
fork/exec gdb directly from the watchdog without using an intermediate shell script
call default signal handler on dying cvmfs2 process after stack trace was sucessfully retrieved by watchdog
cosmetics
TEST: testing post mortem stacktrace retrieval for both private and automounted cvmfs instances
FIX: disable_watchdog flag ignored with older loaders
FIX: initialize disable_watchdog flag in LoaderExports
Merge pull request #103 from reneme/fix_stacktrace

FIX: Post Mortem Stacktrace Creation



This fixes the issue, that stack traces were not created properly after cvmfs has dropped it's user credentials. When our custom signal handler is invoked it now resets all signal handlers to their default. This allows the watchdog process to trigger core dump creation by killing the cvmfs2 process using the same signal that was initially raised.

Additionally to the fix I added two test cases that verify the proper stacktrace creation both in an automount and a private mount setup.