From boxbackup-dev@fluffy.co.uk  Sat Jan 12 20:07:23 2008
From: boxbackup-dev@fluffy.co.uk (dave bamford)
Date: Sat, 12 Jan 2008 20:07:23 +0000
Subject: [Box Backup-dev] Re: #2: When downloading a large file (>0x7fffffff) from server,
 connection is aborted
In-Reply-To: <049.b5f95fa616f051991a0a22a9a757a06e@fluffy.co.uk>
References: <040.db19408560ec8a63e8b2c86a37ee9913@fluffy.co.uk> <049.b5f95fa616f051991a0a22a9a757a06e@fluffy.co.uk>
Message-ID: <47891DFB.6060108@logical-progress.com>

Hi Chris

What version should I go for and where should I get it from. I currently 
use Debian
and fedora for servers.

Cheers Dave.

Box Backup wrote:

>#2: When downloading a large file (>0x7fffffff) from server, connection is
>aborted
>----------------------------+-----------------------------------------------
>  Reporter:  ben            |       Owner:  chris                                                      
>      Type:  defect         |      Status:  assigned                                                   
>  Priority:  critical       |   Milestone:  0.11                                                       
> Component:  box libraries  |     Version:  0.10                                                       
>Resolution:                 |    Keywords:  windows unix large file BackupStore BadBackupStoreFile 4/11
>----------------------------+-----------------------------------------------
>Comment (by chris):
>
> Hi Dave,
>
> You need to upgrade the server as well to fix this problem. There are bugs
> on both sides. You also need to delete any old copies of the file on the
> server.
>
> Cheers, Chris.
>
>  
>


From boxbackup-dev@fluffy.co.uk  Sun Jan 13 01:04:19 2008
From: boxbackup-dev@fluffy.co.uk (Chris Wilson)
Date: Sun, 13 Jan 2008 01:04:19 +0000 (GMT)
Subject: [Box Backup-dev] Re: #2: When downloading a large file (>0x7fffffff)
 from server, connection is aborted
In-Reply-To: <47891DFB.6060108@logical-progress.com>
References: <040.db19408560ec8a63e8b2c86a37ee9913@fluffy.co.uk>
 <049.b5f95fa616f051991a0a22a9a757a06e@fluffy.co.uk> <47891DFB.6060108@logical-progress.com>
Message-ID: <Pine.LNX.4.64.0801130103560.20882@top.qwarx.com>

Hi Dave,

On Sat, 12 Jan 2008, dave bamford wrote:

> What version should I go for and where should I get it from. I currently 
> use Debian and fedora for servers.

Might I recommend the recently released 0.11rc1? :-)

Cheers, Chris.
-- 
_____ __     _
\  __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |

From boxbackup-dev@fluffy.co.uk  Thu Jan 24 01:10:12 2008
From: boxbackup-dev@fluffy.co.uk (Matt Brown)
Date: Thu, 24 Jan 2008 01:10:12 +0000
Subject: [Box Backup-dev] Re: #44: Unable to cd into deleted directories
In-Reply-To: <051.b0a8b645c333b78755b3ec4130d5fe19@fluffy.co.uk>
References: <042.068b378c5ec81a12fa3d2f3d7716f9bb@fluffy.co.uk> <051.b0a8b645c333b78755b3ec4130d5fe19@fluffy.co.uk>
Message-ID: <C3015B08-1B14-4C5A-9F61-4B12B26EC234@mbrown.co.uk>

Hi Chris,

> #44: Unable to cd into deleted directories
> --------------------------- 
> +------------------------------------------------
>  Reporter:  chris         |       Owner:  chris
>      Type:  defect        |      Status:  closed
>  Priority:  normal        |   Milestone:  0.12
> Component:  bbackupquery  |     Version:  0.11rc1
> Resolution:  worksforme    |    Keywords:  cd deleted directory  
> restore
> --------------------------- 
> +------------------------------------------------
> Changes (by chris):
>
>  * status:  new => closed
>  * resolution:  => worksforme
>
> Comment:
>
> Works for me, with the `cd -d` command in `bbackupquery`.


Fantastic, thanks for this... where should I grab from ? Trunk or  
should I wait for RC2 ?

(This product just gets better and better)

Regards

