<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
Is Red Hat looking into doing Upstart? (Or have they already moved? I am a Debian/Ubuntu guy right now)<br>That is a rather significant change to how things get started in Linux.<br><br><br><br><div>> Date: Tue, 12 Jul 2011 13:44:57 -0600<br>> From: chris@fedde.us<br>> To: clue@cluedenver.org<br>> Subject: Re: [clue] [Tech] Red Hat Ent Server runlevels<br>> <br>> The easiest approach is to copy na init.d script for something simple<br>> like cron and modify it for your purposes. If done right then your<br>> script will work with chkconfig. The mechanisms are pretty straight<br>> forward but I think it is easier to work from an example than to craft<br>> something from whole cloth.<br>> <br>> On Mon, Jul 11, 2011 at 2:38 PM, Bruce Ediger <bediger@stratigery.com> wrote:<br>> > I'm a native Slackware user, and my other PC runs Arch at the moment,<br>> > but I need some plain talk about Red Hat Enterprise Server runlevels.<br>> ><br>> > Suppose I have a server that I want started when a system boots.<br>> > My understanding is this:<br>> ><br>> > I write a /bin/sh script that takes one command-line parameter, "start"<br>> > or "stop". When run with "start", the script has to fire up the server.<br>> > When run with "stop", it has to stop the server.<br>> ><br>> > I put the /bin/sh script in /etc/rc.d/init.d. I make it owned by<br>> > root/root, and give it 700 permissions.<br>> ><br>> > I create symbolic links from that /bin/sh script to<br>> > /etc/rc.d/rc3.d/S99mynewscript and /etc/rc.d/rc5.d/K99mynewscript<br>> > and /etc/rc.d/rc6.d/K99mynewscript<br>> ><br>> > Then, I reboot and verify that my server gets stopped and started<br>> > correctly.<br>> ><br>> > Is anything wrong with the procedure above? Have I mixed Slackware and<br>> > Arch style runlevels with Red Hat runlevels? Am I even close to<br>> > correct?<br>> ><br>> > _______________________________________________<br>> > clue mailing list: clue@cluedenver.org<br>> > For information, account preferences, or to unsubscribe see:<br>> > http://cluedenver.org/mailman/listinfo/clue<br>> ><br>> _______________________________________________<br>> clue mailing list: clue@cluedenver.org<br>> For information, account preferences, or to unsubscribe see:<br>> http://cluedenver.org/mailman/listinfo/clue<br></div> </div></body>
</html>