----- Original Message ----- > On 7/20/12 10:54 AM, Steven S. Critchfield wrote: > > Just had a task to get our daemon here up and running like the > > others in the system. This gave me a nice excuse to go learn > > upstart. I know > > CentOS6 and Newer Ubuntu have it by default. I had been tripping > > over the init scripts complaining about me accessing them directly. > > > > First impressions are just "WOW!!!!!!!11!" > > > > That was so easy to set up from scratch. > > > > I suggest any sysadmin who has hacked a script together to start a > > service should look into the upstart configs. Your life just became > > a lot more flexible, powerful, and simpler. > > What, did they get rid of the SysV startup method? Ack!!! In the past, > I'd usually copy the lpd (or something similarly easy) to create my > start/stop scripts. > > How does this work compared to the old way?
upstart is actually a replacement for init. Part of what I find really slick on upstart is that they use dbus and message passing to fire up and down jobs or tasks. One of my soon to change habits is creating a cron that runs every so often and check for stuff waiting to be done. You can write an upstart config that cranks up your otherwise croned app in response to a message. Then when you would have created the work for the cron to do, you just fire the message off to it. -- Steven Critchfield [email protected] -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en