Matt Brown

From boxbackup-dev@fluffy.co.uk  Thu Jan 24 08:45:59 2008
From: boxbackup-dev@fluffy.co.uk (Chris Wilson)
Date: Thu, 24 Jan 2008 08:45:59 +0000 (GMT)
Subject: [Box Backup-dev] Re: #44: Unable to cd into deleted directories
In-Reply-To: <C3015B08-1B14-4C5A-9F61-4B12B26EC234@mbrown.co.uk>
References: <042.068b378c5ec81a12fa3d2f3d7716f9bb@fluffy.co.uk>
 <051.b0a8b645c333b78755b3ec4130d5fe19@fluffy.co.uk>
 <C3015B08-1B14-4C5A-9F61-4B12B26EC234@mbrown.co.uk>
Message-ID: <Pine.LNX.4.64.0801240845210.26095@top.qwarx.com>

Hi Matt,

On Thu, 24 Jan 2008, Matt Brown wrote:

> >#44: Unable to cd into deleted directories
> >---------------------------+------------------------------------------------
> > Reporter:  chris         |       Owner:  chris
> >     Type:  defect        |      Status:  closed
> >Priority:  normal        |   Milestone:  0.12
> >Component:  bbackupquery  |     Version:  0.11rc1
> >Resolution:  worksforme    |    Keywords:  cd deleted directory restore
> >---------------------------+------------------------------------------------
> >Changes (by chris):
> >
> > * status:  new => closed
> > * resolution:  => worksforme
> >
> >Comment:
> >
> >Works for me, with the `cd -d` command in `bbackupquery`.
> 
> Fantastic, thanks for this... where should I grab from ? Trunk or should I
> wait for RC2 ?

Sorry, I didn't fix anything, it didn't appear to be broken. Try "cd -d" 
with your existing install.

> (This product just gets better and better)

:-)

Cheers, Chris.
-- 
_____ __     _
\  __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Ruby/Perl/SQL Developer |
\ _/_/_/_//_/___/ | We are GNU : free your mind & your software |

From boxbackup-dev@fluffy.co.uk  Thu Jan 24 09:36:22 2008
From: boxbackup-dev@fluffy.co.uk (Matt Brown)
Date: Thu, 24 Jan 2008 09:36:22 +0000
Subject: [Box Backup-dev] Re: #44: Unable to cd into deleted directories
In-Reply-To: <Pine.LNX.4.64.0801240845210.26095@top.qwarx.com>
References: <042.068b378c5ec81a12fa3d2f3d7716f9bb@fluffy.co.uk> <051.b0a8b645c333b78755b3ec4130d5fe19@fluffy.co.uk> <C3015B08-1B14-4C5A-9F61-4B12B26EC234@mbrown.co.uk> <Pine.LNX.4.64.0801240845210.26095@top.qwarx.com>
Message-ID: <BA87D4A4-1CDD-4A38-B1CF-9C844EA65A1D@mbrown.co.uk>

Hi Chris,

>>> Works for me, with the `cd -d` command in `bbackupquery`.
>>
>> Fantastic, thanks for this... where should I grab from ? Trunk or  
>> should I
>> wait for RC2 ?
>
> Sorry, I didn't fix anything, it didn't appear to be broken. Try "cd  
> -d"
> with your existing install.

Apologies, it does indeed work. I was looking at http://www.boxbackup.org/trac/wiki/RetrievingFiles 
, would it be worth adding this to the wiki ?

Kind Regards

Matt Brown


From boxbackup-dev@fluffy.co.uk  Thu Jan 24 19:38:19 2008
From: boxbackup-dev@fluffy.co.uk (Chris Wilson)
Date: Thu, 24 Jan 2008 19:38:19 +0000 (GMT)
Subject: [Box Backup-dev] Re: #44: Unable to cd into deleted directories
In-Reply-To: <BA87D4A4-1CDD-4A38-B1CF-9C844EA65A1D@mbrown.co.uk>
References: <042.068b378c5ec81a12fa3d2f3d7716f9bb@fluffy.co.uk>
 <051.b0a8b645c333b78755b3ec4130d5fe19@fluffy.co.uk>
 <C3015B08-1B14-4C5A-9F61-4B12B26EC234@mbrown.co.uk>
 <Pine.LNX.4.64.0801240845210.26095@top.qwarx.com>
 <BA87D4A4-1CDD-4A38-B1CF-9C844EA65A1D@mbrown.co.uk>
