maverick meerkat and samba

johnh10000 · 11-17-2010, 12:51 PM

ok, now everytime I restart my maveric box I have to

Code:

root@tux:~# start smbd
smbd start/running, process 16067
root@tux:~#

oh and stop firestarter. Ok the firewall issue, is probably simple. I am more concerned that an upstart task won't start.

I have checked in boot-up manager, and it is asked to start.

This was an upgrade from Lucid, where I hadno problems.

Help! Any logs you people may need, ask and they will be provided.

frankbell · 11-17-2010, 08:35 PM

Sounds like a job for rc.local, except Ubuntu doesn't have rc.local.

This might help:

https://help.ubuntu.com/community/RcLocalHowto

johnh10000 · 11-17-2010, 10:47 PM

Quote:

Originally Posted by frankbell

Sounds like a job for rc.local, except Ubuntu doesn't have rc.local.

This might help:

https://help.ubuntu.com/community/RcLocalHowto

thanks will look into that when I get up proper! <yawn>

johnh10000 · 11-18-2010, 06:00 AM

It now seems that it is my firewall. It is managing to start.

See if you can see anything wrong with my setup?

Sorry if I seem cross, I am, with a win7 box!!

frankbell · 11-18-2010, 08:38 PM

I have run into problems like this. I'm not a firewall expert. I just bumble along until I get it working. I had an rc.firewall script once that was real kludge, but it worked.

Currently, I have Firestarter configured to allow Samba service for everyone and permit inbound for my network as 192.168.1.0/255.255.255.0 and it's working like a charm on my Debain box, but I have had situations where the exact same combination has not worked and I've had to enter each (likely) host manually (it's a small home network so there's not many dchp addresses that are likely to be used).

Here's my current configuration, in case it helps.

You might take a look at the allow-from and allow-service files in /etc/firestarter/inbound/ to make sure they properly reflect the configuration in the GUI. I can't see how they wouldn't but it's something to check.

Noway2 · 11-19-2010, 04:35 AM

I ran into a problem once upon an upgrade where a few applications like SAMBA wouldn't start. I never found a really satisfying answer. The theory was that these are applications that require networking to be available upon their start up and will terminate if it is not and with the upgrade, networking may be delayed slightly. The 'fix' was to change the start number (Sxx) in the rc script for the run level. I moved them up to a higher number and all became well.

johnh10000 · 11-19-2010, 05:11 AM

Quote:

Originally Posted by Noway2

I ran into a problem once upon an upgrade where a few applications like SAMBA wouldn't start. I never found a really satisfying answer. The theory was that these are applications that require networking to be available upon their start up and will terminate if it is not and with the upgrade, networking may be delayed slightly. The 'fix' was to change the start number (Sxx) in the rc script for the run level. I moved them up to a higher number and all became well.

reasnoble ans, but samba from lucid on, is now an "upstart" job , not init.d ...

As I mentioned yday, its my fire wall that is the issue not samba.

thanks for your reply non the less!