Re: directory locations and dumpuser after new install of amanda 2.6.0p1
I recieved the following warnings after adding --with-maxtapeblocksize to my amanda.spec file and issuing the rpmbuild -ba amanda.spec command: WARNINGS: no user specified (--with-user) -- using 'amanda' no group specified (--with-group) -- using 'backup' + --with-index-server=localhost --with-tape-server=localhost --with-user=amandabackup --with-group=disk --with-owner=root --with-fqdn --with-bsd-security --with-bsdtcp-security --with-bsdudp-security --with-ssh-security --with-udpportrange=700,740 --with-tcpportrange=11000,11040 --with-low-tcpportrange=700,710 --with-debugging=/var/log/amanda --with-assertions --disable-installperms /var/tmp/rpm-tmp.59329: line 46: --with-index-server=localhost: command not found error: Bad exit status from /var/tmp/rpm-tmp.59329 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.59329 (%build) I noticed in newer RPM's that amandabackup is the default dumpuser and disk the default group not amanda user and backup group. Should I also add --with-user amandabackup and --with-group disk to the amanda.spec file and re-issue the rpmbuild -ba command? What is current and future direction for the default user and group in zmanda rpms.
Re: directory locations and dumpuser after new install of amanda 2.6.0p1
On Sat, Jul 26, 2008 at 03:56:38PM -0600, Doyle Collings wrote: > If I do not specify --with-maxtapeblocksize when the source is configured in > 2.6.0p1 will the blocksize parameter in tapetype be ignored and the block > size default to 32k? > I don't have definitive information on this, but I think what Dustin means is that the configure option will be obsoleted by a change in the code that places limits the block size. I suspect the default tapeblocksize will continue to be 32K, but there will no longer be an upper limit to the block size. Thus no need for the configure option. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Re: directory locations and dumpuser after new install of amanda 2.6.0p1
If I do not specify --with-maxtapeblocksize when the source is configured in 2.6.0p1 will the blocksize parameter in tapetype be ignored and the block size default to 32k?
Re: directory locations and dumpuser after new install of amanda 2.6.0p1
On Sat, Jul 26, 2008 at 11:08 AM, Doyle Collings <[EMAIL PROTECTED]> wrote: > When you say thay your getting rid of --with-maxtapeblocksize in > Amanda-2.6.1, does that mean I will be able to specify blocksize in my > tapetype definition without it? Is is neccesary now or does it just specify > the maximum blocksize I can use? Is there a source RPM for 64bit SLES? a) yes b) yes, it currently just specifies the maximum size (well, it's kinda complicated, but) c) Source RPMs are architecture-agnostic. To my knowledge, our RPMs will build on SLES10 - x86_64. If you have trouble, post to the list. Dustin -- Storage Software Engineer http://www.zmanda.com
Re: directory locations and dumpuser after new install of amanda 2.6.0p1
When you say thay your getting rid of --with-maxtapeblocksize in Amanda-2.6.1, does that mean I will be able to specify blocksize in my tapetype definition without it? Is is neccesary now or does it just specify the maximum blocksize I can use? Is there a source RPM for 64bit SLES? >>> "Dustin J. Mitchell" <[EMAIL PROTECTED]> 07/26/08 8:33 AM >>> On Sat, Jul 26, 2008 at 2:43 AM, Doyle Collings <[EMAIL PROTECTED]> wrote: > I have decided to clean out my old installations of Amanda 2.46, 2.6.0p1 rpm, > and 2.6.0p1 from source and start fresh. I noticed that the defaults of the > install from source do not match the rpm from zmanda. For example, The link > http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads_page > states that the Amanda commands are in /usr/sbin. Installing from source > puts them in /usr/local/sbin. It appears that installing from source still > puts the amanda user as the default dumpuser and not amandabackup. Bottom > line, I want my install from source directories and default user to matchup > with intended direction of present and future packages. I would use the RPM > provided but I want to configure my installation configure > --with-maxtapeblocksize=N. I also am running the 64 bit version of SLES > 10SP1 and want to compile with the 64 bit code. Your best bet may be to take the source RPM and tweak the .spec file tp specify your --with-maxtapeblocksize, then build your own RPM. FWIW, we're getting rid of --with-maxtapeblocksize in Amanda-2.6.1. Dustin -- Storage Software Engineer http://www.zmanda.com
Re: directory locations and dumpuser after new install of amanda 2.6.0p1
On Sat, Jul 26, 2008 at 2:43 AM, Doyle Collings <[EMAIL PROTECTED]> wrote: > I have decided to clean out my old installations of Amanda 2.46, 2.6.0p1 rpm, > and 2.6.0p1 from source and start fresh. I noticed that the defaults of the > install from source do not match the rpm from zmanda. For example, The link > http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads_page > states that the Amanda commands are in /usr/sbin. Installing from source > puts them in /usr/local/sbin. It appears that installing from source still > puts the amanda user as the default dumpuser and not amandabackup. Bottom > line, I want my install from source directories and default user to matchup > with intended direction of present and future packages. I would use the RPM > provided but I want to configure my installation configure > --with-maxtapeblocksize=N. I also am running the 64 bit version of SLES > 10SP1 and want to compile with the 64 bit code. Your best bet may be to take the source RPM and tweak the .spec file tp specify your --with-maxtapeblocksize, then build your own RPM. FWIW, we're getting rid of --with-maxtapeblocksize in Amanda-2.6.1. Dustin -- Storage Software Engineer http://www.zmanda.com
Re: directory locations and dumpuser after new install of amanda 2.6.0p1
On Saturday 26 July 2008, Doyle Collings wrote: >I have decided to clean out my old installations of Amanda 2.46, 2.6.0p1 > rpm, and 2.6.0p1 from source and start fresh. I noticed that the defaults > of the install from source do not match the rpm from zmanda. For example, > The link > http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads_page > states that the Amanda commands are in /usr/sbin. Installing from source > puts them in /usr/local/sbin. It appears that installing from source still > puts the amanda user as the default dumpuser and not amandabackup. Bottom > line, I want my install from source directories and default user to matchup > with intended direction of present and future packages. I would use the > RPM provided but I want to configure my installation configure > --with-maxtapeblocksize=N. I also am running the 64 bit version of SLES > 10SP1 and want to compile with the 64 bit code. I havn't posted this for a while, but a consistent configuration means tehre are no surprises (generally) when I install a newer version of amanda, and at present I'm tracking the 2.6.0p# series. I use a script I last edited 2 or 3 years ago to do all this. Amanda is the dumpuser, and is a member of the family disk on this machine. Make it executable, and su amanda to run it. #!/bin/sh # since I'm always forgetting to su amanda... if [ `whoami` != 'amanda' ]; then echo echo " Warning " echo "Amanda needs to be configured and built by the user amanda," echo "but must be installed by user root." echo exit 1 fi make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-gnu-ld \ --prefix=/usr/local \ --with-tapedev="FILE:/amandatapes" \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=coyote \ --with-bsdtcp-security --with-amandahosts \ --with-configdir=/usr/local/etc/amanda \ --with-config=Daily \ --with-gnutar=/bin/tar make === You can of course adjust this to suit, I'm using virtual tapes on a separate hard drive, many times more dependable than my previous setup using DDS2 tapes and a seagate changer. The idea is build consistency. I keep a copy in /home/amanda, which is where I build amanda, and copy it into a newly unpacked amanda src directory each time I unpack a new snapshot. Make install is of course done as root. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Reset button? Which reset button? - Linux, the OS that never sleeps. -- Havlik Denis