Message-ID: <Pine.LNX.4.64.0801241937490.26095@top.qwarx.com>

Hi Matt,

On Thu, 24 Jan 2008, Matt Brown wrote:

> >Sorry, I didn't fix anything, it didn't appear to be broken. Try "cd 
> >-d" with your existing install.
> 
> Apologies, it does indeed work. I was looking at 
> http://www.boxbackup.org/trac/wiki/RetrievingFiles, would it be worth 
> adding this to the wiki ?

Definitely. Do you have write access? Can you add it for me?

Cheers, Chris.
-- 
_____ __     _
\  __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Ruby/Perl/SQL Developer |
\ _/_/_/_//_/___/ | We are GNU : free your mind & your software |

From boxbackup-dev@fluffy.co.uk  Thu Jan 24 21:02:58 2008
From: boxbackup-dev@fluffy.co.uk (Matt Brown)
Date: Thu, 24 Jan 2008 21:02:58 +0000
Subject: [Box Backup-dev] Re: #44: Unable to cd into deleted directories
In-Reply-To: <Pine.LNX.4.64.0801241937490.26095@top.qwarx.com>
References: <042.068b378c5ec81a12fa3d2f3d7716f9bb@fluffy.co.uk> <051.b0a8b645c333b78755b3ec4130d5fe19@fluffy.co.uk> <C3015B08-1B14-4C5A-9F61-4B12B26EC234@mbrown.co.uk> <Pine.LNX.4.64.0801240845210.26095@top.qwarx.com> <BA87D4A4-1CDD-4A38-B1CF-9C844EA65A1D@mbrown.co.uk> <Pine.LNX.4.64.0801241937490.26095@top.qwarx.com>
Message-ID: <89122221-2E87-4DBA-9E21-922D9596B493@mbrown.co.uk>

>
>>> Sorry, I didn't fix anything, it didn't appear to be broken. Try "cd
>>> -d" with your existing install.
>>
>> Apologies, it does indeed work. I was looking at
>> http://www.boxbackup.org/trac/wiki/RetrievingFiles, would it be worth
>> adding this to the wiki ?
>
> Definitely. Do you have write access? Can you add it for me?

I don't have a login to the Wiki, but if I can get an account I would  
be happy to.

Regards

Matt Brown

From boxbackup-dev@fluffy.co.uk  Sun Jan 27 22:00:42 2008
From: boxbackup-dev@fluffy.co.uk (Charles Lecklider)
Date: Sun, 27 Jan 2008 22:00:42 +0000
Subject: [Box Backup-dev] 0.11rc1 win32 code review
Message-ID: <479CFF0A.6020305@invis.net>

I had a few spare minutes today so I thought I'd take a quick look 
through the code for rc1. I've not looked through everything, but what I 
did seems to have far fewer bits of Win32-specific stuff scattered 
through it, and that can only be a good thing.

If there are any Win32 parts I've not listed that you think are worth a 
look let me know and I'll try to find some more time later this week.

-C



lib\backupclient\BackupClientCryptoKeys.cpp:

101: Use SecureZeroMemory() instead of memset(). See also 
lib\common\ZeroStream.cpp. I think OpenSSL has its own secure version of 
memset() which would make cross-platform stuff easier.


lib\win32\emu.cpp:

FormatMessage() needs FORMAT_MESSAGE_IGNORE_INSERTS set.


lib\server\WinNamedPipeStream.cpp:

130: Flags say BYTE mode pipe, comments say MESSAGE mode. Which is it 
supposed to be?

150: If a pipe is opened with FILE_FLAG_OVERLAPPED then all operations 
should be overlapped - including ConnectNamedPipe(). Use 
GetOverlappedResult() to, erm, get the result ;-)

215: Consider using WaitNamedPipe() with a sensible timeout, or don't 
use NMPWAIT_USE_DEFAULT_WAIT when creating the pipe.

167/398: ResetEvent() isn't needed if the event isn't a manual reset type.

472: See 150.

527: Not a good idea to rely on CancelIo() - it only cancels things on 
the thread that started them.


