\label{seccom:poolfilejobretention}
We added two new Pool directives, \texttt{FileRetention} and
-\texttt{JobRetention}, that take precedence over Client directives of the same
-name. It allows you to control the Catalog pruning algorithm Pool by Pool. For
-example, you can decide to increase Retention times for Archive or OffSite Pool.
+\texttt{JobRetention}, that take precedence over Client directives of the
+same name. It allows you to control the Catalog pruning algorithm Pool by
+Pool. For example, you can decide to increase Retention times for Archive
+or OffSite Pool.
-It seems obvious to us, but apparently not to some users, that given the
+It seems obvious, but apparently not to some users, that given the
definition above that the Pool File and Job Retention periods is a global
override for the normal Client based pruning, which means that when the
Job is pruned, the pruning will apply globally to that particular Job.
-Currently, there is a bug in the implementation that causes any Pool
-retention periods specified to apply to {\bf all} Pools for that
-particular Client. Thus we suggest that you avoid using these two
-directives until this implementation problem is corrected.
-
\subsection{Read-only File Daemon using capabilities}
\label{seccom:fdreadonly}
-This feature implements support of keeping \textbf{ReadAll} capabilities after
-UID/GID switch, this allows FD to keep root read but drop write permission.
+This feature implements support of keeping \textbf{ReadAll} capabilities
+after UID/GID switch, this allows FD to keep root read but drop write
+permission.
It introduces new \texttt{bacula-fd} option (\texttt{-k}) specifying that
\textbf{ReadAll} capabilities should be kept after UID/GID switch.
projects / bacula / docs / blobdiff