Jukka Salmi -- amanda-users (2008-09-10 14:40:29 +0200):
[...]
Hmm, EINTR. I'll try to reproduce this with another version of NetBSD
(trying with 4.0_STABLE ATM) before debugging any further...
It seems that I hit a known problem:
On Thu, 2008-09-11 at 09:27 -0600, John Hein wrote:
John Hein wrote at 07:19 -0600 on Sep 11, 2008:
Taalaibek Ashirov wrote at 10:31 +0300 on Sep 11, 2008:
On Wed, 2008-09-10 at 09:56 -0600, John Hein wrote:
What happens when you compile and run this (as the backup user)?
On Thu, Sep 11, 2008 at 11:53 PM, Olivier Nicole [EMAIL PROTECTED] wrote:
Is there a mechanism in Amanda to ensure that only a single tape
changer process is running at any given time?
No -- and this poses a problem for processes that want to move data
between devices. I'm working on such a
On Fri, Sep 12, 2008 at 7:58 AM, Taalaibek Ashirov
[EMAIL PROTECTED] wrote:
Yes, in the test the problem goes away. Actually, I've installed amanda
from ports. Now I deinstalled amanda and got latest source version from
amandas website, added those lines to amflock(). When I did make it gave
Taalaibek Ashirov wrote at 14:58 +0300 on Sep 12, 2008:
Let me recant, it may be amanda at fault or a combination. If you add
the following to the initialization of 'lock' in the test, does your
problem go away?
lock.l_start = 0;
lock.l_len = 0;
If the short test
Dustin J. Mitchell wrote at 09:40 -0400 on Sep 12, 2008:
creating amflock-test
make: don't know how to make amgpgcrypt. Stop
*** Error code 2
Stop in /root/amanda-2.6.0p2/common-src.
*** Error code 1
Stop in /root/amanda-2.6.0p2.
web#
Amanda requires GNU make now (gmake).
Dustin J. Mitchell wrote at 09:32 -0400 on Sep 12, 2008:
On Thu, Sep 11, 2008 at 11:53 PM, Olivier Nicole [EMAIL PROTECTED] wrote:
Is there a mechanism in Amanda to ensure that only a single tape
changer process is running at any given time?
No -- and this poses a problem for
On Fri, Sep 12, 2008 at 11:28 AM, John Hein [EMAIL PROTECTED] wrote:
I think amanda has required gmake for quite a while, hasn't it?
Quietly, yes -- some GNU extensions snuck in/around 2.5.0 or 2.5.1,
and nobody complained, so when I rewrote the autoconf/automake stuff,
I just went whole-hog to
