inconsistant config argument
The typical "example" amanda configuration is 'DailySet1'. To much typing for me, so I normally use 'DS1'. Thinking some amanda commands let you skip the config argument and default to a "coded-in" 'DailySet1' I was looking for how to define the default when using pre-built binaries. Looking at manpages, such cmds are few to non-existant, so this point is moot. However looking at the manpages showed great variety is how different commands accept the argument. It seems something so basic should be more consistant. Here are some samples, note this is based on the manpages which we all know sometimes lag the actual code. # --config not required, required amstatus [--config] # --config not allowed, required amdump amcheck # --config not allowed, optional amreport []# optional if in config dir # with the amanda.conf # not required, --config required IF is given amrestore [--config ] amdump_client [--config ] That's a lot of variability for something so important. Jon -- Jon H. LaBadie j...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
Re: segfault from planner (3.4.2-1)
On Fri, Feb 24, 2017 at 01:50:03PM -0500, Jon LaBadie wrote: > On Mon, Feb 20, 2017 at 07:55:27AM -0500, Jean-Louis Martineau wrote: > > Uwe, > > > > Thanks for your good bug report and patch. > > Can you tried the attached patch instead of yours? > > > > Jean-Louis > > Any idea when the patch will make it into the > "prebuilt" community packages? > > I erased the CentOS7 repo version (3.3.3) with > the community package. Surprisingly, the first > backup worked like a champ. Since then I've > gotten the same planner segfault as Uwe reports. > Minor addendum, downgraded to community version 3.4.1. Backup is in progress, well past where segfault was occurring. Still can't get amdump_client to work. Jon -- Jon H. LaBadie j...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
Re: segfault from planner (3.4.2-1)
On Mon, Feb 20, 2017 at 07:55:27AM -0500, Jean-Louis Martineau wrote: > Uwe, > > Thanks for your good bug report and patch. > Can you tried the attached patch instead of yours? > > Jean-Louis Any idea when the patch will make it into the "prebuilt" community packages? I erased the CentOS7 repo version (3.3.3) with the community package. Surprisingly, the first backup worked like a champ. Since then I've gotten the same planner segfault as Uwe reports. Jon -- Jon H. LaBadie j...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
Problems running amanda 3.4.2 on Debian jessie
The new package of amanda 3.4.2 for Debian is working on sid and testing for some people. But after I have done the upgrade of amanda on my home server, running jessie, it fails. The Debian package of amanda 3.4.2 was recompiled for jessie. The easiest way to check that it fails is "amcheck -c DailySet1": Amanda Backup Client Hosts Check (process:24609): GLib-ERROR **: /build/glib2.0-3vWc1h/glib2.0-2.42.1/./glib/gmem.c:103: failed to allocate 494820 bytes (brought to you by Amanda 3.4.2) How can I help diagnose the problem? Kind regards Jose M Calhariz -- -- A fortuna que eu gasto hoje será uma bagatela amanhã --Sol Kerzner
Released in Debian, on experimental, amanda-3.4.2
Hi, I am announcing that I have released in Debian a new amanda package, in experimental. Was released in experimental because Debian is on freeze and the amanda 3.4.2 does not in one of my configs. Expect some reports about problems in this list. I would like to thank you Nathan Stratton Treadway and Charles Curley for beta testing my amanda package. You made my life easier. Kind regards Jose M Calhariz -- -- A fortuna que eu gasto hoje será uma bagatela amanhã --Sol Kerzner
