I've recently had the pleasure of installing Fedora 8. Everything went fine except when I logout the services appear to stop, including http, tomcat, ssh and even ping.

I'm really not sure why this is as I've never come across this before. Any ideas?

log out? there is no way at all that a user level account can ever affect a service running on it, no chance. if you boot it up and don't log in, does apache work in the first place?

please open a terminal
login as root

and

if HTTPD is configured to start in each needed runlevel

ok I see. It's only on for runlevel 5 so I guess that would explain it. Thank you. I'll try to modify this once I get people off the machine.

Cheers,
Christopher

no, based on what you've said that wouldn't explain anything. level 5 just says "start apache. start ssh. start the X server", nothing in that level actually *depends* on X windows at all, let alone a users login to it.

So it would seem after some research. Any suggestions?

well you still need to define what the experience really is. what happens if you never log on at all for example?

If comp44 is the linux machine in question then:

While comp44 is off:
From another machine I visit http://comp44/ and receive a connection time out.

While comp44 is showing the login Screen immediatley after booting (no user has logged in):
From another machine I visit http://comp44/ and receive a connection time out. Even though I see httpd start "OK" during the boot up sequence:

If I login to comp44 a regular user:
From another machine I visit http://comp44/ and receive the Fedora Test Page. - apache is now running

If I logout so comp44 is showing the login screen:
From another machine I visit http://comp44/ and receive a connection time out. The same as before
.

What I don't understand is how this is happening. I'm not a complete n00b although this is making me feel like one. I don't even know where to begin looking so any suggestions to this would be welcome.

Again this issue is not specific to apache, I'm using this as an example as it was not installed/modified by myself after OS install.

Cheers
Christopher

ooh ooh ooh... it's not the services, it's the network being configured via nm-applet? bet you can't even ping it..? run system-config-network and ensure eth0 or whatever is lsited as starting on boot (also open /etc/sysconfig/network-scripts/ifcfg-eth0 and check for a line saying "ONBOOT=YES") and possibly also that the network service itself is listed as enabled in system-config-services

That's right I can't even ping it.

Woo thank you. All the configuration settings you mentioned were correct what was incorrect was my brain! I had configured the machine locally to be known as something different which I noticed whilst checking the settings you mentioned.

super. something pinged in my head... the network manager stuff is nice at times, but it's really confusing for the scope that it's at... it completely destroys and ignores other system configuration, like the startup scripts. needs work to avoid bizzare things like that.