Re: full dump in degraded mode - possible?
Am 29.03.2013 06:30, schrieb Kamil Jońca: As far I know amanda does not do full dump when no tape (vtape in my case) is not available. Is there any way to force it? If not what is the rationale for this? (I would prefer keep disk with vtapes as short as possible turned on) KJ Hm, what about RTFM ? ;-) especialy man amanda.conf, where in the section about global parameters, it tells you something about the parameter reserve int, which defaults to 100, as to reserve 100% of holdingdisk-space for incremental backups if no tape is online. If you set this parameter to eg 10, amanda will happily do full dumps to the holdingdisk until ist is filled up to 90% and use the rest for incermentals only. hope that helps and happy easter to everyone Christoph
Re: full dump in degraded mode - possible?
C.Scheeder christ...@scheeder.de writes: Am 29.03.2013 06:30, schrieb Kamil Jońca: As far I know amanda does not do full dump when no tape (vtape in my case) is not available. Is there any way to force it? If not what is the rationale for this? (I would prefer keep disk with vtapes as short as possible turned on) KJ Hm, what about RTFM ? Shame on me :( ;-) especialy man amanda.conf, where in the section about global parameters, it tells you something about the parameter reserve int, which defaults to 100, Thanks. KJ -- http://modnebzdury.wordpress.com/2009/10/01/niewiarygodny-list-prof-majewskiej-wprowadzenie/ Political history is far too criminal a subject to be a fit thing to teach children. -- W. H. Auden
anybody USING the krb5 version?
Amanda Users:
I've installed amanda v3.3.3 but am having trouble getting the auth krb5
version to work.Is anybody actually using it yet?
When I run the xinetd as user=root it complains that
amcheck wants to be my dumpuser, operator. But it isn't happy running
xinetd as operator either.
I've manually moved the seteuid(0)paragraph in amandad.c
/* krb5 require the euid to be 0 */
if (strcasecmp(auth, krb5) == 0) {
seteuid((uid_t)0);
}
so it's before the if krb5 then you need to be root
paragraph. That got me a little further. But now it complains that it isn't
being
UN-prived properly.
Manually adding setuid(11) and seteuid (11)(the id for my dumpuser,
operator)
at the tail end of common-src/krb5-security.c fixed the whole thing
AND AMCHECK AND ALSO AMDUMP WORK PERFECTLY.
But that's cheating, manually setting the UID downwards. Is it in the code
already,
proved by the fact that somebody else has got it to work? Or shall we continue
to poke around to find the proper way to down-set the UID, and then send it
in?
Deb Baddorf
Fermilab
PS googling for the error msgs I'm getting, makes me think that no one has
tried
this in a few years, and that they never resolved it either.
