[Box Backup] Latest Boxi Win32 binary
Tue, 4 Aug 2009 02:40:19 -0700 (PDT)
I get the message :-)
Thanks for the update.
I was just wondering if this was a bug and for reporting it as such I wante=
d to discus it.
Now I know how these things work.
Anyway, it seems you again have made a new version available(Great work!).
I will start using that one now.
--- On Mon, 8/3/09, Achim <firstname.lastname@example.org> wrote:
> From: Achim <email@example.com>
> Subject: Re: [Box Backup] Latest Boxi Win32 binary
> To: firstname.lastname@example.org
> Date: Monday, August 3, 2009, 5:04 PM
> Hello Edo:
> On Mon, 3 Aug 2009 13:47:53 -0700 (PDT), scartomail <email@example.com=
> > I have tested the latest Boxi version that Achim made
> > (Thanks for the great work by the way!)
> No problem. I am certain that more eyes on the price (i.e.
> stable Boxi)
> will make the combination Box Backup/Boxi a powerful tool.
> > It seems that you can configure most of the files.
> > Only the pid, sock and state files are not realy
> willing so to speak.
> > You can point the configurtion of boxi to the pid and
> sock files.
> > This is after I have copyd them manulay from the 0.0.7
> version test
> Please refer to the bug tracker  about how to configure
> this: I agree
> that the current way is not very elegant. It would also be
> great if you
> could check if a bug already exists on the tracker, add a
> comment, and in
> case you found a new one: report it in a way that somebody
> else can
> reproduce it. From a good introduction about how to write
> bug report :
> =A0 =A0 * The first aim of a bug report is to let the
> programmer see the
> failure with their own eyes. If you can't be with them to
> make it fail in
> front of them, give them detailed instructions so that they
> can make it
> fail for themselves.
> =A0 =A0 * In case the first aim doesn't succeed, and
> the programmer can't see
> it failing themselves, the second aim of a bug report is to
> describe what
> went wrong. Describe everything in detail. State what you
> saw, and also
> state what you expected to see. Write down the error
> messages, especially
> if they have numbers in.
> =A0 =A0 * When your computer does something
> unexpected, freeze. Do nothing
> until you're calm, and don't do anything that you think
> might be dangerous.
> =A0 =A0 * By all means try to diagnose the fault
> yourself if you think you can,
> but if you do, you should still report the symptoms as
> =A0 =A0 * Be ready to provide extra information if
> the programmer needs it. If
> they didn't need it, they wouldn't be asking for it. They
> aren't being
> deliberately awkward. Have version numbers at your
> fingertips, because they
> will probably be needed.
> =A0 =A0 * Write clearly. Say what you mean, and make
> sure it can't be
> =A0 =A0 * Above all, be precise. Programmers like
> > But the state file REALY needs to be there in a fixed
> > That is C:\Program Files\Box
> > I had to create the file and directory manualy or the
> backup is claiming
> > not to be configured right.
> I have not come across this: last_sync_start and
> last_sync_finish are
> created in the "DataDirectory" as per the .conf file.
> > They are just simple files, why not create them on the
> fly when the
> > starts?
> > I ques than it is not the responsibility of boxi
> > Or they could be created by boxi, all in one "working"
> > Once you point boxi to the directory it needs it is
> just a simple file
> > write command.
> See the DataDirectory in bbackupd.conf. That works for me,
> without the need
> for C:\Program Files\Box Backup\bbackupd\bbackup.state.
> > Anyway the 11 version already looks a lot better.
> I agree, Boxi has made quite some progress, and perhaps we
> can iron out
> most of the remaining issues this summer? Or at least
> report them?
> Thanks in advance, Achim
>  <https://sourceforge.net/tracker/?group_id=3D135105&atid=3D731482>
>  The author of Putty, another great piece of Free
> boxbackup mailing list