On Sun, Feb 08, 2004 at 06:31:13PM -0500, Gene Heskett wrote:
> On Sunday 08 February 2004 08:57, stan wrote:
> [...]
> >Well, I did, but it does have the problem of not having the 3rd
> > token in the DLE (before the "{" so amchekc complains about
> > duplicates
>
> Humm, I'll have to re-read tha
On Sunday 08 February 2004 08:57, stan wrote:
[...]
>Well, I did, but it does have the problem of not having the 3rd
> token in the DLE (before the "{" so amchekc complains about
> duplicates
Humm, I'll have to re-read that part, I'm confused. Not the first
time mind you :)
Checking my own disk
On Sat, Feb 07, 2004 at 10:31:01PM -0500, Gene Heskett wrote:
> On Saturday 07 February 2004 17:05, stan wrote:
> [snip down to the meat here]
> >To answer you specific question:
> >
> >$ amcheck DailyDump
> >
> >ERROR: black: [Can't open disk 'ad2s1e']
> >ERROR: black: [No include for 'ads2e/a
On Saturday 07 February 2004 19:42, stan wrote:
>On Sat, Feb 07, 2004 at 05:50:58PM -0500, Jon LaBadie wrote:
>> On Sat, Feb 07, 2004 at 05:05:49PM -0500, stan wrote:
>>
>> [ edited ]
>>
>> > OK, I've comletly broken it at this point in time :-(
>> >
>> > To answer you specific question:
>> >
>> >
On Saturday 07 February 2004 17:05, stan wrote:
[snip down to the meat here]
>To answer you specific question:
>
>$ amcheck DailyDump
>
>ERROR: black: [Can't open disk 'ad2s1e']
>ERROR: black: [No include for 'ads2e/ak']
>ERROR: black: [Can't open disk 'ad2s1e']
>ERROR: black: [No include for '
On Sat, Feb 07, 2004 at 05:50:58PM -0500, Jon LaBadie wrote:
> On Sat, Feb 07, 2004 at 05:05:49PM -0500, stan wrote:
>
> [ edited ]
> >
> > OK, I've comletly broken it at this point in time :-(
> >
> > To answer you specific question:
> >
> > $ amcheck DailyDump
> >
> > ERROR: black: [Can
On Sat, Feb 07, 2004 at 05:05:49PM -0500, stan wrote:
[ edited ]
>
> OK, I've comletly broken it at this point in time :-(
>
> To answer you specific question:
>
> $ amcheck DailyDump
>
> ERROR: black: [Can't open disk 'ad2s1e']
> ERROR: black: [No include for 'ads2e/ak']
> ERROR: black:
On Fri, Feb 06, 2004 at 10:25:06PM -0500, Gene Heskett wrote:
> On Friday 06 February 2004 19:49, stan wrote:
> >On Fri, Feb 06, 2004 at 02:44:24PM -0500, Gene Heskett wrote:
> >> On Friday 06 February 2004 13:51, stan wrote:
> >> >On Fri, Feb 06, 2004 at 03:48:38PM +0100, Paul Bijnens wrote:
> >>
On Friday 06 February 2004 19:49, stan wrote:
>On Fri, Feb 06, 2004 at 02:44:24PM -0500, Gene Heskett wrote:
>> On Friday 06 February 2004 13:51, stan wrote:
>> >On Fri, Feb 06, 2004 at 03:48:38PM +0100, Paul Bijnens wrote:
>> >> stan wrote:
>> >> >define dumptype comp-user-no-compress {
>> >> >
On Fri, Feb 06, 2004 at 02:44:24PM -0500, Gene Heskett wrote:
> On Friday 06 February 2004 13:51, stan wrote:
> >On Fri, Feb 06, 2004 at 03:48:38PM +0100, Paul Bijnens wrote:
> >> stan wrote:
> >> >define dumptype comp-user-no-compress {
> >> >comment "Non-root partitions on reasonably fast mac
On Fri, Feb 06, 2004 at 06:13:22PM -0500, Jon LaBadie wrote:
> On Fri, Feb 06, 2004 at 01:51:32PM -0500, stan wrote:
> ...
> > black ads2e/ak ad2s1e {
> > include "./[A-K]*"
> > user-tar-no-compress
> > } 3 local
> >
>
> Stan, just in case it is still not clear to you why people
> are
stan wrote:
black ads1e/kz ad1s1e {
exclude "./[A-K]*"
user-tar-no-compress
} 2 local
black ads1e/ak ad1s1e {
include "./[A-K]*"
user-tar-no-compress
} 2 local
Let's believe what you copy/pasted, but it's better to see what
amanda believes. you can f
On Friday 06 February 2004 13:51, stan wrote:
>On Fri, Feb 06, 2004 at 03:48:38PM +0100, Paul Bijnens wrote:
>> stan wrote:
>> >define dumptype comp-user-no-compress {
>> >comment "Non-root partitions on reasonably fast machines"
>> >index
>> >maxdumps 3
>> >priority medium
>> >}
>>
On Friday 06 February 2004 07:54, stan wrote:
>> I think it is simpler than that.
>>
>> -- first set --
>> include "./[A-K]*"
>>
>> -- second set --
>> exclude "./[A-K]*"
>
>Well, I still don't have somethign right here.
>
>Here is amstatus from last nights run:
>
>
>Script started on Fri Feb
On Fri, Feb 06, 2004 at 03:48:38PM +0100, Paul Bijnens wrote:
> stan wrote:
>
>
> >define dumptype comp-user-no-compress {
> >comment "Non-root partitions on reasonably fast machines"
> > index
> > maxdumps 3
> >priority medium
> >}
> >
> > black ads1e/kz ad1s1e {
> > exclude
stan wrote:
define dumptype comp-user-no-compress {
comment "Non-root partitions on reasonably fast machines"
index
maxdumps 3
priority medium
}
> black ads1e/kz ad1s1e {
>exclude "./[A-K]*"
>user-tar-no-compress
>} 2 local
You still seem to be referencing use
>
> I think it is simpler than that.
>
> -- first set --
> include "./[A-K]*"
>
> -- second set --
> exclude "./[A-K]*"
>
Well, I still don't have somethign right here.
Here is amstatus from last nights run:
Script started on Fri Feb 6 06:39:04 2004
$ amstatus DailyDump
black:ads1e/ak
On Thu, Feb 05, 2004 at 02:23:42PM -0500, Jon LaBadie wrote:
> On Thu, Feb 05, 2004 at 11:04:54AM -0500, stan wrote:
> >
> > OK, I think I understand. If I do then the follwing should do what I
> > intended the original to do:
> >
> > -- first set ---
> > include "./[A-K]*"
> > exclude "./[!A-K]*
On Thu, Feb 05, 2004 at 11:04:54AM -0500, stan wrote:
>
> OK, I think I understand. If I do then the follwing should do what I
> intended the original to do:
>
> -- first set ---
> include "./[A-K]*"
> exclude "./[!A-K]*"
>
> -- second set ---
> include "./[!A-K]*"
>
> Or, do I need an exclude
On Thu, Feb 05, 2004 at 04:32:26PM +0100, Paul Bijnens wrote:
> stan wrote:
>
> >On Thu, Feb 05, 2004 at 02:16:09PM +0100, Paul Bijnens wrote:
> >>stan wrote:
> >>
> >/foo/bar/[A-J]*
> >/foo/bar/[K-z]*
> >>
> >>Don't mix uppercase and lowercase in the character maps.
> >>It depends on the
On Thursday 05 February 2004 09:02, stan wrote:
>On Thu, Feb 05, 2004 at 08:03:16AM -0500, Joshua Baker-LePain wrote:
>> On Thu, 5 Feb 2004 at 7:49am, stan wrote
>>
>> > Note that for the 2 disks in question, both partial backusp
>> > claim identical size. I beileve that is because they are
>> > as
On Thu, Feb 05, 2004 at 09:21:16AM -0500, Joshua Baker-LePain wrote:
> On Thu, 5 Feb 2004 at 9:02am, stan wrote
>
> > On Thu, Feb 05, 2004 at 08:03:16AM -0500, Joshua Baker-LePain wrote:
> > > On Thu, 5 Feb 2004 at 7:49am, stan wrote
> > >
> > > > Note that for the 2 disks in question, both parti
stan wrote:
On Thu, Feb 05, 2004 at 02:16:09PM +0100, Paul Bijnens wrote:
stan wrote:
/foo/bar/[A-J]*
/foo/bar/[K-z]*
Don't mix uppercase and lowercase in the character maps.
It depends on the current LANG and/or LC_* settings what they
expand to. Probably not what you want.
Is there a way to t
On Thu, 5 Feb 2004 at 9:02am, stan wrote
> On Thu, Feb 05, 2004 at 08:03:16AM -0500, Joshua Baker-LePain wrote:
> > On Thu, 5 Feb 2004 at 7:49am, stan wrote
> >
> > > Note that for the 2 disks in question, both partial backusp claim identical
> > > size. I beileve that is because they are assumin
On Thu, Feb 05, 2004 at 02:16:09PM +0100, Paul Bijnens wrote:
> stan wrote:
>
> >>>/foo/bar/[A-J]*
> >>>/foo/bar/[K-z]*
>
> Don't mix uppercase and lowercase in the character maps.
> It depends on the current LANG and/or LC_* settings what they
> expand to. Probably not what you want.
>
> Maybe
On Thu, Feb 05, 2004 at 02:16:09PM +0100, Paul Bijnens wrote:
> stan wrote:
>
> >>>/foo/bar/[A-J]*
> >>>/foo/bar/[K-z]*
>
> Don't mix uppercase and lowercase in the character maps.
> It depends on the current LANG and/or LC_* settings what they
> expand to. Probably not what you want.
>
> Maybe
On Thu, Feb 05, 2004 at 08:03:16AM -0500, Joshua Baker-LePain wrote:
> On Thu, 5 Feb 2004 at 7:49am, stan wrote
>
> > Note that for the 2 disks in question, both partial backusp claim identical
> > size. I beileve that is because they are assuming the size of the entire
> > partion.
> >
> > # bla
stan wrote:
/foo/bar/[A-J]*
/foo/bar/[K-z]*
Don't mix uppercase and lowercase in the character maps.
It depends on the current LANG and/or LC_* settings what they
expand to. Probably not what you want.
Maybe you need this:
/foo/bar/[A-J]*
/foo/bar/[K-Za-z]*
Also notice these are not compleme
On Thu, 5 Feb 2004 at 7:49am, stan wrote
> Note that for the 2 disks in question, both partial backusp claim identical
> size. I beileve that is because they are assuming the size of the entire
> partion.
>
> # black ad1s1e comp-user-no-compress 2 local
> black ads1e/ak ad1s1e {
> include "
On Tue, Feb 03, 2004 at 07:23:20PM -0500, Joshua Baker-LePain wrote:
> On Tue, 3 Feb 2004 at 7:16pm, stan wrote
>
> > I've got a couple of 120G disk that contain files in a serries of
> > directories. I need to split these up to allow my DLT40 tape to back up
> > smaller checks.
> >
> > What I ha
On Tue, Feb 03, 2004 at 07:23:20PM -0500, Joshua Baker-LePain wrote:
> On Tue, 3 Feb 2004 at 7:16pm, stan wrote
>
> > I've got a couple of 120G disk that contain files in a serries of
> > directories. I need to split these up to allow my DLT40 tape to back up
> > smaller checks.
> >
> > What I ha
On Tue, 3 Feb 2004 at 7:16pm, stan wrote
> I've got a couple of 120G disk that contain files in a serries of
> directories. I need to split these up to allow my DLT40 tape to back up
> smaller checks.
>
> What I have in mind is something like this:
>
> /foo/bar/[A-J]*
> /foo/bar/[K-z]*
>
> But
I've got a couple of 120G disk that contain files in a serries of
directories. I need to split these up to allow my DLT40 tape to back up
smaller checks.
What I have in mind is something like this:
/foo/bar/[A-J]*
/foo/bar/[K-z]*
But if I put that in the disklist file amcheck says it's invalid.
33 matches
Mail list logo
