Re: amandqa-security.conf

[Olivier]

Thank you, David,

> I have:
> root@jenny:~ # uname -sr
> FreeBSD 11.2-STABLE
> root@jenny:~ # ls -al /usr/local/etc/amanda
> total 40
> drwxr-xr-x   4 rootamanda 7 May 26 00:54 .
> drwxr-xr-x  53 rootwheel120 Jun 24 08:28 ..
> -rw---   1 amanda  amanda   102 Apr 28 08:05 .amandahosts
> drwxrwx---   2 rootamanda 9 Jun 25 01:27 GipNetDaily01
> -rw-r--r--   1 rootwheel   2045 May 26 00:54 amanda-security.conf
> -rw-r--r--   1 rootwheel   2044 May 29  2017 security.conf
> drwxrwx---   2 rootamanda 4 Oct 18  2014 template.d
> root@jenny:~ #

I have tried that, but it did not work for me, because the directory
/usr/local/etc/amanda also contains all the tapelist files and it has to
be owned by the used amanda in order for amdump/amtaper to update these
files.

My .amandahosts file is located in ~amanda which is different from
/usr/local/etc/amanda,

> It's been running this way for years.

Idem. But my implementation may not completely follow the cannons from
FreeBSD since I had installed it by hand long time before trying to use
the ports.

Best regards,

Olivier

>
> Quoting Olivier :
>
>> Hi,
>>
>> Running amanda 3.3.9 on FreeBSD, I just came to an issue.
>>
>> FreeBSD packaging system places all the configuration files into
>> /usr/local/etc instead of /etc. In the case of Amanda, it is
>> /usr/local/etc/amanda.
>>
>> Amanda client expects the file amanda-security.conf in
>> /usr/local/etc/amanda, with the directory owned by root.
>>
>> Amanda server expects that the directory /usr/local/etc/amanda is owned
>> by amanda so the process can do various file manipulations like updating
>> tapelist files.
>>
>> How can I reconciliate both? Or rather have a different directory used
>> by Amanda client?
>>
>> Thanks in advance,
>>
>> Olivier
>> --

-- 

Re: amandqa-security.conf

[David Nevel]

I have:
root@jenny:~ # uname -sr
FreeBSD 11.2-STABLE
root@jenny:~ # ls -al /usr/local/etc/amanda
total 40
drwxr-xr-x   4 rootamanda 7 May 26 00:54 .
drwxr-xr-x  53 rootwheel120 Jun 24 08:28 ..
-rw---   1 amanda  amanda   102 Apr 28 08:05 .amandahosts
drwxrwx---   2 rootamanda 9 Jun 25 01:27 GipNetDaily01
-rw-r--r--   1 rootwheel   2045 May 26 00:54 amanda-security.conf
-rw-r--r--   1 rootwheel   2044 May 29  2017 security.conf
drwxrwx---   2 rootamanda 4 Oct 18  2014 template.d
root@jenny:~ #

It's been running this way for years.

Quoting Olivier :


Hi,

Running amanda 3.3.9 on FreeBSD, I just came to an issue.

FreeBSD packaging system places all the configuration files into
/usr/local/etc instead of /etc. In the case of Amanda, it is
/usr/local/etc/amanda.

Amanda client expects the file amanda-security.conf in
/usr/local/etc/amanda, with the directory owned by root.

Amanda server expects that the directory /usr/local/etc/amanda is owned
by amanda so the process can do various file manipulations like updating
tapelist files.

How can I reconciliate both? Or rather have a different directory used
by Amanda client?

Thanks in advance,

Olivier
--



--
Beware the happy man with power tools.

Re: amandqa-security.conf

[Gene Heskett]

On Wednesday 27 June 2018 01:09:01 Olivier wrote:

> Hi,
>
> Running amanda 3.3.9 on FreeBSD, I just came to an issue.
>
> FreeBSD packaging system places all the configuration files into
> /usr/local/etc instead of /etc. In the case of Amanda, it is
> /usr/local/etc/amanda.
>
> Amanda client expects the file amanda-security.conf in
> /usr/local/etc/amanda, with the directory owned by root.
>
> Amanda server expects that the directory /usr/local/etc/amanda is
> owned by amanda so the process can do various file manipulations like
> updating tapelist files.
>
> How can I reconciliate both? Or rather have a different directory used
> by Amanda client?
>
> Thanks in advance,
>
> Olivier

Here, on linux debian wheezy, FWIW, the /usr/local/etc/amanda directory 
is owned by amanda:disk, but I have 2 amanda-security files, both owned 
by root:root, one beside the amanda directory, and one in it. Differing 
by one byte in length, one has everthing commented, the other leaves off 
a # in front of a line.  This is on this machine, the server. Which one 
it uses, I've not a clue. It Just Works(TM), most of the time.

That directory exists but is empty on all client machines. A bunch of 
wheezy's and one jessie.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

amandqa-security.conf

[Olivier]

Hi,

Running amanda 3.3.9 on FreeBSD, I just came to an issue.

FreeBSD packaging system places all the configuration files into
/usr/local/etc instead of /etc. In the case of Amanda, it is
/usr/local/etc/amanda.

Amanda client expects the file amanda-security.conf in
/usr/local/etc/amanda, with the directory owned by root.

Amanda server expects that the directory /usr/local/etc/amanda is owned
by amanda so the process can do various file manipulations like updating
tapelist files.

How can I reconciliate both? Or rather have a different directory used
by Amanda client?

Thanks in advance,

Olivier
--