> - "IFACE=eth0": shouldn't "net-device-up" wait for all interfaces to
have an ip address ?
>>No. That's the 'static-network-up' event, mentioned above. 'net-
device-up' is a per-device event.
I have another question then, for which device does the service wait when
'net-device-up' is used
> - "IFACE=eth0": shouldn't "net-device-up" wait for all interfaces to
have an ip address ?
>>No. That's the 'static-network-up' event, mentioned above. 'net-
device-up' is a per-device event.
I have another question then, for which device does the service wait when
'net-device-up' is used
> - "IFACE=eth0": shouldn't "net-device-up" wait for all interfaces to
have an ip address ?
No. That's the 'static-network-up' event, mentioned above. 'net-device-
up' is a per-device event.
> - "started nmbd": I wonder whether that should not be put per default
by the samba's installation
> - "IFACE=eth0": shouldn't "net-device-up" wait for all interfaces to
have an ip address ?
No. That's the 'static-network-up' event, mentioned above. 'net-device-
up' is a per-device event.
> - "started nmbd": I wonder whether that should not be put per default
by the samba's installation
With quite a delay :) (almost three years after), I had the same issue, on
14.04.3 LTS (GNU/Linux 3.19.0-33-generic x86_64).
After reading this bug and
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/596064
As a workaround, I set
"start on (local-filesystems and net-device-up IFACE=eth0
With quite a delay :) (almost three years after), I had the same issue, on
14.04.3 LTS (GNU/Linux 3.19.0-33-generic x86_64).
After reading this bug and
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/596064
As a workaround, I set
"start on (local-filesystems and net-device-up IFACE=eth0
This probably refers to the 'static-network-up' event.
In my case this maybe enough, as I use static configured network interfaces,
but what if smbd is bound to a interface using DHCP?
I did not check if this case will work. But I think smbd should handle binding
to static and dynamic
This probably refers to the 'static-network-up' event.
In my case this maybe enough, as I use static configured network interfaces,
but what if smbd is bound to a interface using DHCP?
I did not check if this case will work. But I think smbd should handle binding
to static and dynamic
A solution for the future can be the use of the network-services event.
It is mentioned in the upstart cookbook
(http://upstart.ubuntu.com/cookbook/#networkservices) and Bug #701576
also target the introduction of this event.
In the cookbook it is announced for 11.10.
I checked the existence of
On Tue, Dec 25, 2012 at 02:08:37PM -, Borim wrote:
I checked the existence of the network-services event with Ubuntu 12.10
by starting Ubuntu with the debug switch. But I can not find the
network-services event in /var/log/dmesg where all triggered events are
listed.
This probably refers
A solution for the future can be the use of the network-services event.
It is mentioned in the upstart cookbook
(http://upstart.ubuntu.com/cookbook/#networkservices) and Bug #701576
also target the introduction of this event.
In the cookbook it is announced for 11.10.
I checked the existence of
On Tue, Dec 25, 2012 at 02:08:37PM -, Borim wrote:
I checked the existence of the network-services event with Ubuntu 12.10
by starting Ubuntu with the debug switch. But I can not find the
network-services event in /var/log/dmesg where all triggered events are
listed.
This probably refers
What exactly did you set the start line to? It currently is set to
'start on (local-filesystems and net-device-up IFACE!=lo)'. If you drop
the 'local-filesystems' part, of course there will be problems with the
job starting before the filesystem is mounted.
as described here:
To be clear and recap--
smb.conf has the following
interfaces = eth0
Static IP was assigned via network manager.
smbd would not start up-- as per
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/836849
(open_socket_smbd fail)
As per this bug (the one i am currently updating), i edited the
What version of the samba package do you have installed? Your bug report
says you're running lucid, but the lucid version of the nmbd, upstart
job already includes code to handle creation of the /var/run/samba
directory.
--
You received this bug notification because you are a member of Ubuntu
And do you have the samba-common-bin package installed? If not, you're
seeing bug #572410 which was fixed in maverick.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/823878
Title:
What exactly did you set the start line to? It currently is set to
'start on (local-filesystems and net-device-up IFACE!=lo)'. If you drop
the 'local-filesystems' part, of course there will be problems with the
job starting before the filesystem is mounted.
as described here:
To be clear and recap--
smb.conf has the following
interfaces = eth0
Static IP was assigned via network manager.
smbd would not start up-- as per
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/836849
(open_socket_smbd fail)
As per this bug (the one i am currently updating), i edited the
What version of the samba package do you have installed? Your bug report
says you're running lucid, but the lucid version of the nmbd, upstart
job already includes code to handle creation of the /var/run/samba
directory.
--
You received this bug notification because you are a member of Ubuntu
And do you have the samba-common-bin package installed? If not, you're
seeing bug #572410 which was fixed in maverick.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/823878
Title:
bind interfaces
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: samba (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/823878
** Changed in: samba (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/823878
Title:
bind interfaces only requires a manual change to
After modifying 'net-device-up IFACE=eth0' to the 'start on' clause, i now am
running into the problem that /var/run/samba does not exist, as described here:
https://bugs.launchpad.net/ubuntu/lucid/+source/samba/+bug/596064
--
You received this bug notification because you are a member of
I'm sorry i wasn't clear in #6 -- samba now starts on boot, but nmbd
does not, for the reasons indicated in the above bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/823878
Title:
** Changed in: samba (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/823878
Title:
bind interfaces only requires a manual change to /etc/init/smbd.conf
To
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: samba (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/823878
Title:
bind
After modifying 'net-device-up IFACE=eth0' to the 'start on' clause, i now am
running into the problem that /var/run/samba does not exist, as described here:
https://bugs.launchpad.net/ubuntu/lucid/+source/samba/+bug/596064
--
You received this bug notification because you are a member of
I'm sorry i wasn't clear in #6 -- samba now starts on boot, but nmbd
does not, for the reasons indicated in the above bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/823878
Title:
bind
28 matches
Mail list logo
