/[gnats]/gnats/doc/gnats-faq.texi
ViewVC logotype

Diff of /gnats/doc/gnats-faq.texi

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.9 by has, Sun Jul 21 21:51:59 2002 UTC revision 1.10 by has, Wed Oct 2 22:45:22 2002 UTC
# Line 111  input.  Please report any errors and sug Line 111  input.  Please report any errors and sug
111    
112  @menu  @menu
113  * What is GNATS::               A very short overview  * What is GNATS::               A very short overview
114    * How to pronounce it::        
115  * Get it::                      Where to get @sc{gnats}  * Get it::                      Where to get @sc{gnats}
116  * Versions::                    Which versions are available?  * Versions::                    Which versions are available?
117  * Mailing Lists::               E-mail discussion lists  * Mailing Lists::               E-mail discussion lists
# Line 181  For users sending their PRs via e-mail, Line 182  For users sending their PRs via e-mail,
182  configured.  configured.
183    
184    
185    @node     How to pronounce it
186    @comment  node-name,     next,   previous,  up
187    @section  How is "@sc{gnats}" pronounced?
188    
189    Q: So, How can I pronounce "@sc{gnats}?"  Should I pronounce "G"?
190    
191    It has been reported that the original developers pronounced the "G".
192    (This is unlike the little insect called "gnat" where the "G" is not
193    pronounced.)
194    
195    
196  @node     Get it  @node     Get it
197  @comment  node-name,  next,     previous,      up  @comment  node-name,  next,     previous,      up
198  @section Where do I get it?  @section Where do I get it?
# Line 368  please check also @ref{Configuration}. Line 380  please check also @ref{Configuration}.
380  * Add a database::              How to create a new database  * Add a database::              How to create a new database
381  * Renaming a Category::          * Renaming a Category::        
382  * Changing Fields::              * Changing Fields::            
383    * Append-only Audit-Trail::    
384  @end menu  @end menu
385    
386  @node Add a database  @node Add a database
# Line 464  bugs.exampl Line 477  bugs.exampl
477  GNATS_ADMIN="gnats-admin@@bugs.example.com"  GNATS_ADMIN="gnats-admin@@bugs.example.com"
478  @end smallexample  @end smallexample
479    
480    If your @sc{gnats} sits behind a firewall and needs to exchange mails
481    with the outside world, see also @ref{Outgoing mail bounces}.
482    
483  @end enumerate  @end enumerate
484    
485  @noindent  @noindent
# Line 521  option has changed its meaning: it does Line 537  option has changed its meaning: it does
537  database, but its name.  (In case you prefer the long form of the  database, but its name.  (In case you prefer the long form of the
538  option, it is now @samp{--database} instead of @samp{--directory}.)  option, it is now @samp{--database} instead of @samp{--directory}.)
539    
540    If your @sc{gnats} sits behind a firewall and needs to exchange mails
541    with the outside world, see also @ref{Outgoing mail bounces}.
542    
543  @end enumerate  @end enumerate
544    
545    
# Line 588  The @code{severity} field is checked for Line 607  The @code{severity} field is checked for
607  This is currently not configurable.  This is currently not configurable.
608    
609    
610    @node Append-only Audit-Trail
611    @comment  node-name,  next,  previous,  up
612    @subsection How do make Audit-Trail append-only?
613    
614    Mike Hoolehan wanted a "bugzilla-ish appending audit trail", i.e.,
615    Audit-Trail can not be changed arbitrarily, only appended.
616    
617    He posted the following solution to the @email{help-gnats@@gnu.org}
618    mailing list:
619    
620    First, set the Audit-Trail field to read-only.  Then add this:
621    
622    @example
623    field "Add-To-Audit-Trail" {
624       description "Add a log entry to Audit Trail"
625       multitext { default "\n" }
626       on-change  {
627            add-audit-trail
628            audit-trail-format {
629            format "---- Comments by %s on %s ----\n %s\n\n" #whatever you like
630            fields { "$EditUserEmailAddr" "$CurrentDate" "$NewValue" }
631            }
632        }
633        on-change {
634            set-field "Add-To-Audit-Trail" { "\n" }
635        }
636    }
637    @end example
638    
639    
640  @node Gnatsd  @node Gnatsd
641  @comment  node-name,  next,  previous,  up  @comment  node-name,  next,  previous,  up
642  @section Gnatsd, the @sc{gnats} Daemon  @section Gnatsd, the @sc{gnats} Daemon
# Line 828  the file. Line 877  the file.
877    
878  @menu  @menu
879  * queue-pr not available::        * queue-pr not available::      
880    * Outgoing mail bounces::      
881  @end menu  @end menu
882    
883  @node queue-pr not available,  , E-Mail, E-Mail  @node queue-pr not available, Outgoing mail bounces, E-Mail, E-Mail
884  @comment  node-name,  next,  previous,  up  @comment  node-name,  next,  previous,  up
885  @subsubheading queue-pr not available for sendmail programs  @subsubheading queue-pr not available for sendmail programs
886    
# Line 851  Replace @w{@file{/usr/local/libexec/gnat Line 901  Replace @w{@file{/usr/local/libexec/gnat
901  @file{queue-pr}.  @file{queue-pr}.
902    
903    
904    @node Outgoing mail bounces
905    @comment  node-name,  next,  previous,  up
906    @subsubheading Mail from @sc{gnats} bounces
907    
908    You are getting bounce mails like this:
909    
910    @example
911       ----- Transcript of session follows -----
912    ... while talking to mail.example.com.:
913    >>> MAIL From:<gnats@@mymachine.subdomain.example.com> SIZE=334
914    <<< 501 5.1.8 <gnats@@mymachine.subdomain.example.com>...
915          Domain of sender address gnats@@mymachine.subdomain.example.com does not exist
916    @end example
917    
918    Probably your @sc{gnats} sits behind a firewall, but it needs to
919    exchange mails with the world outside the firewall.  Make sure that
920    @var{GNATS_ADDR} is valid outside.
921    
922    This is what probably happens behind the scenes: On its way to the
923    outside world, the sender address of the mail gets rewritten to
924    something "official" (like @code{Hans-Albert.Schneider@@example.com}, as
925    opposed to @code{me@@mymachine.subdomain.example.com}).  This is
926    especially necessary if the internal hosts are not visible outside.  If
927    your outgoing mail gateway still sees the internal address, it complains
928    with a message like the above (it has probably checked
929    @code{mymachine.subdomain.example.com} with your organization's external
930    DNS server, which does not know @code{mymachine}).
931    
932    To solve this problem, get an "official" address for your @sc{gnats}
933    system, e.g., tool-bugs@@example.com, and use that one for
934    @var{GNATS_ADDR}.
935    
936    
937    
938  @node Miscellaneous  @node Miscellaneous
939  @comment  node-name,  next,  previous,  up  @comment  node-name,  next,  previous,  up

Legend:
Removed from v.1.9  
changed lines
  Added in v.1.10

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26