Re: Still having problems with cygwin...
Should I be sending this to amanda-hackers? Thanks, Ricky
Still having problems with cygwin...
Hi! Since my last request for help, I've updated to the most recent code base (2.4.4p3) and I've applied a patch that was posted to amanda-hackers last year which commented out a number of 'aclose' calls. Neither one solved the problem. Does anyone have any other suggestions? Should I post this to amanda-hackers instead? The problem: I'm trying to back up a Windows 2000 box using cygwin. Cygwin version is 1.5.10. Amanda version is 2.4.4p3 (with and without the patch posted by Brian White on 21 April 2003 to amanda-hackers). Server version is 2.4.4. amcheck reports no errors. When the backup actually runs, the report returns: FAILURE AND STRANGE DUMP SUMMARY: myrddin.mg /cygdrive/c lev 0 FAILED [bad CONNECT response] and /-- myrddin.mg /cygdrive/c lev 0 FAILED [bad CONNECT response] \ Looking in the debug files, I have selfcheck and sendsize both working correctly, but sendbackup fails. The amandad log has: amandad: time 0.002: got packet: Amanda 2.4 REQ HANDLE 000-80E10508 SEQ 1089855002 SECURITY USER amanda SERVICE sendbackup OPTIONS features=feff9ffe0f;hostname=myrddin.mgh.harvard.edu; GNUTAR /cygdrive/c 0 1970:1:1:0:0:0 OPTIONS |;auth=bsd;srvcomp-fast;index;include-list=.amanda-gtar-includes; amandad: time 0.003: sending ack: Amanda 2.4 ACK HANDLE 000-80E10508 SEQ 1089855002 amandad: time 0.020: bsd security: remote host einstein.mgh.harvard.edu user amanda local user SYSTEM amandad: time 0.021: amandahosts security check passed amandad: time 0.021: running service /usr/local/amanda/libexec/sendbackup sendbackup: ERROR [sendbackup: could not create data socket: Operation not permitted] while the sendbackup log has: sendbackup: debug 1 pid 1496 ruid 18 euid 18: start at Wed Jul 14 23:15:13 2004 /usr/local/amanda/libexec/sendbackup: version 2.4.4p3 parsed request as: program `GNUTAR' disk `/cygdrive/c' device `/cygdrive/c' level 0 since 1970:1:1:0:0:0 options `|;auth=bsd;srvcomp-fast;index;include-list=.amanda-gtar-includes;' sendbackup: stream_server: socket() failed: Operation not permitted sendbackup: time 0.004: ERROR [sendbackup: could not create data socket: Operation not permitted] sendbackup: time 0.005: pid 1496 finish time Wed Jul 14 23:15:13 2004 Unfortunately, my hacking skills aren't sufficient to allow me to track down where/why this is happening. Is there some permissions step that I missed? I should note that on an older version of cygwin (1.3.20) I have no problems... Thanks for any suggestions, Ricky Morse
Cygwin question...
Hi! I have a number of Win2K machines I'm backing up using cygwin-based Amanda. Most of them work just great, however I haven't added a new machine for several months. Just a few days ago, I added a new machine, using the already-compiled binaries from the other machines, and I'm having a problem... First, this is amanda 2.4.4 (I haven't done any upgrades for a while, so there may be newer versions out). It was compiled on Cygwin 1.3.20. I'm trying to run it on Cygwin 1.5.10. I realize that this might be the problem, but I'd rather not recompile it if I can, as it was a pain to get compiled correctly. It passes amcheck just fine. However, when it actually tries to back up, I get the following errors in the log files: in amandad.*.debug (this being the third amadad.debug file from the evening): amandad: time 0.020: bsd security: remote host xxx.xxx.xxx.edu user amanda local user SYSTEM amandad: time 0.020: amandahosts security check passed amandad: time 0.020: running service /usr/local/amanda/libexec/sendbackup ERROR [sendbackup: could not create data socket: Operation not permitted] in sendbackup.*.debug: sendbackup: debug 1 pid 1344 ruid 18 euid 18: start at Wed Jul 7 23:24:05 2004 /usr/local/amanda/libexec/sendbackup: version 2.4.4 parsed request as: program `GNUTAR' disk `/cygdrive/c' device `/cygdrive/c' level 0 since 1970:1:1:0:0:0 options `|;auth=bsd;srvcomp-fast;index;include-list=.amanda-gtar-includes;' sendbackup: stream_server: socket() failed: Operation not permitted sendbackup: time 0.005: ERROR [sendbackup: could not create data socket: Operation not permitted] sendbackup: time 0.005: pid 1344 finish time Wed Jul 7 23:24:05 2004 Does anyone have any ideas what might be causing this? A google search revealed nothing... Thanks, Ricky
Re: Bad tape or worse news?
On Wednesday, December 3, 2003, at 04:50 AM, C.Scheeder wrote: H, i'm no free-bsd guru, but Jack Twilley schrieb: Here's the uname output: FreeBSD duchess.twilley.org 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sat Nov 8 00:40:54 PST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DUCHESS i386 I'm running amanda out of ports: amanda-client-2.4.4_2,1 The Advanced Maryland Automatic Network Disk Archiver (clie amanda-server-2.4.4_4,1 The Advanced Maryland Automatic Network Disk Archiver (serv I've started to get the following message in my nightly emails: *** A TAPE ERROR OCCURRED: [writing label: short write]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: twilley009. This is showing up in my messages file: Dec 3 01:08:19 duchess kernel: (sa0:ahc0:0:6:0): WRITE FILEMARKS. CDB: 10 0 0 0 2 0 Dec 3 01:08:19 duchess kernel: (sa0:ahc0:0:6:0): CAM Status: SCSI Status Error Dec 3 01:08:19 duchess kernel: (sa0:ahc0:0:6:0): SCSI Status: Check Condition Dec 3 01:08:19 duchess kernel: (sa0:ahc0:0:6:0): DATA PROTECT asc:27,0 Dec 3 01:08:19 duchess kernel: (sa0:ahc0:0:6:0): Write protected is it possible your tape is physical write-protected? Christoph Also, check to make sure that the tape is rewound. Make sure the tape is properly amlabeled. How much stuff are you trying to put onto the tape? I often get weird error messages when I run out of space. Ricky
Re: Memory requirements for Amanda Server
On Monday, November 24, 2003, at 01:04 PM, Tom Brown wrote: We are building an amanda backup server and have a question regarding memory requirements. My guess is that Amanda is more processor intensive than memory intensive. Is this correct? For a dedicated backup server that won't be doing much of anything else, is 512MB of memory enough? i have such a beast running on RedHat with 256 meg of RAM and its fine My amanda backup server is a pentium 90 with 32M of ram, running FreeBSD 4.9. Seems to work no problem (admittedly, I only have about 30-40 disk-list entries, writing to DDS3) Ricky
Re: Pornography
On Thursday, March 20, 2003, at 03:42 PM, Scott Mcdermott wrote: Marty Shannon, RHCE on Thu 20/03 13:50 -0500: *All* lists *I'm* on -- with the exception of this one -- do not permit any access by non-subscribers (except to subscribe, of course). Agreed. This is standard practice on most lists and cuts down radically on direct spam to the list itself. There is no reason someone should not want to subscribe to the list to post. It doesn't stifle openness either...not sure what argument there is for that. No one is preventing a subscriber from posting or delaying his post. And in most cases the subscription process takes less than a minute. So, I just wanted to chime in: freebsd is another list that doesn't require subscription to send a message. Why? This allows you to say if you have any questions, please email [EMAIL PROTECTED]. You don't have to subscribe, you don't have to know you're getting to a list, etc. Several technical lists do things this way. Now, is this desired is another question. Do we want to make AMANDA approachable to all users? Or should we look only for those admins who have the technical knowledge to subscribe to a mailing list, and understand the implications. I don't know... FWIW, I prefer to let users take care of filtering, and make a resource available, but that make be too idealistic a point of view for the modern world... Ricky
Re: Dumping mounted windows partitions?
On Monday, March 17, 2003, at 11:20 AM, Andreas Hallmann wrote: Hello, I'm dumping 2 windows partitions via gnutar on an amanda 2.4.3 system. Curiously even a level 1 dump has same size as a full dump. Is this a 'normal' , due to some 'shit' in those W98SE partitions? Dumping reiserfs-partitions via gnutar work perfectly and as expected. Any hints how to backup a linux box, with two W98-Partitions the right way? My understanding is that the FAT/FAT32 file systems don't track the information that allows tar to determine if the file has been altered since the last backup. Hence, as far as tar is concerned, every file has been changed. So it does a complete backup. You might be able to fix this by changing the filesystem to NTFS, but in that case, you can't run Win98... HTH, Ricky
Re: hosts timing out on amdump but not amcheck
Regarding the time outs, look in the logs on the client, for sendsize*debug (I think) -- see how long it takes to get the estimate for the various drives. Then, check to see that your etimeout is large enough... HTH, Ricky On Friday, March 7, 2003, at 12:20 PM, justin m. clayton wrote: Thanks for the help. Unfortunately, this has not proved to be the solution to my problem. Suddenly, however, one of the machines (still on autoneg, btw) began working, without any warning or me touching it. All others are still timing out on amdump (though amcheck still works). --Justin On Thu, 13 Feb 2003, Amanda Admin wrote: Justin, This sounds like the symptoms others on the amanda list have attributed to half/full duplex network interface and/or switch problems. I seem to recall a posting just recently saying that (the built-in eth interface on ??) Solaris had a particular affinity towards incorrect duplex detection. Maybe a search of the archives on this topic wwill turn up some details. Doug -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of justin m. clayton Sent: Thursday, February 13, 2003 2:37 PM To: Joshua Baker-LePain Cc: [EMAIL PROTECTED] Subject: Re: hosts timing out on amdump but not amcheck On Thu, 13 Feb 2003, Joshua Baker-LePain wrote: On Thu, 13 Feb 2003 at 9:15am, justin m. clayton wrote First of all, thanks to all who helped me track down my NAK problems from last week. Having fixed that, all backup hosts pass amcheck with flying colors. However, when it comes time for the amdump, my log report claims Request to host timed out when I return the following morning. However, if I run amcheck again, no hosts report problems. This has been going on for a number of days now. I am getting Read error at byte 0...:Bad file number on some hosts (via /tmp/amanda/sendsize.*), and some are reporting amandad: dgram_recv: timeout after 10 seconds amandad: waiting for ack: timeout, retrying (via /tmp/amanda/amandad.*). Strangely, though, the symptom is the same for all machines. What OS/distro? Are there firewalls in the way? The clients are Solaris 8, the server is stable Debian linux, both using 2.4.2p2. No firewalls in the way. This configuration has worked in the past. Justin Clayton VLSI Research System Administrator University of Washington Electrical Engineering Dept [EMAIL PROTECTED] 206/543.2523 EE/CSE 307E Justin Clayton VLSI Research System Administrator University of Washington Electrical Engineering Dept [EMAIL PROTECTED] 206/543.2523 EE/CSE 307E
Wrapping amandad.exe on Cygwin
Hi! I'd like to write a wrapper script for amandad.exe on Cygwin. I want to make sure that all the log files are made readable by the group once amandad is finished. My issue is that I don't quite know how to ensure that amandad gets passed all the proper parameters. Would the following work if placed in inetd.conf in place of amandad.exe? - #!/bin/sh # call amanda /usr/local/amanda/libexec/amandad.exe $@ cd /tmp/amanda chmod g+r * -- Thanks, Ricky
Re: Amanda 2.4.4 + Cygwin = loss of hair...
On Wednesday, March 5, 2003, at 10:01 AM, Steve Loughran wrote: Hi all [snip] I followed the HOWTO-CYGWIN.html doc to the letter, got inetd running from services on XP Pro, but running amcheck on the XP/Cygwin host on the tape server keeps spitting out WARNING: hostname: selfcheck request timed out. Host Down if I run inetd -d from Cygwin bash shell, i see amandad getting started,stopped,started,stopped, over and over again Hi! I have it on Win2K -- not XP. However, in my experience, the inetd -d option doesn't do anything for you -- all that it does is allow you to see that something is, indeed, asking for amanda. Does it work if you run it as a service? Ricky
Re: Problem with compression?
On Monday, February 24, 2003, at 01:03 PM, John Oliver wrote: On Fri, Feb 21, 2003 at 09:10:35PM -0500, Jon LaBadie wrote: On Fri, Feb 21, 2003 at 03:49:32PM -0800, John Oliver wrote: On Fri, Feb 21, 2003 at 06:14:37PM -0500, Gene Heskett wrote: Throw in that marketing is usually a bit optimistic in saying its a 20 gigger without compression, and that always needs a fudge factor when actually estimating, and it likely this will happen. But fudging by 100%? I don't buy that... :-) You don't have to. Gene was only talking about a few percent. No... if my tape is theoretically capable of 20GB uncompressed and 40GB compressed, and after compression amanda can only fit 20GB on it, that would hypothetically demonstrate a 10GB un-compressed capacity. Or, half of what it's actually doing. I do not believe Quantum sells a 10/20 tape drive as a 20/40 I'm sure there *is* some fudging going on, but not, like I said, 100%. I'm apparently loosing about half of the capacity of my tapes, and I'm puzzled why I'm the only one who sees a problem with that... :-) U if you are using server compression, then you (hopefully) have hardware compression turned off. If not, then you're wasting space. However, if you have hardware compression turned off, then the tape itself will store 20Gigs. Even if you have hardware compression turned on, the likelihood that you will be able to actually get 40Gigs of data onto it is vanishingly small. So, you have a tape that holds 20Gigs. Now, Amanda is compressing the data on the server. So, you have two figures -- the amount of data that Amanda receives, uncompressed, and the amount that Amanda writes out to the tape, compressed. Because there is no hardware compression enabled (and mixing software and hardware compression is _bad_), the tape drive will only write 20Gigs of data. The 20Gigs that you see Amanda writing to tape is the 20Gigs that the tape will hold. This happens to be already compressed data, but the tape knows nothing about that. Now, from what I remember, the problem is that you manage to write about 9Gigs of (already compressed, uncompressed it was closer to 14-19 gigs -- I'm not looking at the report right now) data out to the tape. This leaves another 11-odd. The next dump it tried to write to disk didn't compress at all well -- ie, it was something like 12Gigs of data, that even _after_ being compressed, was still something like 12Gigs. So, Amanda tries to write out 12Gigs to an 11Gig space, and fails. Note that, had it succeeded, the uncompressed data being stored on tape would have been close to 30Gigs -- the ~12Gigs of the last entry, plus the uncompressed ~15-19 gigs of the previous entries. HTH, Ricky
Re: problem with cygwin and amanda2.4.4b1
On Friday, February 21, 2003, at 09:16 AM, [EMAIL PROTECTED] wrote: Hello I'm trying to setup amanda2.4.4b1 on a win2000 machine with cygwin. I followed the instruction in the HOWTO for cygwin but have the following problem. i run /usr/sbin/inetd -d on the win2000 machine I run amcheck -c testdisk on my server on my 2000 machine i got the follwoing messages someone wants amanda +closing from 16 848 execl /usr/local/libexec/amandad 848 reaped, status 0x100 restored amanda, fd 16 Hi! I got these exact same messages (modulo a few numbers). One possibility is that you didn't use tabs in all the correct places in inetd.conf? Also, try seeing how it works if you have inetd set as a service. You can add it as a service with /usr/sbin/inetd --install-as-service, and you can then uninstall it with /usr/sbin/inetd --remove-as-service. I found that the -d option didn't let it work, while it did when running as a service... Ricky
Re: Problem with using include list on 2.4.3-FreeBSD server with 2.4.4b1-Cygwin client
On Tuesday, February 18, 2003, at 09:49 PM, Jean-Louis Martineau wrote: On Tue, Feb 18, 2003 at 12:16:16PM -0500, Richard Morse wrote: Apparently, add_include only iterates over the directories at the root of the drive (which makes sense), but therefore, it won't find anything that matches this include: it never checks any deeper into the hierarchy than one level, so when it iterates over Document and Settings, it doesn't match, because Documents and Settings doesn't match the regex Documents and Settings/jad47. I sent a patch for that on amanda-users (6 Jan 2003) but nobody has confirmed that it worked so it was never commited to cvs. The patch is included if you want to try it. Hi! I applied the patch to the 20030212 snapshot of 2.4.4b1. Last night, I used it to back up a client that wasn't doing includes or excludes, just to make sure it didn't mess anything up. Tonight I will run it on a client with both include and exclude files. I'll let you know how it turns out... Ricky
Re: Re-registering?
On Tuesday, February 18, 2003, at 09:58 AM, Potts, Ross A. wrote: Has anyone else already on the list gotten the message that Someone (possibly you) has requested that your email address be added? It is dated today. From the message, it looks as though someone tried to register the amanda-users list to the amanda-users list. I think that this was someone who made a mistake while registering -- they typed the email address of the list, rather than their own. You should ignore this message (unless the list-owner says otherwise). HTH, Ricky Morse
Re: Problem with using include list on 2.4.3-FreeBSD server with 2.4.4b1-Cygwin client
Hi! I realize that it's bad form to follow-up to yourself, but nobody else seems to be, so... On Friday, February 14, 2003, at 11:26 AM, Richard Morse wrote: Hi! I have a 2.4.4b1 client, compiled on Cygwin. I'd like to use the include list feature, so I upgraded my server from 2.4.2p2 to 2.4.3. I have another cygwin client that works, without using the include list feature. When I run amcheck, I get back the error [include must be at least 3 character long: ] and [No incude for /cygdrive/c] from the host which I'm trying to use the include list on. I did let this host run one night as backup, and it generated 10 bytes of data for the tape, which is a problem, as this was a new disk, and there's more than 10 bytes of data to be backed up. As it turns out, the two error messages are coming from different sources. The first one ([include must be at least 3 character long: ] is because there is [was] a blank line at the end of the include file. I usually put one extra newline at the end of a file so that I can easily add things to the end, and for aesthetic reasons. Although this isn't really a bug, blank lines should probably be skipped when reading the file. The second error is more worrisome to me. In my .amanda-gtar-includes file, I had the line: ./Documents and Settings/jad47 Apparently, add_include only iterates over the directories at the root of the drive (which makes sense), but therefore, it won't find anything that matches this include: it never checks any deeper into the hierarchy than one level, so when it iterates over Document and Settings, it doesn't match, because Documents and Settings doesn't match the regex Documents and Settings/jad47. The thing is, I don't want to back up all the data in Documents and Settings, just the stuff in the user folder. However, I want to back up other stuff that's at the root level (ie, at /cygdrive/c), so I don't really want to make my disklist entry be /cygdrive/c/docume~1, and have to put another entry for /cygdrive/c. Is there any solution? (Well, I know that there probably isn't in this version, but is it possible to make the add_include handle directories several levels deep?) Also, is it possible to pass both include _and_ exclude lists to tar? So I could tell it to back up ./Documents and Settings, but exclude ./Documents and Settings/Administrator? (Which, actually, would be useful just in general so I can exclude browser caches...) Thanks, Ricky Morse
Problem with using include list on 2.4.3-FreeBSD server with 2.4.4b1-Cygwin client
Hi! I have a 2.4.4b1 client, compiled on Cygwin. I'd like to use the
include list feature, so I upgraded my server from 2.4.2p2 to 2.4.3.
I have another cygwin client that works, without using the include list
feature.
When I run amcheck, I get back the error [include must be at least 3
character long: ] and [No incude for /cygdrive/c] from the host
which I'm trying to use the include list on. I did let this host run
one night as backup, and it generated 10 bytes of data for the tape,
which is a problem, as this was a new disk, and there's more than 10
bytes of data to be backed up.
The device is specified in disklist as:
w0084451.mgh.harvard.edu /cygdrive/c std-tar-include
I have the following dumptypes defined (I've left out the non-relevant
ones):
define dumptype global {
comment Global defs
index yes
}
define dumptype std-tar {
global
program GNUTAR
compress server fast
}
define dumptype std-tar-include {
std-tar
include list .amanda-gtar-includes
}
On w0084451, I have the following in c:\.amanda-gtar-includes:
./Documents and Settings/jad47
which is the name of the folder that I want to backup (I'm just trying
to backup user data). If, in cygwin, I type less
/cygdrive/c/.amanda-gtar-includes, this is the file that I get (there
is a blank line at the end of it, and I don't know offhand what the
line endings are, but I can find that out if need be).
There are files in /tmp/amanda which are selfcheck.*.include, which I
would like to look at, but they are owned by SYSTEM, with permissions
600, so I can't see them. Is there any way to get a program to run as
SYSTEM so that I can chmod go+r the debug files?
Does anyone know what might be causing the error messages? I've tried
looking at the source, but my C is _very_ rusty...
Thanks muchly,
Ricky Morse
Re: 2.4.4b1 cygwin client and specifying DLEs with spaces...
On Tuesday, February 11, 2003, at 10:42 PM, John R. Jackson wrote:
.. /cygdrive/c {
comp-tar
include list include-1
}
and in /cygdrive/c/include-1:
./Documents and Settings/myuserfolder
Note that you cannot use include file as that passes the thing to
include across to the client in the Amanda protocol and falls prey to
the protocol problems.
Hmmm when I do this, I get include must be at least 3 character
long: and No include for /cygdrive/c. I verified that I'm doing
include list, not include file. Does it matter that I also have an
exclude list defined for the dump type (because my exclude list falls
through several layers...)?
Thanks,
Ricky
Re: AMANDA and the Windows world
On Wednesday, February 12, 2003, at 09:29 AM, Joshua Baker-LePain wrote: The cygwin client is pretty new and thus less tested. I'd just like to say that so far, it seems to work. I still need to do a test restore, and I don't know about ACLs, but the signs are that things are working correctly, given the amount of data that gets backed up every night I'm going to do a test restore today, and probably add another two clients, to get better testing results... Ricky
Re: AMANDA and the Windows world
On Wednesday, February 12, 2003, at 12:23 PM, Jon LaBadie wrote: No need to wait. The backup is being done by tar on the cygwin client. If it saves ACL info and resets them correctly, then amanda will. Do a test on your cygwin client just by creating and extracting a tar archive. So, I tried this, and you are correct -- the ACLs aren't saved by tar (I guess I was hoping that the cygwin tar would be able to work with this... perhaps in future versions? However, I also did do my test restore. It worked, although the permissions were, of course, incorrect. So, if you're like me, and are really only interested in backing up user data -- not programs, or system files, it'll probably work correctly. I'm still looking around to see if there are cygwin based (or, at least, command line based that can write to STDOUT, as I imagine that's all that's needed) backup programs with do handle acls... Ricky
Re: 2.4.4b1 cygwin client and specifying DLEs with spaces...
On Tuesday, February 11, 2003, at 10:42 PM, John R. Jackson wrote:
If so, then you should be able to use an include clause and put the
sub-folders to include within some major top level area, and that file
is only processed by GNU tar and (I think) may contain spaces.
So the DLE might be:
.. /cygdrive/c {
comp-tar
include list include-1
}
and in /cygdrive/c/include-1:
./Documents and Settings/myuserfolder
Note that you cannot use include file as that passes the thing to
include across to the client in the Amanda protocol and falls prey to
the protocol problems.
H at this point, I have a 2.4.2p2 server, which doesn't mention
the include list in the manpage. Will it still work? Or would I
have to upgrade to 2.4.4b1 for the server as well? In which case,
would I have to upgrade the other 2.4.2p2 clients?
Cause if it will just work, then life is great! I just am not ready to
upgrade everything, in part because getting the compiler to work on the
Solaris 2.6 boxes is a big pain...
Thanks,
Ricky
Re: AMANDA and the Windows world
On Wednesday, February 12, 2003, at 02:59 PM, Joshua Baker-LePain wrote: Actually, getting amanda to use some other program (i.e. not GNUtar or *dump) for backups is not exactly trivial. The (long in coming) DUMPER-API is supposed to fix that, but is still a ways off (probably, I'm not really sure). Suppose that I can get WinZip to write it's output to standard out. Also, supposing that I use the include list to pass it a set of directories to zip. Could I write a wrapper to replace runtar that would work? I suppose this might create a problem with estimates, and possibly incrementals as well. But Winzip _might_ support that -- I need to look... I'll get back to y'all with what I find... Ricky
Re: 2.4.4b1 cygwin client and specifying DLEs with spaces...
On Wednesday, February 12, 2003, at 04:57 PM, Joshua Baker-LePain wrote: On Wed, 12 Feb 2003 at 3:47pm, Richard Morse wrote H at this point, I have a 2.4.2p2 server, which doesn't mention the include list in the manpage. Will it still work? Or would I have to upgrade to 2.4.4b1 for the server as well? In which case, would I have to upgrade the other 2.4.2p2 clients? To use include lists you'll need 2.4.3 (or greater) on the server and any clients with disks you want to use the include feature on. Can I just upgrade my server to 2.4.3? Will it work with the 2.4.2p2 clients? Ricky
2.4.4b1 cygwin client and specifying DLEs with spaces...
Hi! This is probably a really easily answered question, but I'm not having any luck finding it (probably going blind)... I've got the 2.4.4b1 client set up on a cygwin machine. The backup is going well, but in order to create a DLE, I had to do some aliasing. Is there a way to specify a DLE like: X.. /cygdrive/c/Documents and Settings/myuserfolder comp-tar That is, include paths with spaces? Alternatively, in the .amanda-gtar-excludes file, can I specify directories with spaces? So I can exclude /Program Files? Thanks, Ricky
Re: Configure/Install
On 02/07/2003 10:58 AM, Chris Broadwater [EMAIL PROTECTED] wrote: Hi, I need some help. I was going through the install of Amanda 2.3.4 and during the Configure the process errored out with the following line configure: error: *** --user-USER is missing Any ideas what I missed. I figured this is a minor issue and caused by an oversight on my behalf You forgot to pass the --with-user=USER parameter to ./configure... Either that, or the user that you passed in doesn't yet exist in /etc/passwd. Use adduser/useradd/vipw/whatever-for-your-system to add the user... HTH, Ricky
2.4.4b client with 2.4.2p2 server?
Hi! I'd like to test the 2.4.4b client on a cygwin-enabled win32 machine. However, I have a 2.4.2p2 server, which does everything that I need to do for my unix boxen. Is there any problem using the 2.4.4b client with a 2.4.2p2 server? Thanks muchly, Ricky Morse Richard Morse System Administrator MGH Biostatistics Center 50 Staniford St. Rm 560 [EMAIL PROTECTED]617/724-9830
