Click to See Complete Forum and Search --> : Setting-up Samba of Fedora Core 4


anteaus
07-11-2005, 10:29 AM
Hi there,

I am trying to set up samba on my pc.After I have set-up the users and shares and rebooted the system,
I get the followng error during the bootup process

Start smb services /etc/init.d/functions: line 83:2032 aborted $nice $#

Note: I did not even touch that particular file of folder.
In fact, I even installed Fedora Core 4 into another pc, but alas, the same
error occured.

With this error, I can only see the Server but is unable to see any of the shared resources.

Can someone pls lend me a hand.


Thks

Anteaus

teyon
07-11-2005, 12:10 PM
more info plz. did you install the samba packages off the cd or did you compile them from source?

i have samba running on my fc4 system and upgraded to 3.0.14 via yum. both the original installed packag and the updated one haven't given me any issues. although im only using it for file sharing purposes not to emulate a nt server.

anteaus
07-11-2005, 08:19 PM
The Samba was installed directly from the cd

Thks

teyon
07-12-2005, 01:35 PM
anteaus,

i dont have my fedora 4 system here with me its back at home so im a little shorthanded. so it looks like you have the stentz set of fc4 installed with the stock samba, same as me.

if anything would be preventing samba to startup off the stock install it would be selinux. on my own machine i disabled it since i didn't feel like tinkering with the targeting policy as of yet. and since im unable to test my theory since i dont have my fedora machine you'll have to try it.

disable that feature, reboot, and then try samba again. you'll need to edit the file /etc/selinux/config using a editor of choice, and change the entry "SELINUX=Enable" to "SELINUX=Disable"

hopefully thats all there is to it and if you want to keep using selinux you'll 'get' to experience the joy of configuring the nsa's little security feature. i hadn't bothered to learn it yet myself which is why i turned it off to begin with.

anteaus
07-16-2005, 10:33 AM
Hi Teyon,

Thanks very much for your valuable piece of advice.
SELINUX was the culprit.
I disabled it via Desktop-system settings-security level-SELINUX-Enforcing-Disabled

Once again, Thanks very much