Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!yale.edu!think.com!enterpoop.mit.edu!bloom-picayune.mit.edu!e40-008-7.MIT.EDU!vikki From: vikki@e40-008-7.MIT.EDU (Vikki King) Subject: Re: [386BSD] slattach in rc.local Message-ID: <1992Dec7.014230.12312@athena.mit.edu> Sender: news@athena.mit.edu (News system) Nntp-Posting-Host: e40-008-7.mit.edu Organization: Massachvsetts Institvte of Technology X-Newsreader: Tin 1.1 PL4 References: <murray.7.723306772@its.uct.ac.za> Date: Mon, 7 Dec 1992 01:42:30 GMT Lines: 40 Hey! I seemed to be having a similar problem starting up innd from rc.news by calling it up in rc. What got it working was to change the owner of rc.news to 'operator'. From what was said about permissions below, I wonder if a similar remedy would help? -John jackson@a1.mec.mass.edu (or) vikki@athena.mit.edu murray@its.uct.ac.za (Mark Murray) writes: : In article <sandi.723285721@gimli> root@gimli.cs.uct.ac.za (Sandi Donno) writes: : >From: root@gimli.cs.uct.ac.za (Sandi Donno) : >Subject: Re: [386BSD] slattach in rc.local : >Date: Wed, 2 Dec 1992 08:42:01 GMT : >In <1992Nov30.231018.28698@sserve.cc.adfa.oz.au> wkt@rodos1.cs.adfa.oz.au (Warren Toomey) writes: : > : >>In article <1992Nov30.080340.5412@ericsson.se>, eratho@eras165.ericsson.se (Thomas W Nilsson) writes: : >>|> : >>|> why doesn't slattach run correct from rc.local?? : : : >I have a similar problem with nnmaster, which also dies when run from : >rc but works fine when run by root from the prompt. I tried using nohup : >some time back when I discovered that nnmaster was saying "terminated: hangup" : >in the log file, but it made no difference whatsoever. : : I'm seeing a pattern here... : : I have the same nnmaster problem, _and_ it won't execute from a script: : : #!/bin/sh : cd /usr/local/lib/nn : nnmaster -l -r -C : : This dies with some stupid permissions problem. : : I tried to set /sbin/dump to setuid to root. This works from the prompt but : not from a script. : : Looks like some 386BSD problem...