Subject to the copyright assignment described below, your patches should be
sent in {\bf diff -u} format relative to the current contents of the Source
Forge CVS, which is the easiest to understand and integrate.
+Please be sure to use the Bacula indenting standard (see below).
If you have checked out the source with CVS, you can get a diff using:
\begin{verbatim}
code contributions more than a hand full of lines must be in the Public
Domain or have the copyright assigned to Kern Sibbald as in the current
code. Note, prior to November 2004, the code was copyrighted by Kern
-Sibbald and John Walker.
+Sibbald and John Walker. When some sort of Bacula entity is created, this
+this copyright will be transferred to that entity. Hopefully this will
+happen by Q1-2007.
Your name should be clearly indicated as the author of the code, and you
must be extremely careful not to violate any copyrights or use other
you.
If you have any doubts about this, please don't hesitate to ask. The
-objective is to assure the long term servival of the Bacula project. There
-is no consideration of personal gain in this request. Our (John and my)
-track records with Autodesk are easily available; early
-programmers/founders/contributors and later employees had substantial
-shares of the company, and no one founder had a controlling part of the
-company. Even though Microsoft created many millionaires among early
-employees, the politics of Autodesk (during our time at the helm) is in
-stark contrast to Microsoft where the majority of the company is still
-tightly held among a few.
+objective is to assure the long term servival of the Bacula project.
Items not needing a copyright assignment are: most small changes,
-enhancements, or bug fixes of 5-10 lines of code, and documentation.
+enhancements, or bug fixes of 5-10 lines of code.
\subsubsection*{Copyright Assignment}
\index{Copyright Assignment}
\addcontentsline{toc}{subsubsection}{Copyright Assignment}
Since this is not a commercial enterprise, and I prefer to believe in
-everyone's good faith, developers can assign the copyright by explicitly
-acknowledging that they do so in their first submission. This is
-sufficient if the developer is independent, or an employee of a
-not-for-profit organization or a university. Any developer who wants to
-contribute and is employed by a company must get a copyright assignment
-from his employer. This is to avoid misunderstandings between the
-employee, the company, and the Bacula project. A good number of
-companies have already followed this procedure.
-
-\subsubsection*{Corporate Assignment Statement}
-\index{Statement!Corporate Assignment}
-\index{Corporate Assignment Statement}
-\addcontentsline{toc}{subsubsection}{Corporate Assignment Statement}
-
-The following statement must be filled out by the employer, signed, and mailed
+everyone's good faith, previously developers could assign the copyright by
+explicitly acknowledging that they do so in their first submission. This
+was sufficient if the developer is independent, or an employee of a
+not-for-profit organization or a university. However, in an effort to
+ensure that the Bacula code is really clean, beginning in August 2006, all
+previous and future developers with CVS access will be asked to submit a
+copyright assignment.
+
+Any developer who wants to contribute and is employed by a company must get
+a copyright assignment from his employer. This is to avoid
+misunderstandings between the employee, the company, and the Bacula
+project. A good number of companies have already followed this procedure.
+
+\subsubsection*{Personal Copyright Assignment Statement}
+\index{Copyright!Personal Assignment}
+\index{Personal Copyright Assignment Statement}
+\addcontentsline{toc}{subsubsection}{Personal Copyright Assignment Statement}
+
+The following statement must be filled out by each non-employed developer
+(please see below for developer's that are employed), signed, and mailed
to my address (please ask me for my address and I will email it -- I'd prefer
not to include it here).
+\footnotesize
+\begin{verbatim}
+Copyright release and transfer statement.
+ From: <your name>
+
+ To: Kern Sibbald
+ Concerning: Copyright release and transfer
+
+ The undersigned hereby certifies that he/she is independent
+ and wishes to develop
+ code for and contribute code to the Bacula project for an
+ undetermined period of time. The copyright as well as all
+ other rights to and interests in such contributed code are
+ hereby transferred to Kern Sibbald.
+
+ Signed in <City, Country> on <Date>:
+
+ <Name of Person>
+
+\end{verbatim}
+\normalsize
+
+This release/transfer statement must be sent to:
+Kern Sibbald
+Address-to-be-given
+
+If you wish to retain the full rights to use the software you
+have contributed in different projects, this is not a problem. Just
+request a perpetual non-exclusive license before sending in your
+copyright assignment. See the file <bacula-source>/src/lib/tls.c
+for an example of such a license.
+
+
+\subsubsection*{Corporate Copyright Assignment Statement}
+\index{Copyright!Corporate Assignment}
+\index{Corporate Copyright Assignment Statement}
+\addcontentsline{toc}{subsubsection}{Corporate Copyright Assignment Statement}
+
+The following statement must be filled out by the employer, signed, and
+mailed to my address (please ask me for my address and I will email it --
+I'd prefer not to include it here).
+
\footnotesize
\begin{verbatim}
Copyright release and transfer statement.
If you wish to retain the full rights to use the software you
have contributed in different projects, this is not a problem. Just
request a perpetual non-exclusive license before sending in your
-copyright assignment.
+copyright assignment. See the file <bacula-source>/src/lib/tls.c
+for an example of such a license.
+
\subsection*{Basic CVS Usage}
\index{Basic CVS Usage}
unusual feature.
This chapter explains what you should do if one of the three {\bf Bacula}
-daemons (Director, File, Storage) crashes.
+daemons (Director, File, Storage) crashes. When we speak of crashing, we
+mean that the daemon terminates abnormally because of an error. There are
+many cases where Bacula detects errors (such as PIPE errors) and will fail
+a job. These are not considered crashes. In addition, under certain
+conditions, Bacula will detect a fatal in the configuration, such as
+lack of permission to read/write the working directory. In that case,
+Bacula will force itself to crash with a SEGFAULT. However, before
+crashing, Bacula will normally display a message indicating why.
+For more details, please read on.
+
\subsection*{Traceback}
\index[general]{Traceback }
To "manually" test the traceback feature, you simply start {\bf Bacula} then
obtain the {\bf PID} of the main daemon thread (there are multiple threads).
+The output produced here will look different depending on what OS and what
+version of the kernel you are running.
Unfortunately, the output had to be split to fit on this page:
\footnotesize
nothing happened. If this is not the case, you will need to correct the
problem by modifying the {\bf btraceback} script.
-Typical problems might be that {\bf gdb} is not on the default path. Fix this
-by specifying the full path to it in the {\bf btraceback} file. Another common
-problem is that the {\bf mail} program doesn't work or is not on the default
-path. On some systems, it is preferable to use {\bf Mail} rather than {\bf
-mail}.
+Typical problems might be that {\bf gdb} or {\bf dbx} for Solaris is not on
+the default path. Fix this by specifying the full path to it in the {\bf
+btraceback} file. Another common problem is that you haven't modified the
+script so that the {\bf bsmtp} program has an appropriate smtp server or
+the proper syntax for your smtp server. If you use the {\bf mail} program
+and it is not on the default path, it will also fail. On some systems, it
+is preferable to use {\bf Mail} rather than {\bf mail}.
\subsection*{Getting A Traceback On Other Systems}
\index[general]{Getting A Traceback On Other Systems }
\addcontentsline{toc}{subsection}{Getting A Traceback On Other Systems}
It should be possible to produce a similar traceback on systems other than
-Linux, either using {\bf gdb} or some other debugger. Solaris with {\bf gdb}
+Linux, either using {\bf gdb} or some other debugger. Solaris with {\bf dbx}
loaded works quite fine. On other systems, you will need to modify the {\bf
btraceback} program to invoke the correct debugger, and possibly correct the
{\bf btraceback.gdb} script to have appropriate commands for your debugger. If
projects / bacula / docs / commitdiff