Thanks for the feedback. We are running Solaris 9, Delegate 9.7.7. Even when just starting and stopping the process we have the same problem if the fully qualified domain names are not resolvable at the time of starting.
Specialist Services | ICO | EMS | NES - TN&S | Telstra Corporation
Level 8 | 231 Elizabeth St, Sydney, NSW 2000
(w) +60 0 0000 000f | (m) +60 000 000 00F
graham.trigge@telstra.. | www.telstra.com
From: Yutaka Sato [mailto:firstname.lastname@example.org]
Sent: Wednesday, 20 January 2010 10:51 AM
Cc: Trigge, Graham
Subject: Re: [DeleGate-En] Ignoring MOUNT DNS lookup errors
In message <42205B56DE9EC24AA31C994A500BE5FF16BE3AF406@WSMSG3104V.srv.dir.telstra.com> on 01/19/10(09:55:21)
you "Trigge, Graham" <email@example.com> wrote:
|I am running Delegate 9.7.7 and am using the software to bridge FTP to SFTP connections. The problem I currently have is a few of the MOUNT commands I have configured are using FQDN names - if any of these names are not resolvable on starting Delegate (as we do each night for log rotation) the application does to restart.
|Is there a method/command to ignore errors originating from DNS lookup checks on fully qualified domain names? I have included a snippet of my configuration file for review:
|If "ftp.ext_server.com" is not resolvable on startup, the application does not start.
Maybe it depends on what your OS is, and how you do the restarting,
but it is highly possible that recent versions of DeleGate does not
9 9 Yutaka Sato <firstname.lastname@example.org> http://delegate.org/y.sato/
( ~ ) National Institute of Advanced Industrial Science and Technology
_< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller