I recently setup my desktop as a diskless thick client running off the network, to cut down on local noise and the need for an extra HDD. Almost everything worked (damn my PC is quiet now!) and I am able to boot up and use the system fine but I cannot shut down without it generating errors.
I'm pretty sure as to what the cause is - the network services are killed in the middle of the shutdown procedure so the steps which follow no longer have access to the drive to safely stop. I tried changing the order in which to stop services but I don't know what all of them do so could not improve on the situation beyond delaying the error during shutdown. I get a few more services to stop properly before the network is cut and the rest of the procedure blows up.
What would be the proper order and run levels that I should stop services in to safely shutdown a disk less client?.. or would I have to change something else to make this work?
I started out with linux about a month or two ago so I'm still very new.
Thanks for any help.
I'm pretty sure as to what the cause is - the network services are killed in the middle of the shutdown procedure so the steps which follow no longer have access to the drive to safely stop. I tried changing the order in which to stop services but I don't know what all of them do so could not improve on the situation beyond delaying the error during shutdown. I get a few more services to stop properly before the network is cut and the rest of the procedure blows up.
What would be the proper order and run levels that I should stop services in to safely shutdown a disk less client?.. or would I have to change something else to make this work?
I started out with linux about a month or two ago so I'm still very new.
Thanks for any help.