Backup Central

Hello!

I've set up a new backup server, and for the first time I haven't disabled compression. BackupPC is now creating log files in (what it is claiming is) .z format. How do I read these? I've tried zcat ("not in gzip format"), uncompress (no error, but no file), and unzip (end of central directory not found). "file XferLog.0.z" says that this file is "data" (which doesn't help...).

So, how do I read these files, and even better: how do I go back to my plaintext logs?

(I *knew* there were great reasons why I have always immediately disable compresson on all of my backup servers! )

Tim Massey
Out of the Box Solutions, Inc.
Creative IT Solutions Made Simple!
[url=Arial]http://www.OutOfTheBoxSolutions.com[/url]
[url=Arial]tmassey < at > obscorp.com[/url] 22108 Harper Ave.
St. Clair Shores, MI 48080
Office: (800)750-4OBS (4627)
Cell: (586)945-8796

On Thu, Feb 9, 2012 at 3:51 PM, Timothy J Massey <tmassey < at > obscorp.com ([email]tmassey < at > obscorp.com[/email])> wrote:
Hello!

I've set up a new backup server, and for the first time I haven't disabled compression.  BackupPC is now creating log files in (what it is claiming is) .z format.  How do I read these?  I've tried zcat ("not in gzip format"), uncompress (no error, but no file), and unzip (end of central directory not found).  "file XferLog.0.z" says that this file is "data" (which doesn't help...).

So, how do I read these files, and even better:  how do I go back to my plaintext logs?


