Re: NIS+ and AMANDA (Solaris)

2001-07-05 Thread a blob of green gelatin
me box as the config file. (at least that's the conculsion I came to) Just thought I'd share in case anyone else ever has this problem. :) Thanks JRJ for the help, Chris On Thu, 5 Jul 2001, a blob of green gelatin wrote: > Wow, just when I thought the world was my oyster (AMANDA-ly

NIS+ and AMANDA (Solaris)

2001-07-05 Thread a blob of green gelatin
Wow, just when I thought the world was my oyster (AMANDA-ly speaking), I hit a roadblock that I can't stumble past. I have a tapeserver I'll call 'basecamp' with AMANDA up and ready to serve. I have a NIS+ server which needs to be backed up (which I'll call 'xena'). Through much trial and error

Re: Simple Q

2001-07-03 Thread a blob of green gelatin
*Light bulb goes from totally dark to a dim luminescence* I ran amcheck from the client side (I had installed it without the --without-server tag). I guess one doesn't use AMANDA server-side programs on the client when it's supposed to be a client eh? :) Doh. Thanks! Chris On Tue, 3 Jul 20

Simple Q

2001-07-03 Thread a blob of green gelatin
Howdy, I've lost my marbles and need help finding one. :) I installed AMANDA as a client on a machine only I can't use /usr as it has no space. I've chosen just to put it in / (/amanda), but the 'dailies' config is being looked for in /usr/local/etc/amanda/dailies How do I tell AMANDA to look

Re: User Configuration for Amanda

2001-06-29 Thread a blob of green gelatin
For things that you want to keep accessed by certain uids, you can change the group and make it group readable. That's what I had to do to get AMANDA to be able to read my raw devices (partitions) for backing up. You can just create a user called 'amanda' and a group called 'backup'. Make 'bac

Re: Amanda setup information request

2001-06-27 Thread a blob of green gelatin
> Anyways, what I am going to ask is this: > If I have a server that will EVENTUALLY need to backup remote boxes (hence the > amanda). However current it ONLY needs to back up itself. What is the > "proper" way I should be setting this up? DO I have to do a regular install > and THEN a client i

Re: Building one one machine; using on another

2001-06-27 Thread a blob of green gelatin
Yeah, it should be, but I think that this machine had just the basics installed on it, and then the previous admin went through and got rid of things deemed unworthy. ;( After reading your other reply and JRJ's great reply, I think I'm going to take the situation by the scruff of the neck and

Re: Building one one machine; using on another

2001-06-27 Thread a blob of green gelatin
On Tue, 26 Jun 2001, John R. Jackson wrote: > >Sooo, no go on that road. > > Not too surprising. > > >Btw, I *did* manage to get a copy of 'flex' available to the 2.6 box (via > >NFS) and it wasn't able to build. > > > >Are either of you (Olivier/JRJ) interested in the output? > > Sure. Maybe it

Re: Building one one machine; using on another

2001-06-27 Thread a blob of green gelatin
Well here's the results: I configured/'make'd amanda on a 2.8 box with everything I needed (gcc & the Sun forte cc). I did this as a regular user. I 'tar'd it up and ftp'd it over to the 2.6 box. This is what I got (I was root btw): taipei# make install Making install in config make[1]: Ente

Re: Building one one machine; using on another

2001-06-26 Thread a blob of green gelatin
Things like that are the reason I'm here, I believe. He's not here anymore, but I don't like to just go hog-wild over a system I've inherited. I'm unfamiliar with the functionalities of lex/flex so your feedback is good for me. :) Cheers, Chris On Wed, 27 Jun 2001, Olivier Nicole wrote: >

Re: Building one one machine; using on another

2001-06-26 Thread a blob of green gelatin
On Tue, 26 Jun 2001, John R. Jackson wrote: > >this machine *is* prvileged ... > > Sorry. I meant flex (and bison, etc) doesn't need any special privileges, > so can be installed anyplace (like your home directory), at least long > enough to get Amanda built. Nobody even needs to know ... :-).

Re: Building one one machine; using on another

2001-06-26 Thread a blob of green gelatin
On Tue, 26 Jun 2001, John R. Jackson wrote: > >The production tape server machine is running Solaris2.6 and doesn't have > >all of the marbles necessary (well it's missing lex at least) to configure > >the Makefile. At this point, installing lex on the 2.6 box isn't an > >option. > > Why? It's

Building one one machine; using on another

2001-06-25 Thread a blob of green gelatin
Howdy, Now that I got AMANDA working with my Exabyte 220 and Solaris8, I'm moving it to our production side to actually implement it. But, there's a slight hitch which I'm not sure how to get around. The production tape server machine is running Solaris2.6 and doesn't have all of the marbles ne

Re: Exabyte 215M Jukebox control

2001-06-19 Thread a blob of green gelatin
I just got a Exabyte 220 working with Amanda. I am using stctl which took awhile to get working (due to it compiling in 32-bit mode by default), but now it's working as advertised. Two things on stctl configuration: Go into the Makefile and uncomment out the BUILD_64BIT line and Compile stctl

Re: amcheck and stc-changer

2001-06-17 Thread a blob of green gelatin
On Thu, 14 Jun 2001, John R. Jackson wrote: > What's "stc-changer"? I don't see anything in the Amanda sources by > that name. It's part of the STCTL package that works with AMANDA and the hardware to.. (hehe i'm sure you know the rest) > >When I do an 'stc-changer -slot 1' ... > >I get the sl

amcheck and stc-changer

2001-06-13 Thread a blob of green gelatin
Hi all! I was just wrestling with an Exabyte 220, AMANDA, and Solaris8 for the past week, and after successfully installing SCTCL (to interface between AMANDA and the hardware), I tried to see if amcheck would tell me happy news. Instead its' unable to read the status from stc-changer. After do