From boxbackup-dev@fluffy.co.uk  Sun Jan 27 23:19:48 2008
From: boxbackup-dev@fluffy.co.uk (Chris Wilson)
Date: Sun, 27 Jan 2008 23:19:48 +0000 (GMT)
Subject: [Box Backup-dev] 0.11rc1 win32 code review
In-Reply-To: <479CFF0A.6020305@invis.net>
References: <479CFF0A.6020305@invis.net>
Message-ID: <Pine.LNX.4.64.0801272305130.26095@top.qwarx.com>

Hi Charles,

On Sun, 27 Jan 2008, Charles Lecklider wrote:

> I had a few spare minutes today so I thought I'd take a quick look 
> through the code for rc1. I've not looked through everything, but what I 
> did seems to have far fewer bits of Win32-specific stuff scattered 
> through it, and that can only be a good thing.
> 
> If there are any Win32 parts I've not listed that you think are worth a 
> look let me know and I'll try to find some more time later this week.

Many, many thanks for taking the time to do this! Most of the things you 
pointed out look to be relatively easy to fix. I'll address them over the 
next few days.

But I have a big problem with the overlapped I/O stuff. Basically it makes 
the whole code for WinNamedPipeStream very difficult to read and 
understand the correctness of. I get a lot of errors from this code during 
the unit tests on Windows, and it sometimes hangs on XP (perhaps even on 
2K).

I'd really like to remove overlapped I/O completely. But I have a bit of a 
problem with that too, which is why I introduced it in the first place.

On Windows, we use a thread in BackupDaemon to manage the named pipe. 
Because it appears to be unsafe (causes deadlocks) to access the pipe in 
multiple threads (e.g. to Write() status messages from the main thread 
while the listener thread is blocked on Read()), I have to pass messages 
from the main thread to the listener thread and signal an Event when a new 
message is available for the listener to write to the named pipe.

Now the problem comes when multiple messages are received by the named 
pipe (from the control client). I haven't found a way to tell if there are 
still more messages (or bytes) queued on the pipe. If I just 
WaitForMultipleObjects(main-thread-event, named-pipe) then I don't know 
how many messages to read from the named pipe. If I just read one, then I 
could miss an important message, never read it and deadlock with the 
control client. If I read more than one, I'll end up blocking on Read() 
and never read any more messages from the main thread, so I could also 
deadlock if the control client is waiting for a message from the main 
thread (such as sync finished).

I really wanted to do a non-blocking read on the named pipe, to discover 
whether there are more messages waiting without blocking (and probably 
deadlocking) but I can't see how. Do you have any ideas about this?

Second question (easier I hope): I noticed that Win32 has a Timer API 
(CreateTimerQueueTimer) and I tried to use this to replace the horrible 
RunTimer thread, but the events seem to be delivered very late or not at 
all. I can post sample code if it helps (I don't want to commit it because 
it's badly broken), but do you have any recommendations about it or ideas 
why it might not be working properly? I think you recommended using 
something different in the past, was it Waitable Timer objects? Do they 
work better? 

Cheers, Chris.
-- 
_____ __     _
\  __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Ruby/Perl/SQL Developer |
\ _/_/_/_//_/___/ | We are GNU : free your mind & your software |

From boxbackup-dev@fluffy.co.uk  Mon Jan 28 01:18:10 2008
From: boxbackup-dev@fluffy.co.uk (Charles Lecklider)
Date: Mon, 28 Jan 2008 01:18:10 +0000
Subject: [Box Backup-dev] 0.11rc1 win32 code review
In-Reply-To: <Pine.LNX.4.64.0801272305130.26095@top.qwarx.com>
References: <479CFF0A.6020305@invis.net> <Pine.LNX.4.64.0801272305130.26095@top.qwarx.com>
Message-ID: <479D2D52.2040207@invis.net>

Chris Wilson wrote:
> I'd really like to remove overlapped I/O completely. But I have a bit of a 
> problem with that too, which is why I introduced it in the first place.

Overlapped IO is actually very simple; it's just explained amazingly 
poorly in the SDK. Before you rip it out, try using it more as it was 
intended to be used ;-)

1) Make sure you're using it everywhere; if you open a pipe with the 
overlapped flag then everything has to be overlapped.