[url=http://www.mail-archive.com/backuppc-users < at > lists.sourceforge.net/msg19612.html]http://www.mail-archive.com/backuppc-users < at > lists.sourceforge.net/msg19612.html[/url]


Richard 

On 2/9/2012 4:51 PM, Timothy J Massey wrote:
Hello!

I've set up a new backup server, and for the first time I haven't
disabled compression. BackupPC is now creating log files in (what it
is claiming is) .z format. How do I read these? I've tried zcat
("not in gzip format"), uncompress (no error, but no file), and unzip
(end of central directory not found). "file XferLog.0.z" says that
this file is "data" (which doesn't help...).

So, how do I read these files, and even better: how do I go back to
my plaintext logs?

(I *knew* there were great reasons why I have always immediately
disable compresson on all of my backup servers! )

Backuppc uses a special compression format. You can read it with the
BackupPC_zcat program. On my machine, it is located in
/usr/local/BackupPC/bin.

--
Bowie

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Bowie Bailey <Bowie_Bailey < at > BUC.com> wrote on 02/09/2012 05:01:32 PM:

On 2/9/2012 4:51 PM, Timothy J Massey wrote:
Hello!

I've set up a new backup server, and for the first time I haven't
disabled compression. BackupPC is now creating log files in (what it
is claiming is) .z format. How do I read these? I've tried zcat
("not in gzip format"), uncompress (no error, but no file), and unzip
(end of central directory not found). "file XferLog.0.z" says that
this file is "data" (which doesn't help...).

So, how do I read these files, and even better: how do I go back to
my plaintext logs?

(I *knew* there were great reasons why I have always immediately
disable compresson on all of my backup servers! )

Backuppc uses a special compression format. You can read it with the
BackupPC_zcat program. On my machine, it is located in
/usr/local/BackupPC/bin.

I love BackupPC, but that is the *dumbest* thing *ever*. (Sorry, Craig! ).

And even if you for some reason thought that was a *brilliant* idea, why wouldn't you change the extension? Would bpz be so hard?

Tim Massey
Out of the Box Solutions, Inc.
Creative IT Solutions Made Simple!
[url=Arial]http://www.OutOfTheBoxSolutions.com[/url]
[url=Arial]tmassey < at > obscorp.com[/url] 22108 Harper Ave.
St. Clair Shores, MI 48080
Office: (800)750-4OBS (4627)
Cell: (586)945-8796


--
Bowie

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Bowie Bailey <Bowie_Bailey < at > BUC.com> wrote on 02/09/2012 05:01:32 PM:

Backuppc uses a special compression format. You can read it with the
BackupPC_zcat program. On my machine, it is located in
/usr/local/BackupPC/bin.

Oh, and to ask again: Can I turn this off? Or is this, for some reason, completely linked to the compression state of the backup?

Tim Massey
Out of the Box Solutions, Inc.
Creative IT Solutions Made Simple!
[url=Arial]http://www.OutOfTheBoxSolutions.com[/url]
[url=Arial]tmassey < at > obscorp.com[/url] 22108 Harper Ave.
St. Clair Shores, MI 48080
Office: (800)750-4OBS (4627)
Cell: (586)945-8796

On Thu, Feb 9, 2012 at 4:40 PM, Timothy J Massey <tmassey < at > obscorp.com ([email]tmassey < at > obscorp.com[/email])> wrote:
>
Backuppc uses a special compression format.  You can read it with the
BackupPC_zcat program.  On my machine, it is located in
/usr/local/BackupPC/bin.


I love BackupPC, but that is the *dumbest* thing *ever*.  (Sorry, Craig!    ).

And even if you for some reason thought that was a *brilliant* idea, why wouldn't you change the extension?  Would bpz be so hard?  


Most people would read them by clicking on the links in the web interface and not know/care whether there was an extension or not.

-- 
   Les Mikesell
      lesmikesell < at > gmail.com ([email]lesmikesell < at > gmail.com[/email])

Timothy J Massey wrote at about 16:51:34 -0500 on Thursday, February 9, 2012:
Hello!

I've set up a new backup server, and for the first time I haven't disabled
compression. BackupPC is now creating log files in (what it is claiming
is) .z format. How do I read these? I've tried zcat ("not in gzip
format"), uncompress (no error, but no file), and unzip (end of central
directory not found). "file XferLog.0.z" says that this file is "data"
(which doesn't help...).

So, how do I read these files, and even better:

/usr/share/BackupPC/bin/BackupPC_zcat
(exact location may be different on your system)

how do I go back to my plaintext logs?
I don't believe you can. The logs are pooled and hence when
compression is turned on they are compressed and stored in the cpool.

(I *knew* there were great reasons why I have always immediately disable
compresson on all of my backup servers! )

It's really not a big deal...


Tim Massey


Out of the Box Solutions, Inc.
Creative IT Solutions Made Simple!
http://www.OutOfTheBoxSolutions.com
tmassey < at > obscorp.com

22108 Harper Ave.
St. Clair Shores, MI 48080
Office: (800)750-4OBS (4627)
Cell: (586)945-8796

----------------------------------------------------------------------
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/

----------------------------------------------------------------------
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Timothy J Massey wrote at about 17:40:43 -0500 on Thursday, February 9, 2012:
Bowie Bailey <Bowie_Bailey < at > BUC.com> wrote on 02/09/2012 05:01:32 PM:

On 2/9/2012 4:51 PM, Timothy J Massey wrote:
Hello!

I've set up a new backup server, and for the first time I haven't
disabled compression. BackupPC is now creating log files in (what it
is claiming is) .z format. How do I read these? I've tried zcat
("not in gzip format"), uncompress (no error, but no file), and unzip
(end of central directory not found). "file XferLog.0.z" says that
this file is "data" (which doesn't help...).

So, how do I read these files, and even better: how do I go back to
my plaintext logs?

(I *knew* there were great reasons why I have always immediately
disable compresson on all of my backup servers! )

Backuppc uses a special compression format. You can read it with the
BackupPC_zcat program. On my machine, it is located in
/usr/local/BackupPC/bin.

I love BackupPC, but that is the *dumbest* thing *ever*. (Sorry, Craig!
).

Why?

BackupPC compresses and pools the log files which is consistent with
the handling of all other files in the pc tree (except for the
'backups' info file). This keeps everything streamlined and
consistent.

Of course one could have made another design choice, but calling this
"the dumbest thing ever" is not very helpful nor intelligent.

And even if you for some reason thought that was a *brilliant* idea, why
wouldn't you change the extension? Would bpz be so hard?

Because it uses zLib compression and I believe .Z is a common
extension for that. This is not the DOS/Windows world where you just
willy-nilly make up new 3 letter extensions for every program under
the sun.

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Les Mikesell <lesmikesell < at > gmail.com> wrote on 02/10/2012 01:06:54 AM:

On Thu, Feb 9, 2012 at 4:40 PM, Timothy J Massey <tmassey < at > obscorp.com> wrote:

Backuppc uses a special compression format. You can read it with the
BackupPC_zcat program. On my machine, it is located in
/usr/local/BackupPC/bin.


I love BackupPC, but that is the *dumbest* thing *ever*. (Sorry,
Craig! ).

And even if you for some reason thought that was a *brilliant* idea,
why wouldn't you change the extension? Would bpz be so hard?

Most people would read them by clicking on the links in the web
interface and not know/care whether there was an extension or not.

Touche. But doesn't make this any smarter than it was...

I usually monitor backups (especially when I've just created a new guest to back up or when I'm having problems) by "tail -f /path/to/XferLog". I can't do that with these compressed log files (or, I can't figure out how to, anyway).

GUI's are great and all (and I use BackupPC's a *lot*), but it would be nice to not have them break the command line, too!

Or, at least, outsmart me. Does someone have a way to simulate a "tail -f" with the compressed logs?

Tim Massey
Out of the Box Solutions, Inc.
Creative IT Solutions Made Simple!
[url=Arial]http://www.OutOfTheBoxSolutions.com[/url]
[url=Arial]tmassey < at > obscorp.com[/url] 22108 Harper Ave.
St. Clair Shores, MI 48080
Office: (800)750-4OBS (4627)
Cell: (586)945-8796

"Jeffrey J. Kosowsky" <backuppc < at > kosowsky.org> wrote on 02/10/2012 08:55:34 AM:

Timothy J Massey wrote at about 17:40:43 -0500 on Thursday, February 9, 2012:
Bowie Bailey <Bowie_Bailey < at > BUC.com> wrote on 02/09/2012 05:01:32 PM:

On 2/9/2012 4:51 PM, Timothy J Massey wrote:
Hello!

I've set up a new backup server, and for the first time I haven't
disabled compression. BackupPC is now creating log files in (what it
is claiming is) .z format. How do I read these? I've tried zcat
("not in gzip format"), uncompress (no error, but no file), and unzip
(end of central directory not found). "file XferLog.0.z" says that
this file is "data" (which doesn't help...).

So, how do I read these files, and even better: how do I go back to
my plaintext logs?

(I *knew* there were great reasons why I have always immediately
disable compresson on all of my backup servers! )

Backuppc uses a special compression format. You can read it with the
BackupPC_zcat program. On my machine, it is located in
/usr/local/BackupPC/bin.

I love BackupPC, but that is the *dumbest* thing *ever*. (Sorry, Craig!
).

Why?

BackupPC compresses and pools the log files which is consistent with
the handling of all other files in the pc tree (except for the
'backups' info file). This keeps everything streamlined and
consistent.

At the price of making it, at a very minimum, very awkward to deal with. I can't easily cat, grep, tail, etc. I have to perform jumping-jacks to do any of these things, just so the files can be compressed.

And why would *log* files necessarily be handled consistently with backup data files? Do image manipulation programs store their log files in .GIF's?

In any case, the why or why not is not terribly important: it *does*. I asked if there was a way to make it not. I can only assume from the silence that there is not.

And even if you for some reason thought that was a *brilliant* idea, why
wouldn't you change the extension? Would bpz be so hard?

Because it uses zLib compression and I believe .Z is a common
extension for that. This is not the DOS/Windows world where you just
willy-nilly make up new 3 letter extensions for every program under
the sun.

No. .Z is *not* simply an extension for "I used zLib on this". .Z is the extension used for files created by the "compress" command. Try using the "compress" command on a BackupPC log file...

And whether UNIX or DOS, having two *incompatible* file types share the same extension is just a really bad idea. Would you expect to find a .gz file that couldn't be handled by gzip?!? Oh, excuse me, was that neither helpful nor intelligent?

Tim Massey
Out of the Box Solutions, Inc.
Creative IT Solutions Made Simple!
[url=Arial]http://www.OutOfTheBoxSolutions.com[/url]
[url=Arial]tmassey < at > obscorp.com[/url] 22108 Harper Ave.
St. Clair Shores, MI 48080
Office: (800)750-4OBS (4627)
Cell: (586)945-8796

Timothy J Massey wrote at about 09:52:03 -0500 on Friday, February 10, 2012:
"Jeffrey J. Kosowsky" <backuppc < at > kosowsky.org> wrote on 02/10/2012 08:55:34
AM:

Timothy J Massey wrote at about 17:40:43 -0500 on Thursday, February 9,
2012:
At the price of making it, at a very minimum, very awkward to deal with. I
can't easily cat, grep, tail, etc. I have to perform jumping-jacks to do
any of these things, just so the files can be compressed.

The log files can be quite long and they contain a lot of
redundancy allowing for very high compression levels . Compression is
a good idea here!

And why would *log* files necessarily be handled consistently with backup
data files? Do image manipulation programs store their log files in
.GIF's?

I think it is very *clever* to use the same pooling and compression
scheme for both the backup files and the metadata -- whether attrib
files or log files. You may think differently, but simply calling it
"the dumbest" idea ever shows both a lack of understanding and
appreciation of the work done by Craig, your smiley notwithstanding.

Because it uses zLib compression and I believe .Z is a common
extension for that. This is not the DOS/Windows world where you just
willy-nilly make up new 3 letter extensions for every program under
the sun.

No. .Z is *not* simply an extension for "I used zLib on this". .Z is the
extension used for files created by the "compress" command. Try using the
"compress" command on a BackupPC log file...

The point is that both 'compress' and BackupPC use 'zlib' compression,
hence rather than creating some non-standard new suffix, Craig chose
to use an existing standard to signal that it similarly uses
zlib. Again, you may have different tastes, but what Craig did makes
perfect sense to me by reminding me that the files are indeed compressed.

And whether UNIX or DOS, having two *incompatible* file types share the
same extension is just a really bad idea. Would you expect to find a .gz
file that couldn't be handled by gzip?!?

As many people have already told you, the log files are meant to be
read by the GUI. If you want to manually read and parse them yourself,
you are welcome to, but since they are not intended to be accessed
directly by users there was no need to be pedantic in the suffix
naming convention.

Oh, excuse me, was that neither helpful nor intelligent?

You are the one who called this "the dumbest idea". It's not "dumb" at
all, it just doesn't do what you want or expect it to do. If you don't
like it and would like an alternative option to have non-compressed
log files, then stop griping and either write your own code to add the
new functionality or pay someone else to write it. I'm really sick of
people who spend their time complaining rather than constructively
contributing back.


Tim Massey


Out of the Box Solutions, Inc.
Creative IT Solutions Made Simple!
http://www.OutOfTheBoxSolutions.com
tmassey < at > obscorp.com

22108 Harper Ave.
St. Clair Shores, MI 48080
Office: (800)750-4OBS (4627)
Cell: (586)945-8796

----------------------------------------------------------------------
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/

----------------------------------------------------------------------
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Timothy J Massey wrote at about 09:41:53 -0500 on Friday, February 10, 2012:
I usually monitor backups (especially when I've just created a new guest
to back up or when I'm having problems) by "tail -f /path/to/XferLog". I
can't do that with these compressed log files (or, I can't figure out how
to, anyway).

GUI's are great and all (and I use BackupPC's a *lot*), but it would be
nice to not have them break the command line, too!

Or, at least, outsmart me. Does someone have a way to simulate a "tail
-f" with the compressed logs?

Seems trivial to me (plus or minus some buffering delay)...

tail -n +0 -f /path/to/XferLog.Z | BackupPC_zcat

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

On Fri, Feb 10, 2012 at 8:41 AM, Timothy J Massey <tmassey < at > obscorp.com ([email]tmassey < at > obscorp.com[/email])> wrote:
> Most people would read them by clicking on the links in the web
interface and not know/care whether there was an extension or not.



Touche.  But doesn't make this any smarter than it was...

I usually monitor backups (especially when I've just created a new guest to back up or when I'm having problems) by "tail -f /path/to/XferLog".  I can't do that with these compressed log files (or, I can't figure out how to, anyway).


It's pretty rare to have problems that change in realtime between logfile lines.  Relax a little, get a cup of coffee, check the results when they show up.



GUI's are great and all (and I use BackupPC's a *lot*), but it would be nice to not have them break the command line, too!  


