On Wed, Jun 28, 2017 at 12:28:38PM -0300, Helen Koike wrote:
>
>
> On 2017-06-28 10:47 AM, Antoine Jacoutot wrote:
> > On Wed, Jun 21, 2017 at 07:25:54PM -0300, Helen Koike wrote:
> > >
> > >
> > > On 2017-06-21 11:50 AM, Stuart Henderson wrote:
> > > > On 2017/06/21 16:38, Antoine Jacoutot wrote:
> > > > > > > rc.d was never designed to handle anything but daemons...
> > > > > > >
> > > > > >
> > > > > > Right, I'll redesign the scripts then.
> > > > > > To add a script in rc.local and rc.shutdown I need to add instruction in the
> > > > > > README right? The user needs to manually add those no? Or is there a way to
> > > > > > automatically add them at install (sorry if this is in the docs, I didn't
> > > > > > find it) ?
> > > > >
> > > > > You could use a @sample in the plist but if the user already has these files
> > > > > around, the @sample won't get installed obviously . So documenting in the
> > > > > readme seems like the way to go.
> > > > > Unless someone has another idea?
> > > >
> > > > I think that would be the simplest approach.
> > > >
> > >
> > > There is a problem using rc.local because of the order it runs, I need to
> > > run some scripts before the daemons begin.
> >
> > These scripts must be run on each boot, right, not only when the machine is
> > instanciated?
>
> right
>
> >
> > > I changed the approach and used the meta script
> > > /etc/rc.d/google_compute_image to run those startup/shutdown scripts, it
> > > feels much better then before at least.
> >
> > It does indeed. That said, I can't make up my mind about it :-)
> > Stuart what do you think, is this acceptable?
> >
Committed with a few tweaks, I hope I didn't break anything ;-)
Thanks!
--
Antoine
No comments:
Post a Comment