Hi,

The script did not run on "start on startup", only on "start on filesystem"
setting. Still, the /etc/init/rc.conf was not processed.
BTW, my system does not hang, it starts ssh properly.

Could it be related to duplicate mounts reported by df? :
*r...@master2:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs               909177556 871911312  37266244  96% /
/dev/mapper/pl-srv   909177556 871911312  37266244  96% /
none                   3057772       272   3057500   1% /dev/console
none                   3057772       272   3057500   1% /dev/tty1
none                   3057772       272   3057500   1% /dev/tty2
none                   3057772       272   3057500   1% /dev/tty3
none                   3057772       272   3057500   1% /dev/tty4
none                   3057772       272   3057500   1% /dev
none                   3062604         0   3062604   0% /dev/shm
none                   3062604        20   3062584   1% /var/run
none                   3062604         0   3062604   0% /var/lock
none                   3062604         0   3062604   0% /lib/init/rw*

Neither /etc/fstab of the container, nor lxc.conf file specify mounting of
the /var/run filesystem (which I heard to be problematic for LXC
containers).

--
Arie



On Wed, Jan 12, 2011 at 16:49, Serge E. Hallyn
<serge.hal...@canonical.com>wrote:

> Quoting Arie Skliarouk (sklia...@gmail.com):
> > I have the same problem as the original poster. A lucid container boots
> and
> > ssh is started, but nothing else:
> >
> > *r...@master2:~# ps awx
> >   PID TTY      STAT   TIME COMMAND
> >     1 ?        Ss     0:00 /sbin/init
> >    34 ?        S      0:00 upstart-udev-bridge --daemon
> >    50 ?        S<s    0:00 udevd --daemon
> >    94 ?        Ss     0:00 /usr/sbin/sshd
> >   111 ?        Ss     0:00 sshd: r...@pts/134
> >   125 pts/134  Ss     0:00 -bash
> >   137 pts/134  R+     0:00 ps awx*
> >
> > How can I make upstart to start other services, especially the
> > /etc/init/rc.conf one?
>
> If you look at the /usr/lib/lxc/templates/lxc-ubuntu that ships
> with lxc, it installs a /etc/init/lxc.conf which kicks the boot
> along.  It sends two upstart events, but in some testing last
> night my boot continued fine without those - what was absolutely
> essential was the
>
>        rm -rf /var/run/*.pid
>        rm -rf /var/run/network/*
>
> Without those, my boot hung.
>
> So you should be able to create any /etc/init/kickme.conf, just
> make sure it has:
>
> description "kick upstart"
> start on startup
> script
>        rm -rf /var/run/*.pid
>        rm -rf /var/run/network/*
> end script
>
> -serge
>
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Reply via email to