Giuseppe/Simon: I was not in my office yesterday, so I haven't yet tried the repaired "gdb-wrapper.sh" script.
Looking at the log files, there were 2 segfaults: one was from a number different from the one that has been causing all of the segfaults to date, and the other occurred on the first page, before the number was logged. I did write a script to watch the process tree, and re-start faxgetty after it segfaults. Here it is: #!/bin/bash # monfaxgetty.sh - restart faxgetty daemon after segfault TGT=" faxgetty$" while true; do sleep 60 res=$(ps -A | grep "$TGT") if [ "$res" ]; then continue fi echo $(date) "-- faxgetty daemon not found. Restarting." /usr/local/sbin/faxgetty -D ttyS0 done This script is invoked by typing: nohup /var/spool/hylafax/bin/monfaxgetty.sh >> /var/log/monfaxgetty 2>&1 <&- & The redirection shenanigans at the end of the line redirects stderror to stdout (2>&1), and closes stdin (<&-) (you can also use 0<&-). Any time the daemon has to restart faxgetty, it logs the date and time to "/var/log/monfaxgetty". The script runs as a daemon, checking for faxgetty once a minute. The fact that my receptionist didn't plug the old fax machine back in yesterday after 2 segfaults indicates that it works as planned. If anyone reading this wants to use the script, pay very close attention to the spaces in the "res=" command. Bash is very fussy about spaces, and it took me several tries to get it right. Also, the definition of "TGT" is important: there is a single space, then "faxgetty$". I'll see if I can get the debugger running, and send the dumps from any further segfaults. Mark -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/600219 Title: faxgetty segfault To manage notifications about this bug go to: https://bugs.launchpad.net/hylafax/+bug/600219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
