Re: rc.local equivalent in Woody?
On Mon, Apr 01, 2002 at 07:24:44AM -0600, John Hasler wrote: > Karl E. Jorgensen writes: > > Or perhaps local.foobar ? > > Run-parts will ignore a file with a '.' in the name. Ouch. That's a *very* good point :-) Out goes the dots ... -- Karl E. Jørgensen [EMAIL PROTECTED] www.karl.jorgensen.com Today's fortune: Your job is being a professor and researcher: That's one hell of a good excuse for some of the brain-damages of minix. (Linus Torvalds to Andrew Tanenbaum) pgpZqTiBeqJX4.pgp Description: PGP signature
Re: rc.local equivalent in Woody?
Karl E. Jorgensen writes: > Or perhaps local.foobar ? Run-parts will ignore a file with a '.' in the name. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: rc.local equivalent in Woody?
On Sat, Mar 30, 2002 at 10:01:12PM -0800, Karsten M. Self wrote: > on Tue, Mar 26, 2002, Sean 'Shaleh' Perry ([EMAIL PROTECTED]) wrote: > > > > On 26-Mar-2002 Randolph S. Kahle wrote: > > > In my Potato installation, I place a call to hdparm in rc.local. > > > > > > In my new Woody installation, I cannot find rc.local. > > > > > > What is the correct place / file to use for boot-up configuration / > > > control commands? > > > > > > > make a /etc/init.d/local script (call it something that is likely to > > not be used by a package). Use update-rc.d to add it to the run level > > tree. > > This question comes up enough that a policy ought IMVAO be set for it. > > Viz: any rc script named local-foo is considered local and sacrosanct > by the system, where "-foo" could have any arbitrary value, including > null (for the single instance of a local script). > > But this way I could, say, run four local webservers as > local-apache-mydom0, local-apache-mydom1, local-apache-mydom2, and > local-apache-mydom3, without worrying about how they're treated by > Debian. Or perhaps local.foobar ? "." instead of "-", as this could use the same notation as the Debian Menu policy.. > > I'll bounce this to the devel (or other) list if someone thinks this is > a worthwhile suggestion. Definitely. Just my 1 pence... -- Karl E. Jørgensen [EMAIL PROTECTED] www.karl.jorgensen.com ... An rfc2324 advocate http://www.rfc.net/rfc2324.html pgpp9Himtszbp.pgp Description: PGP signature
Re: rc.local equivalent in Woody?
> > This question comes up enough that a policy ought IMVAO be set for it. > > Viz: any rc script named local-foo is considered local and sacrosanct > by the system, where "-foo" could have any arbitrary value, including > null (for the single instance of a local script). > > But this way I could, say, run four local webservers as > local-apache-mydom0, local-apache-mydom1, local-apache-mydom2, and > local-apache-mydom3, without worrying about how they're treated by > Debian. > > I'll bounce this to the devel (or other) list if someone thinks this is > a worthwhile suggestion. > well, this is practically guaranteed right now, unless some package named 'local' comes along and wants to be weird (-: I would like to see this documented more clearly in as many obvious places as possible though. And yes, you should definately pester the devels. Maybe mail the documentation people as well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: rc.local equivalent in Woody?
on Tue, Mar 26, 2002, Sean 'Shaleh' Perry ([EMAIL PROTECTED]) wrote: > > On 26-Mar-2002 Randolph S. Kahle wrote: > > In my Potato installation, I place a call to hdparm in rc.local. > > > > In my new Woody installation, I cannot find rc.local. > > > > What is the correct place / file to use for boot-up configuration / > > control commands? > > > > make a /etc/init.d/local script (call it something that is likely to > not be used by a package). Use update-rc.d to add it to the run level > tree. This question comes up enough that a policy ought IMVAO be set for it. Viz: any rc script named local-foo is considered local and sacrosanct by the system, where "-foo" could have any arbitrary value, including null (for the single instance of a local script). But this way I could, say, run four local webservers as local-apache-mydom0, local-apache-mydom1, local-apache-mydom2, and local-apache-mydom3, without worrying about how they're treated by Debian. I'll bounce this to the devel (or other) list if someone thinks this is a worthwhile suggestion. Peace. -- Karsten M. Self http://kmself.home.netcom.com/ What Part of "Gestalt" don't you understand? Keep software free. Oppose the CBDTPA. Kill S.2048 dead. http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html pgp7pxhcYcexL.pgp Description: PGP signature
Re: rc.local equivalent in Woody?
hi ya i'd put it ( hdparm ) into /etc/init.d/bootmisc.sh (or create that file ) c ya alvin On Tue, 26 Mar 2002, Alan James wrote: > On Tue, Mar 26, 2002 at 10:11:20AM -0700, Randolph S. Kahle wrote: > > In my Potato installation, I place a call to hdparm in rc.local. > > > > In my new Woody installation, I cannot find rc.local. > > > > What is the correct place / file to use for boot-up configuration / > > control commands? > > > > I just put this in roots crontab : > > @reboot /sbin/hdparm -d 1 /dev/hda > > Does the trick for me. ("crontab -e" to edit a users own crontab) > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: rc.local equivalent in Woody?
On Tue, Mar 26, 2002 at 10:11:20AM -0700, Randolph S. Kahle wrote: > In my Potato installation, I place a call to hdparm in rc.local. > > In my new Woody installation, I cannot find rc.local. > > What is the correct place / file to use for boot-up configuration / > control commands? > I just put this in roots crontab : @reboot /sbin/hdparm -d 1 /dev/hda Does the trick for me. ("crontab -e" to edit a users own crontab) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: rc.local equivalent in Woody?
On 26-Mar-2002 Randolph S. Kahle wrote: > In my Potato installation, I place a call to hdparm in rc.local. > > In my new Woody installation, I cannot find rc.local. > > What is the correct place / file to use for boot-up configuration / > control commands? > make a /etc/init.d/local script (call it something that is likely to not be used by a package). Use update-rc.d to add it to the run level tree. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
rc.local equivalent in Woody?
In my Potato installation, I place a call to hdparm in rc.local. In my new Woody installation, I cannot find rc.local. What is the correct place / file to use for boot-up configuration / control commands? Regards, Randy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: rc.local equivalent
"Karl E. Jorgensen" wrote: > > On Sun, Mar 03, 2002 at 08:39:29PM -0800, Xeno Campanoli wrote: > > Say, is there a catchall equivalent in Debian of the rc.local file? > > Once again I'm trying to interpret a recommendation from the TrinityOS > > HOWTO on setting up security. He suggests putting: > > > > dmesg >> /etc/info/dmesg > > > > at the end of the rc.local file, which presumably executes last in a > > RedHat system. Is there a better way to accomplish this anyway. > > Early into the boot, debian does something similar > (/etc/init.d/bootmisc.sh) and stores the output in /var/log/dmesg. > > I haven't read the TrinityOS HOWTO (nor do I know redhat), but unless > they need the "later image" of dmesg, this might do the trick for you. Idonno. He's also recommending a constant append of these suckers so you have them all from all your old reboots. On the other hand, is main reasoning is that you lose the top end gradually on a machine that stays up for a long time, which I've seen before, and you don't need all the old ones if that's all you're trying to accomplish. Anyway, at least I'm writing the two files in the same place (/var/log/latterdmesg.log I'm calling the new one). The /etc/info area doesn't really seem right for it anyway. That kindof thing, to my mind, really goes on /var. Thanks for the feedback. > -- > Karl E. Jørgensen > [EMAIL PROTECTED] > www.karl.jorgensen.com > Today's fortune: > Linux is obsolete > (Andrew Tanenbaum) > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- http://www.eskimo.com/~xeno [EMAIL PROTECTED] Physically I'm at: 5101 N. 45th St., Tacoma, WA, 98407-3717, U.S.A.
Re: rc.local equivalent
On Sun, Mar 03, 2002 at 08:39:29PM -0800, Xeno Campanoli wrote: > Say, is there a catchall equivalent in Debian of the rc.local file? > Once again I'm trying to interpret a recommendation from the TrinityOS > HOWTO on setting up security. He suggests putting: > > dmesg >> /etc/info/dmesg > > at the end of the rc.local file, which presumably executes last in a > RedHat system. Is there a better way to accomplish this anyway. Early into the boot, debian does something similar (/etc/init.d/bootmisc.sh) and stores the output in /var/log/dmesg. I haven't read the TrinityOS HOWTO (nor do I know redhat), but unless they need the "later image" of dmesg, this might do the trick for you. -- Karl E. Jørgensen [EMAIL PROTECTED] www.karl.jorgensen.com Today's fortune: Linux is obsolete (Andrew Tanenbaum)
Re: rc.local equivalent
Xeno Campanoli wrote: Say, is there a catchall equivalent in Debian of the rc.local file? Once again I'm trying to interpret a recommendation from the TrinityOS HOWTO on setting up security. He suggests putting: dmesg >> /etc/info/dmesg at the end of the rc.local file, which presumably executes last in a RedHat system. Is there a better way to accomplish this anyway. You can create a file in /etc/init.d and then put the above command inside. There is already a skeleton file in the directory, you can just copy it down. cp /etc/init.d/sekeleton /etc/init.d/dmesg-backup (edit the file and put the command in the "start)" block) update-rc.d dmesg-backup start 99 2 3 4 5 . Don't forget to edit the DAEMON variable in the startup script (just put "dmesg"). The update-rc.d just means that the dmesg-backup script will be started last (ie: 99) and on 2,3,4,5 init levels. Oki
rc.local equivalent
Say, is there a catchall equivalent in Debian of the rc.local file? Once again I'm trying to interpret a recommendation from the TrinityOS HOWTO on setting up security. He suggests putting: dmesg >> /etc/info/dmesg at the end of the rc.local file, which presumably executes last in a RedHat system. Is there a better way to accomplish this anyway? -- http://www.eskimo.com/~xeno [EMAIL PROTECTED] Physically I'm at: 5101 N. 45th St., Tacoma, WA, 98407-3717, U.S.A.
rc.local equivalent
Say, is there a catchall equivalent in Debian of the rc.local file? Once again I'm trying to interpret a recommendation from the TrinityOS HOWTO on setting up security. He suggests putting: dmesg >> /etc/info/dmesg at the end of the rc.local file, which presumably executes last in a RedHat system. Is there a better way to accomplish this anyway. -- http://www.eskimo.com/~xeno [EMAIL PROTECTED] Physically I'm at: 5101 N. 45th St., Tacoma, WA, 98407-3717, U.S.A.
Re: rc.local equivalent
Create a file in "/etc/init.d/" and call it whatever you wish. Then use "update-rc.d" to create the symlinks needed to make it work. See the "README" in "/etc/init.d/" for more details. Holp, John Mr. <[EMAIL PROTECTED]> wrote: : A couple of days ago someone asked the question that was in the back of my : mind, but I don't recall seeing the answer/s. : In Red Hat and some other Red Hat "like" distributions the path sequence : /etc/rc.d/init.d/rc.local : can be used to execute your custom scripts and/or start daemons at boot : time, that is they are run out of rc.local : The person was asking what/where is the place where one does this kind of : thing in Debian? : I cannot find /etc/rc.d : There is an /etc/rc.boot : and a /etc/init.d : If I wanted to start the printer daemon at boot time where would I put the : following : lpd start : You can also use rc3.d to start the lpd daemon in the Red : Hat way of doing things - is this the answer? : This appears to be an area where things are done differently in Red Hat : versus Debian : Thanks : John : -- : To UNSUBSCRIBE, email to [EMAIL PROTECTED] : with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- * For God so loved the world that He gave his only begotten Son, * * that whoever believes in Him should not perish...John 3:16 *
Re: rc.local equivalent
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A long time ago, in a galaxy far, far way, someone said... > A couple of days ago someone asked the question that was in the back of my > mind, but I don't recall seeing the answer/s. > > In Red Hat and some other Red Hat "like" distributions the path sequence > > /etc/rc.d/init.d/rc.local > > can be used to execute your custom scripts and/or start daemons at boot > time, that is they are run out of rc.local > > The person was asking what/where is the place where one does this kind of > thing in Debian? Debian doesn't have one. I usually make /etc/rc.local manually and make /etc/rc2.d/S99rc.local a symlink to that. > I cannot find /etc/rc.d > > There is an /etc/rc.boot > > and a /etc/init.d > > If I wanted to start the printer daemon at boot time where would I put the > following > > lpd start > > You can also use rc3.d to start the lpd daemon in the Red > Hat way of doing things - is this the answer? Basically RedHat tends to use the "nonstandard" runlevel 3 (ie /etc/rc.d/rc3.d, or /etc/rc3.d if you're using RH 7.x) while Debian defaults to the "standard" runlevel 2 (ie /etc/rc2.d). "standard" or "nonstandard" in this case being compared to other Unix implementations that use the SysV init (ie Irix, Solaris, HP-UX, etc). > This appears to be an area where things are done differently in Red Hat > versus Debian One of them. Basically everyting under /etc/rc.d on RedHat is under /etc on Debian. - -- - -- Phil Brutsche [EMAIL PROTECTED] GPG fingerprint: 9BF9 D84C 37D0 4FA7 1F2D 7E5E FD94 D264 50DE 1CFC GPG key id: 50DE1CFC GPG public key: http://tux.creighton.edu/~pbrutsch/gpg-public-key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6pqts/ZTSZFDeHPwRAicYAKC9YqFvgvmlGxfBC3XRx/UIB54NNwCeLwZv /ocTfr25L5vAW8QcTZc2fIA= =W3+K -END PGP SIGNATURE-
Re: rc.local equivalent
as far as i know there isn't one. make your own script in /etc/init.d and link to it in the runlevels that you want /etc/rc2.d is the default runlevels init scripts. personally, i like this method better, as you can just remove symlinks to stop them from starting up, but don't have to delete the init script itself. -- Forrest English http://truffula.net "When we have nothing left to give There will be no reason for us to live But when we have nothing left to lose You will have nothing left to use" -Fugazi On Wed, 7 Mar 2001, Holp, John Mr. wrote: > A couple of days ago someone asked the question that was in the back of my > mind, but I don't recall seeing the answer/s. > > In Red Hat and some other Red Hat "like" distributions the path sequence > > /etc/rc.d/init.d/rc.local > > can be used to execute your custom scripts and/or start daemons at boot > time, that is they are run out of rc.local > > The person was asking what/where is the place where one does this kind of > thing in Debian? > > I cannot find /etc/rc.d > > There is an /etc/rc.boot > > and a /etc/init.d > > If I wanted to start the printer daemon at boot time where would I put the > following > > lpd start > > You can also use rc3.d to start the lpd daemon in the Red > Hat way of doing things - is this the answer? > > This appears to be an area where things are done differently in Red Hat > versus Debian > > > > Thanks > > John > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
rc.local equivalent
A couple of days ago someone asked the question that was in the back of my mind, but I don't recall seeing the answer/s. In Red Hat and some other Red Hat "like" distributions the path sequence /etc/rc.d/init.d/rc.local can be used to execute your custom scripts and/or start daemons at boot time, that is they are run out of rc.local The person was asking what/where is the place where one does this kind of thing in Debian? I cannot find /etc/rc.d There is an /etc/rc.boot and a /etc/init.d If I wanted to start the printer daemon at boot time where would I put the following lpd start You can also userc3.d to start the lpd daemon in the Red Hat way of doing things - is this the answer? This appears to be an area where things are done differently in Red Hat versus Debian Thanks John