On Thu, 27 Sep 2001, Robert Dale wrote:
> As long as I don't have to have an account or login to search and browse
> the archives, I'm indifferent. Otherwise, I like Mailman and would suggest to
> move the list/archives to sf.net.
I agree that there are problems with the amanda lists as they a
On Thu, 27 Sep 2001, Jon LaBadie wrote:
> So, the questions are;
>
> Do we want the list archived at yahoo?
>
> If so, who can/will add the "listsaver-of"
> addresses to the lists?
>
As long as I don't have to have an account or login to search and browse
the archives, I'm indiff
As many know, the archives at yahoogroups for this
list and the amanda-hackers list are not current.
I could not find an appropriate email address at
yahoogroups to ask about this but I finally got
through to the right person(s).
I sent it to "abuse" with a big "I APOLOGIZE".
The following is t
On Thu, 27 Sep 2001 [EMAIL PROTECTED] wrote:
> I mentioned to Margaret that Amanda uses inetd.conf, and since
> FRH 7.1.1 uses xinetd.conf, I didn't think we could upgrade our Linux
> installation without breaking Amanda.
you just need to build an xinetd.d file for amanda: I'm using:
- - - - -
On Thu, 27 Sep 2001 at 2:01pm, Lalo Castro wrote
> The client sends the reply packet, but the server doesn't seem to
> receive them. The server, when called on it's own backup, recieves the
> packet fine, which makes me think that the xinetd.conf and services
> files are as they should be (t
Hi,
I'm running amanda 2.4.2p2 on two RH Linux 7.1 machines, client and
server. I am having problems with the "selfcheck timed out" error. An
amcheck for the servers own backup returns success, but when the server
begins the client amcheck, the host times out. The client receives the
reques
Mike lemoine wrote:
Actually, I had it backwards. In the xinetd.conf I had amandad{ user = root} and
that worked. The
--with-user=root, was something I tried a few hours ago. I'm a little dizzy from
staring at amanda so much trying to
solve a different problem. Sorry.
> Well, assuming
> What amanda proceses are running ? Just ufsdumps ?
Well, here's an excerpt from top as I run my latest test:
| load averages: 0.03, 0.07, 0.19 14:48:19
| 56 processes: 54 sleeping, 1 stopped, 1 on cpu
| CPU states: 99.2% idle, 0.6% user, 0.2% kernel,
** Gael Lepetit <[EMAIL PROTECTED]> on Wed, 26 Sep 2001 12:28:23 +0200
** in [How to "nice" an Amanda dump/compression] writes:
Gael> Hi,
Hello!
Gael> How to "nice -5" automagically an Amanda gzip/dump ??
On our FreeBSD systems, I do a login class (in /etc/login.conf) called
"backup" and set t
* Michael S. Peek <[EMAIL PROTECTED]> (Thu, Sep 27, 2001 at 11:36:11AM -0400)
> Hello all,
> I've been using amanda for, well, years now, and I have never run accross this
> problem before. I have one brand new host that is taking *WAY* too long to
> back up. Here's the skinny:
[8<]
> The ne
> I sat down and did some figuring. Dump has been running on this host for
> 18:21:27, and has only gotten 1.24% completed by sending 8992k of the dump back
> to the tape host. According to a little math, I figure that it's moving about
> 139 bytes/sec, and has about 61 days 16:26:36 left until
Well, assuming that one doesn't want amanda running as root, has anyone else had and
solved
this problem?
On Wed, 26 Sep 2001, Lalo Castro wrote:
> I had the same problem, but reconfigured it with ./configure --with-user=root, and
>that cleared it up.
>
> Mike lemoine wrote:
>
> > I've seen
Hello all,
I've been using amanda for, well, years now, and I have never run accross this
problem before. I have one brand new host that is taking *WAY* too long to
back up. Here's the skinny:
It's a Sun SPARC Ultra-5 running Solaris-2.7 with amanda 2.4.2p2. There are a
total of six machines
jeremy wadsack writes:
>It's run by inetd (or xinetd) so it is started anytime a new
>connection comes in. If it doesn't get anything from the connection it
>stops. Otherwise, you could end up filling up the memory / process
>space with amandad instances by nudging the port and then not
>connectin
Dave Brooks ([EMAIL PROTECTED]):
>>So you started amandad, which started listening for requests, didn't hear
>>any within 30 seconds, and so quit. That's normal.
>>
> The daemon terminates itself if it doesnt receive any requests within 30
> seconds? So you have to restart it? Surely that ca
Amanda Users:
I have been really lucky so far with using Amanda for the past 3 years
without any problems, but I recently ran into a stumper that I cannot figure
out. I just built a new Backup server on a RedHat 7.1 machine in which I
back up a mixed environment of Linux, Tru64 UNIX, Solaris, IRI
Ok, I'm getting the selfcheck time out message for two of my 12 amanda
clients. They all have exactly the same configuration, as far as I can
tell. I have installed the latest amanda source on each client system,
using the same config settings. I have checked, double checked and
triple checked al
17 matches
Mail list logo
