Further investigation results
Hi John,
FYI and also for others.
In Solaris 8 the raw devices are set to
crw--- root sys .
ufsdump does a check on the real user id and will not let you at the raw
device if you are not really root even though the link from the /dev
directory is
In Solaris 8 the raw devices are set to
crw--- root sys .
Actually, in all versions of Solaris (and many other OS's).
ufsdump does a check on the real user id and will not let you at the raw
device if you are not really root even though the link from the /dev
directory is setuid. ...
Hi Folks,
I am slowly working my way through the software and now have amanda busy
reusing tapes etc. I am getting a small problem with a queue failing
without really telling me why. The response from Amanda (email) is as
follows
These dumps were to tape INC001.
The next tape Amanda expects to
lagoon.ind /usr/local lev 0 FAILED [disk /usr/local offline on
lagoon.ind.tansu.com.au?]
You should always use "amcheck" first. It often reports a much better
message than "disk offline". So what does it say?
I can't work out the failure message. The logs don't tell me anything
more than
: lagoon.ind.tansu.com.au: [can not read/write /etc/dumpdates:
Permission denied]
Client check: 1 host checked in 0.328 seconds, 1 problem found
(brought to you by Amanda 2.4.2p1)
~
[amanda@lagoon]% ls -al /etc/dumpdates
-rw-rw-r-- 1 root sys0 Feb 9 14:37 /etc/dumpdates
~
[amanda
... Don't you ever sleep?
I'm beginning to think it's a waste of time :-).
Sorry for appearing dumb but sendsize*debug? What it is?
It's a file in /tmp/amanda on the client. Lots of good stuff going on
in there.
ERROR: lagoon.ind.tansu.com.au: [can not read/write /etc/dumpdates:
Permission
Many thanks John,
Permissions problem. I don't have permissions on the rdsk device. I will
have to check the groups again for amanda.
Thanks and Regards
"John R. Jackson" wrote:
... Don't you ever sleep?
I'm beginning to think it's a waste of time :-).
Sorry for appearing dumb but
John
well the patch didn't seem to do much (the huge one needs autoconf etc
which I don't have). I forced a #define ssize_t int into the top of
amanda.h and things seem to compile and amcheck OK. Just leaves a test
backup and restore to do.
I'll let you know how we get on.
--
Martin Hepworth
John
Still complains at the same place, same error...must be another issue
somewhere
--
Martin Hepworth
Senior Systems Administrator
Solid State Logic Ltd
+44 (0)1865 842300
"John R. Jackson" wrote:
anyway in common-src I get the following error
gcc -DHAVE_CONFIG_H -I. -I. -I../config
-c
alloc.c -o alloc.o
In file included from alloc.c:33:
amanda.h:509: parse error before `areads_dataready'
amanda.h:509: warning: data definition has no type or storage class
*** Error code 1
make: Fatal error: Command failed for target `alloc.lo'
Current working directory /home/sol/martinh/amanda
anyway in common-src I get the following error
gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -g -O2 -c
alloc.c -o alloc.o
In file included from alloc.c:33:
amanda.h:509: parse error before `areads_dataready'
amanda.h:509: warning: data definition has no type or storage class
***
On Feb 20, 2001, Patrick LIN [EMAIL PROTECTED] wrote:
can i know where i can find gnu tar 1.3.19
See docs/INSTALL in 2.4.2p1
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at
I recently upgraded a system and also upgraded amanda also. On the old
system using amanda 2.4.1p1 I had added the -DIGNORE_TAR_ERRORS so that
amanda would not toss a good backup just because of a missing file (that
happens here since I am backing up a mail spool which frequently has files
I will try this. In 2.4.1p1 there was a place in the client-src/Makefile
for AMANDA_FLAGS (I think that was it) where I added the -DIGNORE_TAR_ERRORS
option. Since I could not find that in the client-src/Makefile I assumed it
had disappeared.
On Sat, 17 Feb 2001, John R. Jackson wrote:
I
I recently upgraded a system and also upgraded amanda also. On the old
system using amanda 2.4.1p1 I had added the -DIGNORE_TAR_ERRORS ...
In building 2.4.2p1 I could not find anywhere to include the -D ...
Nothing has changed in the build sequence. You would do this the same
way you did
On Sat, Feb 17, 2001 at 10:03:12AM -0500, Mike Hendrix wrote:
I will try this. In 2.4.1p1 there was a place in the client-src/Makefile
for AMANDA_FLAGS (I think that was it) where I added the -DIGNORE_TAR_ERRORS
option. Since I could not find that in the client-src/Makefile I assumed it
had
On Feb 17, 2001, Mike Hendrix [EMAIL PROTECTED] wrote:
I recently upgraded a system and also upgraded amanda also. On the old
system using amanda 2.4.1p1 I had added the -DIGNORE_TAR_ERRORS so that
amanda would not toss a good backup just because of a missing file
Instead of ignoring all
The Amanda core team is pleased to announce the release of Amanda
2.4.2p1. It is a bugfixe release.
It can be dowloaded from http://www.amanda.org/
Here's a list of the changes for release 2.4.2p1 (from the NEWS file):
Look at the ChangeLog file for more details.
* Bugs fix release
18 matches
Mail list logo
