rBuilder Talk:How to configure the automatic launching of installed services
From rPath Wiki
I created a package that I tried to launch on a AMI at Amazon EC2. Although the instance came up it appears that the SSHD was not responding. Whether it was part of the package or not, I couldn't be sure.
When network daemons are added to a package does the package configure them for automatic launching or are there some additional steps to be taken whe the daemons are added?added to t
- Voipfc 09:46, 16 November 2006 (EST)
- For a full index of all existing discussion topics, see Forum Topics.
- For instructions on using the rPath Wiki forums, see Forum Usage Instructions.
- For information on all recommended methods of communicating with rPath, see How to Communicate with rPath.
Comments
There's a howto for this at rPath Linux:Changing Service Startup Behavior HOWTO
With a few exceptions like dhcpd (can destabilize a network by starting automatically) and openldap (database initialized with excessively open permissions), services should now start by default.
The sshd service itself starts by default. You will need to ensure that it is included; you need (at a minimum) the openssh-server:runtime component (and its dependencies) included in your appliance.
Amazon EC2 is now directly supported
AMIs can now be directly generated and published to EC2. Please see the new documentation on this topic as well as the example appliances on rBuilder online. Bpja 02:15, 20 March 2007 (EDT)