PR:25

the standard JS error reporting mechanism. Not recommended for most
script-level error logging.

socket instead of the broken sleep(1) on input previously used.

This allows irc.js to run with MUCH lower CPU utilization.

aren't submitted etc.

Apparently, js/36 isn't really a bug, a script MUST check the online state
itself.

PR:36->closed

(The textmode() call was causing the screen to be cleared on *nix which
resulted in background disapearing when it shouldn't have)

use the exposed array (since it's NOT actually changed!)

Simplifies screen updates greatly.

list.

PR:25->closed

valid).

1) Properly initialize variables.
2) Just because a directory is empty doesn't mean it doesn't exist.

reason and don't separately append to the audit trail.
Remove trailing newlines from state and responsible before testing against
new value.
Do a send_followup() if neither responsible nor state is being changed.

PR:10

file/core.

(Test PR:10)

gnats_cvs.js $USER gnatsuser gnatspw

Where $USER is the CVS user who comitted the change
gnatsuser is the GNATS userID (ie: cvs)
gnatspw is the GNATS password.

* the 'in transit' flag and how to ignore or fix the problem
* the 'usual' DNS server IP address
* detecting outbound SMTP filtering/blocking
* avoiding a relay "loop"
* detecting and correcting SMTP relay authentication problems

object (doh!)

core files are created and how their named on Linux systems).