2) Make sure you're not sharing overlapped structs. It's fine to re-use 
them after each request, but attempting to use one that's already in use 
will send you straight to deadlock, do not pass Go, do not collect £200.

3) Always use GetOverlappedResult(). Even when you want to wait for only 
a certain time before giving up: wait on the overlapped event, if it 
gets signalled then call GetOverlappedResult(), otherwise clean up and exit.

4) Let Windows reset the overlapped event when it wants to - don't try 
to babysit.

5) If you really really want to poll the pipe for a new message (and I 
don't understand why you'd want to - this is what threads are for), 
issue the overlapped read as usual, then call GetOverlappedResult() 
passing FALSE for bWait. That will always return immediately, with a 
message if there is one, or ERROR_IO_INCOMPLETE if there isn't.

6) Use message mode - it makes life much easier.

> Second question (easier I hope): I noticed that Win32 has a Timer API 
> (CreateTimerQueueTimer) and I tried to use this to replace the horrible 
> RunTimer thread, but the events seem to be delivered very late or not at 
> all. I can post sample code if it helps (I don't want to commit it because 
> it's badly broken), but do you have any recommendations about it or ideas 
> why it might not be working properly? I think you recommended using 
> something different in the past, was it Waitable Timer objects? Do they 
> work better? 

Have a look at RegisterWaitForSingleObject(). With a little care and 
attention you can use the overlapped event as the handle to wait for, 
and end up with some very simple and short code....

-C


From boxbackup-dev@fluffy.co.uk  Tue Jan 29 00:43:14 2008
From: boxbackup-dev@fluffy.co.uk (James O'Gorman)
Date: Tue, 29 Jan 2008 00:43:14 +0000
Subject: [Box Backup-dev] Re: [Box Backup-commit] COMMIT r2063 - in box/trunk/bin: bbackupd
 bbstored
In-Reply-To: <20080128235835.5CA6C3269E8@www.boxbackup.org>
References: <20080128235835.5CA6C3269E8@www.boxbackup.org>
Message-ID: <20080129004313.GT15350@netinertia.co.uk>

On Mon, Jan 28, 2008 at 11:58:35PM +0000, subversion@fluffy.co.uk wrote:
> Likewise, use @localstatedir_expanded@ as default location for temporary
> state (*.pid and bbackupd.sock), defaults to /usr/local/var, although
> /var/run may be better on LFS systems.

I must admit, I'm not sure about this. I've never seen a /usr/local/var
on any system, and /var/run is generally a pretty safe place to put
pidfiles and sockets.

Does autoconf make it possible to change the default location for
localstatedir or would it have to be another kludge in configure.ac?

James

From boxbackup-dev@fluffy.co.uk  Tue Jan 29 00:48:41 2008
From: boxbackup-dev@fluffy.co.uk (Chris Wilson)
Date: Tue, 29 Jan 2008 00:48:41 +0000 (GMT)
Subject: [Box Backup-dev] Re: [Box Backup-commit] COMMIT r2063 - in
 box/trunk/bin: bbackupd bbstored
In-Reply-To: <20080129004313.GT15350@netinertia.co.uk>
References: <20080128235835.5CA6C3269E8@www.boxbackup.org>
 <20080129004313.GT15350@netinertia.co.uk>
Message-ID: <Pine.LNX.4.64.0801290045120.26095@top.qwarx.com>

Hi James,

On Tue, 29 Jan 2008, James O'Gorman wrote:

> On Mon, Jan 28, 2008 at 11:58:35PM +0000, subversion@fluffy.co.uk wrote:
> > Likewise, use @localstatedir_expanded@ as default location for temporary
> > state (*.pid and bbackupd.sock), defaults to /usr/local/var, although
> > /var/run may be better on LFS systems.
> 
> I must admit, I'm not sure about this. I've never seen a /usr/local/var
> on any system, and /var/run is generally a pretty safe place to put
> pidfiles and sockets.
> 
> Does autoconf make it possible to change the default location for
> localstatedir or would it have to be another kludge in configure.ac?

I think we can override the default in the same way I did for sysconfdir, 
although it's not a documented technique. I think there's no official way 
to do this. Will do it now.

Cheers, Chris.
-- 
_____ __     _
\  __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Ruby/Perl/SQL Developer |
\ _/_/_/_//_/___/ | We are GNU : free your mind & your software |

From boxbackup-dev@fluffy.co.uk  Tue Jan 29 01:39:20 2008
From: boxbackup-dev@fluffy.co.uk (Eric Cronin)
Date: Mon, 28 Jan 2008 20:39:20 -0500
Subject: [Box Backup-dev] Re: [Box Backup-commit] COMMIT r2063 - in box/trunk/bin: bbackupd bbstored
In-Reply-To: <20080129004313.GT15350@netinertia.co.uk>
References: <20080128235835.5CA6C3269E8@www.boxbackup.org> <20080129004313.GT15350@netinertia.co.uk>
Message-ID: <AE663666-A134-4F9A-A6AC-4E10116D2E77@gizmolabs.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-16--74739100
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit


On Jan 28, 2008, at 7:43 PM, James O'Gorman wrote:

> On Mon, Jan 28, 2008 at 11:58:35PM +0000, subversion@fluffy.co.uk  
> wrote:
>> Likewise, use @localstatedir_expanded@ as default location for  
>> temporary
>> state (*.pid and bbackupd.sock), defaults to /usr/local/var, although
>> /var/run may be better on LFS systems.
>
> I must admit, I'm not sure about this. I've never seen a /usr/local/ 
> var
> on any system, and /var/run is generally a pretty safe place to put
> pidfiles and sockets.

The /var/bbackupd directory is the one I really care about for  
MacPorts.  That belongs in /opt/local/var/bbackupd in the MP hierarchy  
(/var which is actually /private/var is left for Apple).  Having the  
default be /var and not ${prefix}/var makes sense for most people, but  
the knob to override it would be good.

Thanks,
Eric

--Apple-Mail-16--74739100
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQEVAwUBR56DyIgz4Q+coYsSAQj+EggAin4MSlssgNy6H+8+cHPuM2C1Ez/Fi1RI
3aANLcO77nabXLnuwT1ZNUTVAu4pNxew9ITMJy9vKb1HmzkUDOx67xig7WM5nmgb
UVZe5c8jdK/G7vOwbY1tXuNqan1DuOl36M7C5f3oRjzfwcgfJZFVAgJ62KGwli+e
aTL0SWc6akmxPZM/LoCryvzxxqzjkQOGmmYzySdmQvyUaN4PaLnRTLxkmKQ/U4UW
GiFtbKLPxhmpqY5bTPvD3bIPLsoOfpMvqZJhqEgcF3ZvW2+o9ZanZa/wVYMOdPf8
xlHZVxCAEtpdK5iAUiJEqPDE+szp2tYlH9JAg4wakAs1bYbz9+pO4g==
=CEx1
-----END PGP SIGNATURE-----

--Apple-Mail-16--74739100--

From boxbackup-dev@fluffy.co.uk  Tue Jan 29 02:47:14 2008
From: boxbackup-dev@fluffy.co.uk (Eric Cronin)
Date: Mon, 28 Jan 2008 21:47:14 -0500
Subject: [Box Backup-dev] Re: [Box Backup-commit] COMMIT r2063 - in box/trunk/bin: bbackupd bbstored
In-Reply-To: <AE663666-A134-4F9A-A6AC-4E10116D2E77@gizmolabs.org>
References: <20080128235835.5CA6C3269E8@www.boxbackup.org> <20080129004313.GT15350@netinertia.co.uk> <AE663666-A134-4F9A-A6AC-4E10116D2E77@gizmolabs.org>
Message-ID: <33D56C34-3BD9-4941-AB93-9F1E05934853@gizmolabs.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-17--70664624
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit


On Jan 28, 2008, at 8:39 PM, Eric Cronin wrote:

>
> On Jan 28, 2008, at 7:43 PM, James O'Gorman wrote:
>
>> On Mon, Jan 28, 2008 at 11:58:35PM +0000, subversion@fluffy.co.uk  
>> wrote:
>>> Likewise, use @localstatedir_expanded@ as default location for  
>>> temporary
>>> state (*.pid and bbackupd.sock), defaults to /usr/local/var,  
>>> although
>>> /var/run may be better on LFS systems.
>>
>> I must admit, I'm not sure about this. I've never seen a /usr/local/ 
>> var
>> on any system, and /var/run is generally a pretty safe place to put
>> pidfiles and sockets.
>
> The /var/bbackupd directory is the one I really care about for  
> MacPorts.  That belongs in /opt/local/var/bbackupd in the MP  
> hierarchy (/var which is actually /private/var is left for Apple).   
> Having the default be /var and not ${prefix}/var makes sense for  
> most people, but the knob to override it would be good.

Actually, seems I was confused as to what actually goes into /var/ 
bbackupd.  Looks like its transient run-time files, so /var/run is  
fine for MacPorts too.


Semi-related, --sysconfdir is still getting ignored for me:

[dougal] ecronin% grep sysconfdir config.log
   $ ./configure --prefix=/opt/local --sysconfdir=/opt/local/etc
sysconfdir='/etc'
sysconfdir_expanded='/etc'


Thanks,
Eric

--Apple-Mail-17--70664624
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQEVAwUBR56Tsogz4Q+coYsSAQii+wf9H4UiAAs0W5wo7bjuoK8vI+eiigyAyeYU
KkcUSzaLUncVLfSgK2aooXNt9G8nGxMt/gPqHQMqXZmP5xv1gZ7PZDW7DW1cdpKQ
VYzM/e5/6qoWz0EoclQWt0j/oeDg69oV6/In2UdWeEnQHnqfyNwXp96HtTsuluM6
DOBvY8f1vSYRxy/nWHq9LqmPIg60hEyMBzpBqG/wDcBWbQ1l+5g7B95PbZqxyXxt
5eKw/uurp8IzKwg8Teu6fKGQo8FGaRrQQGl2i2F7WWRTTpyTQ2Y6QmSEOJr9hczw
uB5nBgzXXT4/jEKyKN2C1XHfegs/x4Mv4bMrYfX4kQifofY5vDlptA==
=UAPS
-----END PGP SIGNATURE-----

--Apple-Mail-17--70664624--

From boxbackup-dev@fluffy.co.uk  Tue Jan 29 09:17:22 2008
From: boxbackup-dev@fluffy.co.uk (James O'Gorman)
Date: Tue, 29 Jan 2008 09:17:22 +0000
Subject: [Box Backup-dev] Re: [Box Backup-commit] COMMIT r2063 - in
 box/trunk/bin: bbackupd bbstored
In-Reply-To: <33D56C34-3BD9-4941-AB93-9F1E05934853@gizmolabs.org>
References: <20080128235835.5CA6C3269E8@www.boxbackup.org> <20080129004313.GT15350@netinertia.co.uk> <AE663666-A134-4F9A-A6AC-4E10116D2E77@gizmolabs.org> <33D56C34-3BD9-4941-AB93-9F1E05934853@gizmolabs.org>
Message-ID: <20080129091722.GU15350@netinertia.co.uk>

On Mon, Jan 28, 2008 at 09:47:14PM -0500, Eric Cronin wrote:
>  Semi-related, --sysconfdir is still getting ignored for me:
> 
>  [dougal] ecronin% grep sysconfdir config.log
>    $ ./configure --prefix=/opt/local --sysconfdir=/opt/local/etc
>  sysconfdir='/etc'
>  sysconfdir_expanded='/etc'

Fix in r2077 in trunk.

James

From boxbackup-dev@fluffy.co.uk  Wed Jan 30 22:34:13 2008
From: boxbackup-dev@fluffy.co.uk (James O'Gorman)
Date: Wed, 30 Jan 2008 22:34:13 +0000
Subject: [Box Backup-dev] bin vs sbin
Message-ID: <20080130223412.GZ15350@netinertia.co.uk>

I'm just going over the manpages as I've noticed some of the sections
seem to be incorrect, and just thought - currently we put everything in
$prefix/bin.

Should we move the "system" commands to $prefix/sbin? By this I mean:

 * bbackupd
 * bbackupctl
 * bbackupd-config
 * bbstored
 * bbstoreaccounts
 * bbstored-certs
 * bbstored-config

bbackupquery seems to be the only "user" command that we actually have.
If everyone agrees with this, is it just a case of editing modules.txt?

James

