#+TYP_TODO: MAYBE TODO DONE
* TODO error message becomes a scheduling command

Consider this code:
  
#+begin_src scheme
(use-modules (drmaa v1 low))
(define (test)
  (let ((t (allocate-job-template!)))
    (set-attribute! t (DRMAA 'REMOTE_COMMAND) "/bin/ls")
    (set-attribute! t (DRMAA 'JS_STATE)
                    (DRMAA 'SUBMISSION_STATE_ACTIVE))
    (set-attribute! t (DRMAA 'WD)
                    "/home/rwurmus/")

    ;; This is wrong and leads to an error
    (set-attribute! t (DRMAA 'NATIVE_SPECIFICATION)
                    "-b n -V -q all.q -w n -A rwurmus")
    (run-bulk-jobs t 1)))

(init-session!)
(test)
(exit-session!)
#+end_src

Since there is no =rwurmus= accounting group, the template fails with an error message.  Part of this error message is interpreted as a command:

#+begin_example
scheme@(guile-user)> (test)
WARNING - Accounting to 'rwurmus' was denied, thus your job was assigned into your default department 'akalin
WARNING - Accounting to 'rwurmus' was denied, thus your job was assigned into your default department 'akalin
ice-9/boot-9.scm:1669:16: In procedure raise-exception:
ERROR:
  1. &message: "master got unknown command from JSV: \"'.\" (17)"

Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
scheme@(guile-user) [1]> ,bt
In ice-9/boot-9.scm:
  1669:16  0 (raise-exception _ #:continuable? _)
#+end_example

That’s the trailing “'.” of the error message that somehow slips by and is interpreted as a command.  Is some buffer too small?