Bit of a long shot...
I'm executing a long-running process that takes several hours. The process is the re-indexing of the CDDB database's fuzzy matching file. The process keeps quitting after a while, although the length of time is variable:
# /usr/local/bin/cddbd -fdv
Generating the fuzzy matching hash file.
Scanning /home/freedb/cddb/soundtrack.
Scanning /home/freedb/cddb/lost+found.
Scanning /home/freedb/cddb/jazz.
Scanning /home/freedb/cddb/data.
Scanning /home/freedb/cddb/rock.
Scanning /home/freedb/cddb/reggae.
Scanning /home/freedb/cddb/newage.
Scanning /home/freedb/cddb/folk.
Scanning /home/freedb/cddb/misc.
Received signal 28.
Quitting, status 1.
The output is from the CDDB process. I had never seen signal 28 before, and after some research there are two possibilities: a "window size change" (although that appears to be BSD or Sun Unix only) or "Virtual alarm clock" (BSD only). I'm running this in Ubuntu...
So I wondered, ignoring the fact that I shouldn't be getting these on Linux anyway, could screen be issuing "window size change" signals?
As I said, a bit of a long shot!