Date: Wed, 28 Feb 2001 13:27:15 -0600 From: Mike Meyer <mwm@mired.org> To: Drew Tomlinson <drewt@writeme.com> Cc: "FreeBSD Questions (E-mail)" <freebsd-questions@FreeBSD.org> Subject: RE: Startup Script Message-ID: <15005.20755.398545.110975@guru.mired.org> In-Reply-To: <BA5D0CE1CBB2D411B6AA00A0CC3F02390AF887@ldcmsx01.lc.ca.gov> References: <BA5D0CE1CBB2D411B6AA00A0CC3F0239D8461A@ldcmsx01.lc.ca.gov> <BA5D0CE1CBB2D411B6AA00A0CC3F02390AF887@ldcmsx01.lc.ca.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
Drew Tomlinson <drewt@writeme.com> types: > > I don't know anything about dynipclient, but the script looks fine to > > me - assuming that dynipclient is somehow detaching itself so the > > command the shell started is exiting. Are you checking for > > "dynipclient", or for pid 195? If the former, dynipclient may have a > > different name than you expect, so check for the latter. > > This script also works fine when invoked from the command line: You already mentioned that. > > > I am a newbie and know basically nothing about scripts. > > But I suspect what > > > might be happening is that the dynipclient starts in the > > first line but then > > > is stopped because of the command in the second. Am I > > correct? Any ideas? > > > > No, that's not correct. > > > > If something is causing the server part of the package to exit, see > > what you can do to get a log - preferably detailed - from the > > server. If www.dynip.com provides a sample startup script, you might > > check that and see if they are doing anything odd when it starts the > > program. > OK, I would like to get a log but I don't know how to go about that. Do you > have any suggestions? I assume I need to pipe the output to a file? I > don't even know how to do that exactly. Sorry for the "dumb" questions and > thanks for your help. Well, you can check the various system logs to see if it put anything there. Redirecting might work; if so, add the sequence '>/var/run/dynip.log 2>&1' (minus the ''s, of course) to the line that starts it. On the other hand, in the process of daemonizing itself, it may close all those things. In which case, you'll need to check with the dynip folks to see how to get it to log things. Or check the source, if you've got that. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15005.20755.398545.110975>