How is the documented BackupPC_zcat program broken.
 

Or, at least, outsmart me.  Does someone have a way to simulate a "tail -f" with the compressed logs?




Do it the same way tail does it.  Sleep a while and read again.

--
    Les Mikesell
     lesmikesell < at > gmail.com ([email]lesmikesell < at > gmail.com[/email])

"Jeffrey J. Kosowsky" <backuppc < at > kosowsky.org> wrote on 02/10/2012 10:33:38 AM:

Because it uses zLib compression and I believe .Z is a common
extension for that. This is not the DOS/Windows world where you just
willy-nilly make up new 3 letter extensions for every program under
the sun.

No. .Z is *not* simply an extension for "I used zLib on this". .Z is the
extension used for files created by the "compress" command. Try using the
"compress" command on a BackupPC log file...

The point is that both 'compress' and BackupPC use 'zlib' compression,
hence rather than creating some non-standard new suffix, Craig chose
to use an existing standard to signal that it similarly uses
zlib. Again, you may have different tastes, but what Craig did makes
perfect sense to me by reminding me that the files are indeed compressed.

Hey, JAR files and ODT files use LZW compression, just like ZIP! Why don't we use ZIP as an extension for them? It would be so... elegant!

The point of an extension is to tell the poor, lowly human what type of data is contained in that file in a glance. If someone creates a random new file format (kind of like BackupPC's compressed log format!), they should *NOT* recycle a very well understood extension so that the poor, lowly human won't be able to figure out why the canonical tool for working with that format doesn't work (which it does *not*) without some sort of magic knowledge. The fact that zLib was (ab)used to create this new format does not mean you should use .Z, any more than OpenOffice (or Java or any of the dozens of new formats that ZIP their multi-file contents) should call their files .ZIP.

And at least in the case of OpenOffice, et. al, the canonical ZIP management tool *WILL* *ACTUALLY* do something productive, unlike BackupPC's .Z log files and the canonical tool for managing .Z files.

Oh, excuse me, was that neither helpful nor intelligent?

You are the one who called this "the dumbest idea". It's not "dumb" at
all, it just doesn't do what you want or expect it to do. If you don't
like it and would like an alternative option to have non-compressed
log files, then stop griping and either write your own code to add the
new functionality or pay someone else to write it. I'm really sick of
people who spend their time complaining rather than constructively
contributing back.

Because I *never* contribute to the BackupPC community...

Tim Massey
Out of the Box Solutions, Inc.
Creative IT Solutions Made Simple!
[url=Arial]http://www.OutOfTheBoxSolutions.com[/url]
[url=Arial]tmassey < at > obscorp.com[/url] 22108 Harper Ave.
St. Clair Shores, MI 48080
Office: (800)750-4OBS (4627)
Cell: (586)945-8796

Timothy J Massey wrote at about 11:27:36 -0500 on Friday, February 10, 2012:
"Jeffrey J. Kosowsky" <backuppc < at > kosowsky.org> wrote on 02/10/2012 10:33:38
AM:
The point is that both 'compress' and BackupPC use 'zlib' compression,
hence rather than creating some non-standard new suffix, Craig chose
to use an existing standard to signal that it similarly uses
zlib. Again, you may have different tastes, but what Craig did makes
perfect sense to me by reminding me that the files are indeed
compressed.

Hey, JAR files and ODT files use LZW compression, just like ZIP! Why
don't we use ZIP as an extension for them? It would be so... elegant!

The point of an extension is to tell the poor, lowly human what type of
data is contained in that file in a glance.

This is truly getting tiresome. You have been told by multiple people,
multiple times that the "poor, lowly human" is not supposed to be
reading these files directly. "Poor, lowly humans" are expected to use
the documented GUI.

For those who want to delve into the internal file structure of
BackupPC, Craig has been kind enough to *signal* compression using the
.Z extension. If anybody is too confused by this or does not understand the
structure of BackupPC well enough to know how to read such files, then
that person should probably stick with the GUI.

The developer, and in particular an open source developer, has no
obligation to make all the inner workings coincide with your idea of
how internal files should be named.

When I first started playing with BackupPC it took me all of about 10
seconds to figure out that cat/gzip/compress etc. did not work on
these files and that I had to use the *included* BackupPC_zcat
utility. It took orders of magnitude less time than this thread
flaming Craig for the "dumbest" idea.

If someone creates a random new file format (kind of like
BackupPC's compressed log format!), they should *NOT* recycle a
very well understood extension so that the poor, lowly human won't
be able to figure out why the canonical tool for working with that
format doesn't work (which it does *not*) without some sort of
magic knowledge. The fact that zLib was (ab)used to create this
new format does not mean you should use .Z, any more than
OpenOffice (or Java or any of the dozens of new formats that ZIP
their multi-file contents) should call their files .ZIP.

And at least in the case of OpenOffice, et. al, the canonical ZIP
management tool *WILL* *ACTUALLY* do something productive, unlike
BackupPC's .Z log files and the canonical tool for managing .Z files.

It's an *internal* file -- not meant to be accessed by every day
users. Those that want to delve in have never had any problem figuring
it out before. It's truly not worth complaining about.

Personally, the last thing I want is to have another three letter
extension I need to remember. YMMV. If it truly bothers you so much
then submit a patch or fork the code and use your own naming
convention. There are many more important things to worry about and
much better uses of limited and valuable programming time for
BackupPC.

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/