Hello,
Bacula version 1.38.10:
Well, this version despite careful testing here, turned out to be a rather
disasterous release because there were a lot of users experiencing either a
deadlocked Director (Linux) or Director crashes (FreeBSD). As best I can
tell, this occurs (occurred) on systems where there was a clock shift of more
than 10 seconds. Why some systems see this and others not, I am unsure. I
can only speculate that some systems don't have properly defined
"step-tickers". If you use NTP and haven't defined step-tickers, you can get
sudden clock changes once NTP synchronizes ...
Anyway, the base problem was a missing unlock_jobs() call in a loop that
terminated early.
As most of you know, I have released a patch for this that I strong recommend
to everyone. At the same time, I am not very happy about users upgrading to
1.38.10 and being obligated to immediately apply a patch, so either today or
tomorrow, I will be releasing a 1.38.11 that includes the patch. If you have
already loaded from rpm 1.38.10-2 or 1.38.10-3, you already have the code
with the patch fixed.
In addition, I have recently modified licenses for some of the documentation
(see 1.38.11 release notes for details) and clarified the licenses for the
other docs directories (home-page, techlogs, ...).
If all goes well, this patch will *finally* fix most if not all the problems
of the "reload" command failing AND *hopefully* the daylight saving time
shift problems (untested).
Bacula version 1.39.x:
This release is coming along nicely, but there is still more work to do.
Though I generally do not like deadlines, I would like to set mid-July as a
cutoff for new features, and addition of major new code into the HEAD (e.g.
the new Win32 cross-compiling code). This does not at all mean that the code
must be complete, but just that the major cut will be in, and unless
something really spectacular comes up, no new features will be added.
By the end of July, I would like to have the 1.39.x code stabalized enough
(again, not all code may be complete) so that we can begin beta testing. Then
hopefully in the weeks that follow, we can begin a code freeze permitting
only essential bug fixes ...
Vacations:
Well, I had planned to be here until at least mid-September or mid-October
until version 1.40.0 is released, but my son-in-law has announced his
marriage in August in Norway, so I will be on vacation between 8 August and
13 August. I don't expect that this will have any impact on our current
development efforts.
--
Best regards,
Kern
(">
/\
V_V
PS: Flame material:
There are a few users out there who do not appreciate my comments about Fedora
FC5, but I do enjoy venting my frustration from time to time, even if I do
get mildly flamed for it :-) So, here it goes again:
My three main criteria for a distro are stability, recent software, and
security updates. From the beginning of my Open Source efforts in 1998, I
have used RedHat/Whitebox(RedHat compatible)/Fedora. I was always relatively
satisfied with RedHat as their mix of the three criteria meet my personal
(and I stress, my *personal*) needs. I switched to Whitebox when RedHat went
commercial then to Fedora, because it looked like they would carry on in the
old RedHat tradition. Unfortunately that was not the case because, under
Fedora FC4, I suffered through a number of disasterous updates (OO that seg
faulted every 5 minutes, tetex that destroyed converted image files, ...).
Now after upgrading all but my laptops and servers from FC4 to FC5, I have
run into a huge number of problems, and Fedora no longer meets my needs for
stability.
Searching for a new distro is not so easy. Kubuntu treats users as idiots by
disabling the root account and giving full sudo privilege to the main user.
Ubuntu won't boot on a relatively modern (1.5 years old) machine. Debian is
great on stability and security updates, but has really old software. If you
use Debian testing, you get good stability and recent software but
"currently" (they are in the process of changing) no security updates.
So, finally I think I have settled on SuSE for my desktop machine. Not an easy
decision. Positive: they are very close to RedHat/Fedora so I can easily
find my way around; they have the best installer and graphical management
interface (Yast2) that I have ever seen baring none; and they have a very
professional looking desktop and nice KDE integration. Negative: they do not
support SELinux, so you can forget SuSE for a server (in my book); they have
talked about dropping KDE support or turning it over to users; Novell might
just decide to go the full commercial route à la RedHat.
So, bottom line: you can probably expect less support from Bacula for Fedora,
more for SuSE (probably my development machine in 1-2 weeks time), and more
support for Debian (or possibly CentOS), which will most likely be my server
machine. Note, even if I don't use Debian for my server, Bacula support for
Debian will surely increase as I will shortly have a Debian test machine
environment (burning the isos today ...).
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
