Description of problem:
If job is continued via command condor_continue, they receive twice signal SIGCONT.
When is it (suspended and) continued because of expression (SUSPEND) CONTINUE, they receive SIGCONT only once.


Version-Release number of selected component (if applicable):
condor-classads-7.6.5-0.5
condor-7.6.5-0.5


How reproducible:
100%


Steps to Reproduce:
1. Default configuration of condor (expression SUSPEND and CONTINUE set to FALSE).
2. Submit job (execution script is from bug 635012, comment 18):
  # cat /tmp/test.job 
    universe = vanilla
    cmd = /tmp/bz635012.py
    output = /tmp/job_$(cluster).$(process).output
    error = /tmp/job_$(cluster).$(process).error
    Log = /tmp/job_$(cluster).$(process).log
    queue 1

  # runuser -s /bin/bash -l condor -c "condor_submit /tmp/test.job"

3. When job is running, suspend and continue him via condor_suspend and condor_continue command.

4. Look to output file:
  # cat /tmp/job_1.0.output
    [11:05:26]+0.8911 - Run '/tmp/bz635012.py' with pid: 5778
    [11:05:26]+0.8911 - 0
    [11:05:27]+0.9203 - 1
    . . .
    [11:05:40]+0.9533 - 14
    [11:05:41]+0.9533 - 15
    [11:06:02]+0.4006 - caught signal - sig_num: 18 ('SIGCONT')
    [11:06:02]+0.4008 - 16
    [11:06:02]+0.4738 - caught signal - sig_num: 18 ('SIGCONT')
    [11:06:02]+0.4740 - 17
    [11:06:03]+0.4788 - 18
    . . .

  
Additional info:
Found on verification of bug 635012.