From owner-freebsd-questions Sat Oct 14 11:12:53 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA14367 for questions-outgoing; Sat, 14 Oct 1995 11:12:53 -0700 Received: from etinc.com (etinc-gw.new-york.net [165.254.13.209]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA14362 for ; Sat, 14 Oct 1995 11:12:50 -0700 Received: from trumpet.etnet.com (trumpet.etnet.com [129.45.17.35]) by etinc.com (8.6.11/8.6.9) with SMTP id OAA14090; Sat, 14 Oct 1995 14:24:25 -0400 Date: Sat, 14 Oct 1995 14:24:25 -0400 Message-Id: <199510141824.OAA14090@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: et-users@netrail.net From: dennis@etinc.com (dennis) Subject: Re: [ET-users] Re: T1 Card and FreeBSD Cc: questions@freebsd.org, nathan@netrail.net Sender: owner-questions@freebsd.org Precedence: bulk > >> >would you know the file it runs when a freebsd does a shutdown? I want to >> >put that line uust before it syncs the disks. In linux it was >> >/etc/rc.d/rc.0 but I can't see what freebsd uses. >> > > >> I don't know, I'm copying this to the freebsd list...... > >> you could create a file called "doshutdown" like this > >> /usr/hdlc/utils/et5reset >> shutdown > >> and use it instead of shutdown..... > >A quick look at the shutdown man page leads me to believe that there's >no script run by shutdown. > >However, it should be possible to hack the shutdown source to do what >you want. I'm not a C expert, but it seems that you could fork another >process that'd execute whatever scripts that you wanted and wait for >completion. > This sounds like way too much work. I would do the following: mv /sbin/shutdown /sbin/shutdown.orig and then create a batch file named /sbin/shutdown as to following: /usr/hdlc/utils/et5reset 0 #/usr/hdlc/utils/et5reset 2 when you add another board /sbin/shutdown.orig Another solution is to enable the "memory sharing" option in the config file for the board. This will cause the shared memory window to be enabled only when the memory is being accessed. There is a little overhead, but not much. You may be using this to put multiple boards at the same address when you add more boards anyway. Dennis ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous Communications Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25