home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #31 / NN_1992_31.iso / spool / comp / infosyst / gopher / 1739 < prev    next >
Encoding:
Text File  |  1992-12-25  |  1.2 KB  |  32 lines
  1. Newsgroups: comp.infosystems.gopher
  2. Path: sparky!uunet!wupost!darwin.sura.net!aplcen.apl.jhu.edu!aplcenmp!prm
  3. From: prm@aplcenmp.apl.jhu.edu (Paul Raymond McMullin)
  4. Subject: Re: No logging when running ``gopherd -u gopher'' ?
  5. Message-ID: <BzrMzM.7GJ@aplcenmp.apl.jhu.edu>
  6. Organization: Johns Hopkins Continuing Professional Programs
  7. References: <SHENTON.92Dec23155051@nsisrv.gsfc.nasa.gov>
  8. Date: Thu, 24 Dec 1992 13:33:22 GMT
  9. Lines: 21
  10.  
  11. This sounds like a question for the FAQ:
  12.  
  13. (Q) "Howcum gopher works differently from inetd than from when I was
  14.     running it as a stand-alone process?"
  15.  
  16. (A) Most unix(tm) systems appear to have a limit of 5 parameters that
  17.     are passed from the inetd invocation line to the program.  This is
  18.     remedied by "wrapping" the invocation in a shell script, and invoking the
  19.     script from inetd ala:
  20.  
  21.         #!/bin/sh
  22.         cd /export1/sdnet/newgopher/gopherd
  23.         gopherd -I -o /export1/sdnet/newgopher/gopherd/gopherd.conf \
  24.             -l /export1/sdnet/newgopher/gopher.log \
  25.             -u sdnet -c /export1/sdnet/newgopher/gopher-data 70
  26.  
  27.     or whatever it is that you need to be doing...
  28.  
  29. -prm
  30. -- 
  31. Paul McMullin prm@aplcomm.jhuapl.edu
  32.