Re: [Bacula-users] Tiny Bug

[Kern S. <ke...@si...>]

Hello,

Ah yes. The value is internally kept in seconds, and originally
the default was seconds, but I found that to be unreasonable
in many situations (e.g. Retention periods), so I changed the
default with no qualifier (i.e. no s,d,h,...) to be days.

Unfortunately, I didn't fix the manual.  I'll go back and=20
clear that up.  Thanks for bringing it up.

Best regards,

Kern

PS: This changed in 1.31 Beta 20May03. The ChangeLog entry is:
- Make default "duration" days rather than seconds if there is no
modifier.

On Tue, 2003-07-15 at 14:36, Marc Brueckner der Megauser wrote:
> Hi @ all,
>=20
> while testing backups and restores from and to windows machines I found a=
 tiny bug=20
> that confused me some time ago.
> Its about the "FD Connect Timeout" and "SD Connect Timeout" entry in the =
Director=20
> Resource. The Manual says that the timeout has to be specified in seconds=
, but bacula=20
> interprets this values as days. E.g.
>=20
> bacula-dir.conf:
> ...
> ...
> 	FD Connect Timeout =3D 60  # I would like to have 60 seconds
> ...
> ...
>=20
> Console:
> *show director
> Director: name=3DBacula-dir MaxJobs=3D4 FDtimeout=3D5184000 SDtimeout=3D5=
184000
>    query_file=3D/etc/bacula/query.sql
>=20
>=20
> But if I enter
>=20
>     FD Connect Timeout =3D 60s  # I would like to have 60 seconds
>                                              ^
> *show director
> Director: name=3DBacula-dir MaxJobs=3D4 FDtimeout=3D60 SDtimeout=3D60
>    query_file=3D/etc/bacula/query.sql
> 	=09
>=20
> Bye=20
> Marc
>=20
>=20
> -------------------------------------------------------
> This SF.Net email sponsored by: Parasoft
> Error proof Web apps, automate testing & more.
> Download & eval WebKing and get a free book.
> www.parasoft.com/bulletproofapps1
> _______________________________________________
> Bacula-users mailing list
> Bac...@li...
> https://lists.sourceforge.net/lists/listinfo/bacula-users