Re: [Planetlab-users] rc.vinit

[Scott K. <sc...@CS...>]

Hi Neil,

The contents of /etc/rc.vinit were a temporary measure
to get the keys installed.  In the next couple of days,
we will have an alternate method for doing this.

Your impressions are correct.  It should be called with
a "start" parameter on startup and a "stop" parameter
on shutdown (with the caveat that a call on shutdown is
best effort and not guaranteed).

Scott


On Thu, Jan 08, 2004 at 02:07:45PM -0800, Neil Spring wrote:
> rc.vinit on new slices has the following contents:
> 
> [uw_nspring@planetlab3 log]$ cat /etc/rc.vinit
> #!/bin/sh
> /etc/ssh/fetch_keys
> 
> Although I'd prefer to have my very own file for managing what should 
> be started on my slice, I recognize the attractiveness of reusing the 
> rc.vinit mechanism for slice management.  I have two questions, though.
> 
> First, it was my impression that rc.vinit would be called with "start" 
> as a parameter on startup, and "stop" as a parameter on a graceful 
> shutdown.  I am starting to doubt that, as this rc.vinit would try to 
> populate authorized_keys on startup and shutdown.  Should I continue to 
> expect "start" to be the first parameter?  Or was I mistaken?
> 
> Second, how likely is it that planetlab will want to modify rc.vinit?  
> I think it would be better to make /etc/rc.vinit instead be:
> 
> #!/bin/sh
> # do not modify this file, as planetlab may change it.
> /etc/ssh/fetch_keys
> # other initialization code may go here
> test -e /etc/rc.vinit.local && /bin/sh /etc/rc.vinit.local $1
> 
> and instruct users like me to write rc.vinit.local.
> 
> -neil