Re: Run script at boot time
On Fri, Mar 22, 2013 at 10:50:15AM +0000, Tony van der Hoff wrote:
> >
> <snip useful information re init.d>
>
> Unfortunately, that solution didn't seem to work.
>
> Indeed, in this instance, it doesn't matter when the script is run,
> except that the network must be running, so on the face of it, rc.local
> would fit the bill.
>
> I placed the line /usr/sbin/ltsp_update_sshkeys in /etc/rc.local, but
> after I rebooted, I needed to run it manually to set the host keys. I
> don't know whether the utility didn't run, or didn't run at the right
> time, or failed.
>
> Perhaps I should explain a bit about what I'm trying to achieve. LTSP is
> a thin-client server for Linux. After boot-up, the clients communicate
> over an ssh tunnel with the server, using a key-based authentication
> mechanism. After certain upgrades, it seems that these keys need
> resetting, for which LTSP provides the aforementioned utility.
>
> I don't understand why I need to run it, as the server has a static ip
> address, but some kernel upgrades also affect it. After a reboot, the
> terminal users start moaning about not being able to log in, and I have
> to run (as root) the utility. This is not always convenient, resulting
> in some downtime.
>
> My imagined solution was to run the utility after each boot-up, but as
> you see, no such luck. Ideally I'd prefer to fix the underlying need to
> update the host keys, but I've no idea where to start.
>
I use LTSP and I haven't had to update the keys in years. I vaguely
recall having to do it once, but I can't remember the reason. I update
my Debian Stable LTSP server daily, and even upgraded from Lenny to
Squeeze, and didn't need to update the keys.
Maybe you could try asking on the ltsp-discuss list.
To get your command to run, maybe you could try adding 'sleep 30s &&' to the
front of it just in case the system needs that time to get the network
up.
-Rob
Reply to: