restarting network service brought system down

[zak_wang]

I made changes to the network configuration and open the "services" window to restart network service and networkmanager service. My whole system stopped responding to me after I clicked the restarted button.

I took it as an accident and forced off power. I tried again to stop network service to see if it goes wrong again. And yes it didn't disappoint me... I tried it in several different cases later to check whether the online status conflicts with the restart operation but the answer is no. It let me down every time I click the restart button.

I restarted network service successfully in F8 before and currently I am running F9. Is there any restricts on using network service that forbids restarting after boot? Or is it caused by something I can't see?

I wondered if I should post this in the network section but I thought it was more like a general problem. Anybody has any clues?

[Jake]

It could be possible, that it is the service manager program that is causing it. Try doing it via terminal.

How:

su -
password:
service network restart

[zak_wang]

It is impossible for me to use commands like service and ifconfig under the ordinary account even if I typed su and password to get the super privilege. The terminal simply returns command not found. That's why I resorted to service manager. And I tried to start and stop and restart the cups service. All done successfully without errors. So I guess it might be another issue than the problem of service manager.

[scottro]

That's explained at http://home.nyc.rr.com/computertaijutsu/rhpath.html

That will be changing in F10, by the way, the /sbin commands will be in a normal user's path.

[Jake]

Originally Posted by zak_wang

It is impossible for me to use commands like service and ifconfig under the ordinary account even if I typed su and password to get the super privilege. The terminal simply returns command not found. That's why I resorted to service manager. And I tried to start and stop and restart the cups service. All done successfully without errors. So I guess it might be another issue than the problem of service manager.

Type "su -" iinstead of "su". then try it.

[zak_wang]

Originally Posted by JakeS

Type "su -" iinstead of "su". then try it.

this is great thanks.
long way to go.

[zak_wang]

Originally Posted by scottro

That's explained at http://home.nyc.rr.com/computertaijutsu/rhpath.html

That will be changing in F10, by the way, the /sbin commands will be in a normal user's path.

This makes a lot of sense. But with this change taking place, will the security level be reduced for that a normal user could give out super commands?

[zak_wang]

Back to my topic.
I typed service network restart and hit enter. Then, below is what happened before I forced shut my computer just now (I can't remember clearly but the last line is correct) :

shutting off eth0
stopping network service
starting network service
bringing(or starting? I'm not sure) up eth0

and then everything caaaaa..... Nothing recognize me as its friend. Crash. Stop.
Sounds like something weired?

[Jake]

That is strange. very strange, does your entire system lock up? including unable to move mouse? does ctrl alt F1(or F4) take you to run level 3? or is it completely locked?

Also, when you save network configuration, can you restart your system instead of restarting service? because it sounds like it might be your changes that are killing it. I think this because the system does not hang when you boot up initially when it starts the network service.

[zak_wang]

right. my entire system was locked up. no mouse move. no key pressed event. no virtual terminal.
but everything is fine to reboot. i tried afterwards to restart service without making changes to network. and it still happened.
if there is no solution... i would go for F10.

[marko]

Originally Posted by zak_wang

This makes a lot of sense. But with this change taking place, will the security level be reduced for that a normal user could give out super commands?

No, the usual protections will stay in place

[zak_wang]

Originally Posted by marko

No, the usual protections will stay in place

That would be great.

[zak_wang]

but what about the service problem.
Does it look familiar to somebody?

[Jake]

I have never seen this problem before, though it does make me curious as to what could cause it. the fact the service starts perfectly fine when you boot, but then your system locks up if you do it manually is weird. Normally something like this could be down to a driver, but the fact it starts up in the first place tells me otherwise. Hmm, what happens if you disable the auto start of the service at boot, so when you boot it doesn't start the network. And then manually start it when logged in?

[zak_wang]

I'm not taking my laptop with me today so I can't execute what you suggested. But I thought of something that might help you get out of the puzzle and then take me out of it too:

1. I have NetworkManager service enabled and running, controlling eth0(wired), which is the only way that I could get internet access, while leaving eth1(wireless) uncontrolled.

2. Network service is disabled. However, it is alive running.