Re: Email delivery
Jon LaBadie wrote: On Thu, Oct 27, 2005 at 10:50:26PM -0400, Matt Hyclak wrote: On Fri, Oct 28, 2005 at 04:07:10AM +0200, Lars Bakker enlightened us: Can somebody tell me how Amanda sends email reports? I'm using the Kolab2 server on the same machine that should do the backups but unfortunately I get no reports although the smtp server works fine. Is Amanda using another program for mail delivery? It finds a mail program at compile time. You can find it with grep MAILER /path/to/logfiles/amandad.$DATETIME.debug Filling in the path and date/time appropriately. On my system, it's looking at /usr/bin/Mail. Another way is amgetconf: $ amgetconf DS1 build.mailer /usr/ucb/Mail Yet another way: $ amadmin xx version | grep MAILER -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: problems with label of tape in last slot
Am 27.10.2005 um 10:49 schrieb Paul Bijnens: Stefan Herrmann wrote: yes I do have problems: stefan:/usr/local/amanda/etc/amanda/daily amanda$ amtape daily label daily2 amtape: scanning for tape with label daily2 amtape: slot 3: date Xlabel daily3 (wrong tape) amtape: slot 4: date Xlabel daily4 (wrong tape) amtape: slot 5: date Xlabel daily5 (wrong tape) amtape: slot 6: date Xlabel daily6 (wrong tape) amtape: slot 7: date Xlabel daily7 (wrong tape) amtape: slot expr:: tape_rdlabel: tape open: syntax error: No such file or directory amtape: slot 1: date 20051026 label daily1 (wrong tape) amtape: slot 2: date 20051027 label daily2 (exact label match) amtape: label daily2 is now loaded. the tape in slot 8 (daily8) cant be scanned. so if i want to load daily8 there is no match and I cant load the tape :( Is is there anything different with the last slot? No, nothing different .. same as the other slots What is the output of: $ cd /usr/local/amanda/etc/amanda/daily $ amgetconf tapecycle 8 # at least that what I expect yes, that's the output $ amgetconf tapedev file:/some/directory/slots # use this output in the next cmd stefan:/usr/local/amanda/etc/amanda/daily amanda$ amgetconf tapedev file:/Volumes/amanda1/daily $ ls -la /some/directory/slots/slot[78] ... # any difference between slot 7 and 8??? permissions, filesize etc. stefan:/Volumes/amanda1/daily amanda$ ls -la slot[78] slot7: total 144 drwxr-xr-x 6 amanda unknown204 24 Oct 09:15 . drwxr-x--- 13 amanda unknown442 28 Oct 04:00 .. -rw--- 1 amanda unknown 10 24 Oct 09:15 0-daily7 -rw--- 1 amanda unknown 32768 24 Oct 09:15 0.daily7 -rw--- 1 amanda unknown 10 24 Oct 09:15 1-TAPEEND -rw--- 1 amanda unknown 32768 24 Oct 09:15 1.TAPEEND slot8: total 32409304 drwxr-xr-x 24 amanda unknown 816 25 Oct 05:28 . drwxr-x--- 13 amanda unknown 442 28 Oct 04:00 .. -rw--- 1 amanda unknown 10 25 Oct 04:00 0-daily8 -rw--- 1 amanda unknown32768 25 Oct 04:00 0.daily8 -rw--- 1 amanda unknown 14 25 Oct 04:00 1-stefan.hq.imos.net._.1 -rw--- 1 amanda unknown695926784 25 Oct 04:00 1.stefan.hq.imos.net._.1 -rw--- 1 amanda unknown 14 25 Oct 04:01 2-sulu.hq.imos.net._.1 -rw--- 1 amanda unknown498237440 25 Oct 04:01 2.sulu.hq.imos.net._.1 -rw--- 1 amanda unknown 14 25 Oct 04:04 3-sulu.hq.imos.net._opt2.1 -rw--- 1 amanda unknown397836288 25 Oct 04:01 3.sulu.hq.imos.net._opt2.1 -rw--- 1 amanda unknown 12 25 Oct 04:04 4-ox.hq.imos.net._var.0 -rw--- 1 amanda unknown 3866624 25 Oct 04:04 4.ox.hq.imos.net._var.0 -rw--- 1 amanda unknown 12 25 Oct 04:35 5-sulu.hq.imos.net._boot.0 -rw--- 1 amanda unknown 11501568 25 Oct 04:04 5.sulu.hq.imos.net._boot.0 -rw--- 1 amanda unknown 15 25 Oct 04:49 6-stefan.hq.imos.net._.0 -rw--- 1 amanda unknown 14072414208 25 Oct 04:49 6.stefan.hq.imos.net._.0 -rw--- 1 amanda unknown 12 25 Oct 04:49 7-ox.hq.imos.net._.0 -rw--- 1 amanda unknown 22708224 25 Oct 04:49 7.ox.hq.imos.net._.0 -rw--- 1 amanda unknown 13 25 Oct 04:49 8-sulu.hq.imos.net._opt2.1 -rw--- 1 amanda unknown 81297408 25 Oct 04:49 8.sulu.hq.imos.net._opt2.1 -rw--- 1 amanda unknown 14 25 Oct 05:28 9-ox.hq.imos.net._usr.0 -rw--- 1 amanda unknown809664512 25 Oct 04:50 9.ox.hq.imos.net._usr.0 -rw--- 1 amanda unknown 10 25 Oct 05:28 00010-TAPEEND -rw--- 1 amanda unknown32768 25 Oct 05:28 00010.TAPEEND there is a difference because tape 8 has been used and tape 7 not :) And of course the obvious question: what version of amanda is it? version 2.4.5 It seems like the chg-disk somewhere generates a syntax error when loading the last slot with option -next. Try this: $ /usr/local/libexec/chg-disk -slot 7 $ sh -vx /usr/local/libexec/chg-disk -next Do you get the same syntax error? If yes, can you post (or mail me) the output of the sh -vx ...? I only get errors file not found for amanda.conf, how can I specify my daily set ? bye Stefan Herrmann
Re: Email delivery
On Fri, Oct 28, 2005 at 04:07:10AM +0200, Lars Bakker enlightened us: Can somebody tell me how Amanda sends email reports? I'm using the Kolab2 server on the same machine that should do the backups but unfortunately I get no reports although the smtp server works fine. Is Amanda using another program for mail delivery? It finds a mail program at compile time. You can find it with grep MAILER /path/to/logfiles/amandad.$DATETIME.debug Filling in the path and date/time appropriately. On my system, it's looking at /usr/bin/Mail. Another way is amgetconf: $ amgetconf DS1 build.mailer /usr/ucb/Mail Really, I didn't know my amanda was using that mail program. I guess I'll have to find some kind of wrapper script that works like the mail program because my mailx installation does not work in conjunction with Kolab2. I have tried to use nail (ln -s /usr/bin/nail /usr/bin/mail) instead and reports seem to work fine but when I run amcheck with the -m parameter no mail is sent. nail and mailx do not use the same parameters but I kind of hoped that amanda would just use the -s parameter for specifying the subject. I think the best way to handle my particular problem would be to recompile the debian package. Any other ideas? regard lars
Re: Dell PowerVault 122T LTO2 tapetype sanity check.
Jon LaBadie wrote:
On Wed, Oct 26, 2005 at 04:33:19PM -0700, Alan Jedlow wrote:
Hi,
I know the docs say to turn hardware compression
off before running amtapetype, unfortunately I've
found no info on how to disable hw compression on a
Dell PowerVault 122T LTO2 library.
How bad is this result ?
---
-bash-3.00$ /usr/sbin/amtapetype -e 200g -f /dev/nst0 -t Ultrium2
Writing 4096 Mbyte compresseable data: 40 sec
Writing 4096 Mbyte uncompresseable data: 350 sec
WARNING: Tape drive has hardware compression enabled
Estimated time to write 2 * 204800 Mbyte: 35000 sec = 9 h 43 min
wrote 6422528 32Kb blocks in 98 files in 6420 seconds (short write)
wrote 6422528 32Kb blocks in 196 files in 6719 seconds (short write)
define tapetype Ultrium2 {
comment just produced by tapetype prog (hardware compression on)
length 200704 mbytes
filemark 0 kbytes
speed 31300 kps
}
---
Most drives use a compression algorithm that expands,
rather than compressing, data that is random or nearly so.
LTO drives have the nearly unique feature for dealing with
this problem in that they sense the expansion potential and
turn off compression themselves.
This is confirmed by the length parameter in the produced tapetype
above. 200 GB is the native length of LTO2 tape, so it seems that the
drive did not try to compress the incoming data. Looks like there's no
reason to worry.
--
Toomas Aas
|arvutivõrgu peaspetsialist | head specialist on computer networks|
|Tartu Linnakantselei | Tartu City Office |
- +372 736 1274
Re: Dumps too big
Montagni, Giovanni wrote: I have a configuration that do full backup every day. Yesterday, amanda say that dumps way too big must skip incremental dumps. But the tape is used only by 68%, as i can see from the report. --- USAGE BY TAPE: Label Time Size %Nb bk01 3:29 70593.6 68.0 6 --- Why amanda can't do full backup? How can i return to make full backup? In addiction, the amount of data is less than other days, when tape is used by 88%. That's strange... Maybe some DLE has considerably increased in size. On previous days, all your DLEs fit on tape and filled it by 88%. Now some DLE has grown, so the total amount of backup would be more than 100% of your tape size. Amanda's planner notices that and doesn't back up some DLE, to make the total backup size less than your tape length. So the total amount backed up is less than usual, because one DLE wasn't backed up at all. Without seeing more of your Amanda report that's all merely a guess, but I'm pretty sure that's it. -- Toomas Aas
Re: Email delivery
Lars Bakker wrote: I have tried to use nail (ln -s /usr/bin/nail /usr/bin/mail) instead and reports seem to work fine but when I run amcheck with the -m parameter no mail is sent. Amcheck -m only sends mail if it finds some problem(s). If your setup is OK, it doesn't send anything -- Toomas Aas |arvutivõrgu peaspetsialist | head specialist on computer networks| |Tartu Linnakantselei | Tartu City Office | - +372 736 1274
R: R: Release of amanda-2.5.0b1
What's the best way to set up tape changer manual with two tapes? Just set runtapes 2, tape changer chg-manual ? And for label tapes? I must label all tapes before set those options? I also think i have to update tapecycle... I'm wait for any suggestion, because i don't know what's is the correct way... Thanks a lot. Giovanni -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Jon LaBadie Inviato: giovedì 27 ottobre 2005 17.02 A: amanda-users@amanda.org Oggetto: Re: R: Release of amanda-2.5.0b1 On Thu, Oct 27, 2005 at 11:37:36AM +0200, Montagni, Giovanni wrote: -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Jean-Louis Martineau Inviato: martedì 25 ottobre 2005 13.08 A: amanda-announce@amanda.org; amanda-users@amanda.org Oggetto: Release of amanda-2.5.0b1 Hello, The Amanda core team is pleased to announce the release of Amanda 2.5.0b1. It is a redesign of many part of amanda. The span/split patch from John Stange was ported to 2.5.0 and is integrated in this release. This means that in 2.5.0 i can use two tape for backup without tape changer? So when the end of first tape is reached, amanda eject the tape and wait for the second? I believe the two capabilities are independent. You always (well, for a very long time) could use multiple tapes without a changer. There is a pseudo-changer script, chg-manual, that notifies the operator when it is necessary to swap tapes. The tape span/split patch removes the restriction that the entire image of each single DLE dump must tape to a single tape. With the patch activated an image that partially fits at the end of a tape can be continued on the next tape rather than restarting from the beginning of the image. Your posting raises a question I don't recall addressed. How does the span/split patch handle the situation where runtapes is 1 and/or no changer is specified? Or where runtapes is N and on the Nth tape an image doesn't fit? I presume the last image is restarted the next run of taper or if direct to tape that image is lost? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Email delivery
I have tried to use nail (ln -s /usr/bin/nail /usr/bin/mail) instead and reports seem to work fine but when I run amcheck with the -m parameter no mail is sent. Amcheck -m only sends mail if it finds some problem(s). If your setup is OK, it doesn't send anything I know, but I have inserted a wrong disk so it guess should report that the tape has to be changed.
Re: Connection refused by peer
Thomas Wegner wrote: Could you try without a changer, or debug your changer script? That might be the problem. I have no changer and in amanda.conf is no changer defined. -- [EMAIL PROTECTED]:~$ amtape backup_woche device amtape: no tpchanger specified in /etc/amanda/backup_woche/amanda.conf - That's an error message I believe, even though it's not evidently worded as such. You seem to have specified runtapes 1 without giving a changer. Either configure a changer if you want more than one tape per run, or just set runtapes to 1. Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
R: R: Release of amanda-2.5.0b1
What's the best way to set up tape changer manual with two tapes? Just set runtapes 2, tape changer chg-manual ? And for label tapes? I must label all tapes before set those options? I also think i have to update tapecycle... I'm wait for any suggestion, because i don't know what's is the correct way... Thanks a lot. Giovanni -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Jon LaBadie Inviato: giovedì 27 ottobre 2005 17.02 A: amanda-users@amanda.org Oggetto: Re: R: Release of amanda-2.5.0b1 On Thu, Oct 27, 2005 at 11:37:36AM +0200, Montagni, Giovanni wrote: -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Jean-Louis Martineau Inviato: martedì 25 ottobre 2005 13.08 A: amanda-announce@amanda.org; amanda-users@amanda.org Oggetto: Release of amanda-2.5.0b1 Hello, The Amanda core team is pleased to announce the release of Amanda 2.5.0b1. It is a redesign of many part of amanda. The span/split patch from John Stange was ported to 2.5.0 and is integrated in this release. This means that in 2.5.0 i can use two tape for backup without tape changer? So when the end of first tape is reached, amanda eject the tape and wait for the second? I believe the two capabilities are independent. You always (well, for a very long time) could use multiple tapes without a changer. There is a pseudo-changer script, chg-manual, that notifies the operator when it is necessary to swap tapes. The tape span/split patch removes the restriction that the entire image of each single DLE dump must tape to a single tape. With the patch activated an image that partially fits at the end of a tape can be continued on the next tape rather than restarting from the beginning of the image. Your posting raises a question I don't recall addressed. How does the span/split patch handle the situation where runtapes is 1 and/or no changer is specified? Or where runtapes is N and on the Nth tape an image doesn't fit? I presume the last image is restarted the next run of taper or if direct to tape that image is lost? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Connection refused by peer
Am Freitag, den 28.10.2005, 13:07 +0200 schrieb Alexander Jolk:
Could you try without a changer, or debug your changer script? That
might be the problem.
I have no changer and in amanda.conf is no changer defined.
--
[EMAIL PROTECTED]:~$ amtape backup_woche device
amtape: no tpchanger specified in /etc/amanda/backup_woche/amanda.conf
-
That's an error message I believe, even though it's not evidently worded
as such. You seem to have specified runtapes 1 without giving a
changer. Either configure a changer if you want more than one tape per
run, or just set runtapes to 1.
No, I didn't configured any changer or any runtapes. This is my
amanda.conf:
-
org Wochenbackup # your organization name for reports
mailto root tommi # space separated list of operators at your site
dumpuser backup # the user to run dumps under
#
inparallel 4# maximum dumpers that will run in parallel
netusage 600 # maximum net bandwidth for Amanda, in KB per sec
# a filesystem is due for a full backup once every dumpcycle days
#dumpcycle 7 days # the number of days in the normal dump cycle
#tapecycle 7 tapes # the number of tapes in rotation
dumpcycle 1 day
tapecycle 2 tapes
bumpsize 20 MB # minimum savings (threshold) to bump level 1 - 2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * (level-1)**bumpmult
#runtapes 9 # explained in WHATS.NEW
#tpchanger no-changer # the tape-changer glue script, see
TAPE.CHANGERS
tapedev /dev/nst0 # Linux @ tuck, important: norewinding
# tapedev /dev/nrst8 # or use the (no-rewind!) tape device directly
#Eintrag von Hand vom 23.10.2005
tapetype HP-DAT-C1537A
labelstr ^Wochenbackup[0-9][0-9]*$# label constraint regex: all tapes
must match
diskdir /var/backups/amandadump/backup_woche # where the holding disk
is
disksize 500 MB # how much space can we use on it
#diskdir /dumps/amanda/work # additionaly holding disks can be
specified
#diskdir /mnt/disk4
#disksize 1000 MB # they are used round-robin
# Amanda needs a few MB of diskspace for the log and debug files,
# as well as a database. This stuff can grow large, so the conf
directory
# isn't usually appropriate.
infofile /var/lib/amanda/backup_woche/curinfo # database filename
logfile /var/log/amanda/backup_woche/log # log filename
# where the index files live
indexdir /var/lib/amanda/backup_woche/index
# tapetypes
#Eintrag von Hand - siehe amanda.org vom 23.10.2005
define tapetype HP-DAT-C1537A {
comment HP C1537A Streamer - DDS3 Tape
length 11694 mbytes
filemark 78 kbytes
speed 830 kps
}
define dumptype nocomp-user {
comment Non-root partitions on slow machines
options no-compress
priority medium
}
Thomas
Re: Email delivery
On Fri, Oct 28, 2005 at 11:54:10AM +0200, Lars Bakker wrote: On Fri, Oct 28, 2005 at 04:07:10AM +0200, Lars Bakker enlightened us: Can somebody tell me how Amanda sends email reports? I'm using the Kolab2 server on the same machine that should do the backups but unfortunately I get no reports although the smtp server works fine. Is Amanda using another program for mail delivery? It finds a mail program at compile time. You can find it with grep MAILER /path/to/logfiles/amandad.$DATETIME.debug Filling in the path and date/time appropriately. On my system, it's looking at /usr/bin/Mail. Another way is amgetconf: $ amgetconf DS1 build.mailer /usr/ucb/Mail Really, I didn't know my amanda was using that mail program. I guess I'll have to find some kind of wrapper script that works like the mail program because my mailx installation does not work in conjunction with Kolab2. I have tried to use nail (ln -s /usr/bin/nail /usr/bin/mail) instead and reports seem to work fine but when I run amcheck with the -m parameter no mail is sent. nail and mailx do not use the same parameters but I kind of hoped that amanda would just use the -s parameter for specifying the subject. The above 'ln -s' command indicates you have the ability and willingness to replace whatever is in /usr/bin/mail. In that case, replace it with a shell script that will be a /usr/bin/nail wrapper. I.e. one that takes amanda's arguments intended for mail and and adjusts them to be appropriate for nail. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Email delivery
On Fri, Oct 28, 2005 at 11:54:10AM +0200, Lars Bakker wrote: I think the best way to handle my particular problem would be to recompile the debian package. Forgot to mention, that if the debian package can't send mail reports properly, a defect report to debian seems appropriate. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: problems with label of tape in last slot
On Fri, Oct 28, 2005 at 10:39:54AM +0200, Stefan Herrmann wrote: It seems like the chg-disk somewhere generates a syntax error when loading the last slot with option -next. Try this: $ /usr/local/libexec/chg-disk -slot 7 $ sh -vx /usr/local/libexec/chg-disk -next Do you get the same syntax error? If yes, can you post (or mail me) the output of the sh -vx ...? I only get errors file not found for amanda.conf, how can I specify my daily set ? The changer scripts 'assume' they are running from the config directory containing the amanda.conf file. Change directory to there and try it. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Email delivery
On Fri, 28 Oct 2005, Jon LaBadie wrote:
On Fri, Oct 28, 2005 at 11:54:10AM +0200, Lars Bakker wrote:
I think the best way to handle my particular problem would be to
recompile the debian package.
Forgot to mention, that if the debian package can't send mail
reports properly, a defect report to debian seems appropriate.
Indeed. On my Amanda server, mail works fine (but I use sendmail ;-).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
Re: R: R: Release of amanda-2.5.0b1
On Fri, Oct 28, 2005 at 12:23:16PM +0200, Montagni, Giovanni wrote: What's the best way to set up tape changer manual with two tapes? Just set runtapes 2, tape changer chg-manual ? I don't know about chg-manual, but tape changer scripts often require some configuration settings for your environment. Generally these are documented in the script's comments, just like amanda.conf is self-documenting :) And for label tapes? I must label all tapes before set those options? Tapes must be labeled once, before use. Whether that is before changing various options or not is up to your timetable. I also think i have to update tapecycle... Basically yes, but you can always cycle more tapes than the value of tapecycle. Tapecycle is a lower limit for too-early overwrite protection of your data. It is not an upper limit. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Email delivery
I guess I'll have to find some kind of wrapper script that works like the mail program because my mailx installation does not work in conjunction with Kolab2. I have tried to use nail (ln -s /usr/bin/nail /usr/bin/mail) instead and reports seem to work fine but when I run amcheck with the -m parameter no mail is sent. nail and mailx do not use the same parameters but I kind of hoped that amanda would just use the -s parameter for specifying the subject. The above 'ln -s' command indicates you have the ability and willingness to replace whatever is in /usr/bin/mail. In that case, replace it with a shell script that will be a /usr/bin/nail wrapper. I.e. one that takes amanda's arguments intended for mail and and adjusts them to be appropriate for nail. That is what I intended to do. My Kolab2 server is not part of the debian package system and that's why the local mail delivery is broken or at least it's the reason for mailx not working properly. I haven't had the time to solve this problem yet and there are several other programs which use mailx. So maybe writing a wrapper would help. What I did not mention before is that I'm using the chg-manual script. When I took a look into that script I found out that there is a function named request() which asks the user to insert a tape and press return. Right beneath it is another version of that function which is not enabled by default and which provides an email based tape change request. Consequently, I just changed the functions and everything worked the way I wanted it to work. --- lars
Re: Need help diagnosing hostname problems
KEVIN ZEMBOWER wrote: Thank you, Olivier, Scott and Matt, for all your suggestions. Your helpfulness is part of what makes Amanda a truly great solution. AMANDA-users take care of each other ;-) The problem, as you all suggested, seems to be the lack of a reverse DNS look-up capability I'm betting this might be a fairly common problem that some of you all have solved before. What's your preferred solution? I can think of a couple of alternatives, such as: - set up my own DNS on one of my hosts in the DMZ. This isn't too hard, but is one more thing to maintain. If the folks who control the DNS won't set up proper reverse-lookups for your hosts (this would be somehow unprofessional, AFAI see), I don't see any problem in setting up a local BIND with a forwarders-parameter pointing to the DNS of the folks. If your hosts are pretty static, there won't be much maintenance, just some initial setup. Stefan -- Stefan G. Weichinger AMANDA core team member mailto://[EMAIL PROTECTED] -- oops! linux consulting implementation http://www.oops.co.at --
