Date: Thu, 24 Jul 2014 13:24:14 +0800 From: Jov <amutu@amutu.com> To: kpneal@pobox.com Cc: "Mike." <the.lists@mgm51.com>, freebsd-questions@freebsd.org Subject: Re: run sh rc cause two cron process running Message-ID: <CADyrUxPubEbjAdbbrZp81t82bHSQ==zfjCTZwkDOGZBjTU_Q4Q@mail.gmail.com> In-Reply-To: <20140724034118.GA86589@neutralgood.org> References: <CADyrUxPAwDJ2VjfJXhAbgm73oAkmW1CZ4gUZ1%2B_EUzwgZdR9Qg@mail.gmail.com> <20140723162119.GA46908@neutralgood.org> <201407231333010555.00FDB5EB@smtp.24cl.home> <20140724034118.GA86589@neutralgood.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for all your advice,I will not run sh rc in the future. In the fact,most time I use the /etc/rc.d/xx stop|start to test the configure.But Sometimes I do not sure wich file I should run,or what command I should run,and I find sh rc is handy.For example: ntpdate_enable="YES" cloned_interfaces="lo1" ipv4_addrs_lo1="192.168.2.1-4/29" I can't find ntpdate in /etc/rc.d,and I am not familiar with ifconfig command. If some one run sh rc,is it possible report a warning? I find the sh rc on the web,I am sure some one else use it. Jov blog: http:amutu.com/blog <http://amutu.com/blog>; 2014-07-24 11:41 GMT+08:00 <kpneal@pobox.com>: > On Wed, Jul 23, 2014 at 01:33:01PM -0400, Mike. wrote: > > On 7/23/2014 at 12:21 PM kpneal@pobox.com wrote: > > |If you want to test the entire boot process then you have no real choice > > |except to reboot. But I will say that in all my years I've never created > > |a problem simply by editing rc.conf that required testing with a reboot. > > | > > |I have made changes that required testing with a full reboot, but there > > was > > |more to that than changing rc.conf. > > ============= > > > > > > > > After I make changes to rc.conf, I always run > > > > sh -n rc.conf > > > > to check for syntax errors, e.g., a missing quote, which can have a less > > than positive effect upon the boot process. > > A habit I've found helpful is to, whenever I open a quote/brace/bracket, > always go ahead and add the close. Then go back and add in the middle > the desired content. > > This basically eliminates the entire class of missing closing character > errors. > -- > Kevin P. Neal http://www.pobox.com/~kpn/ > "14. Re-reading No. 13, I realize that it's quite possible I'm losing my > mind. I'm glad that for the most part I'm not aware it's happening." > -- from "20 things I'm thankful for": Fortune, Nov 29, 2004, page 230 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADyrUxPubEbjAdbbrZp81t82bHSQ==zfjCTZwkDOGZBjTU_Q4Q>