Please don't comment on bugs which have been closed.
I think bug 1007273 is probably the issue you are all seeing - please
can you help out by providing good feedback on symptoms you are seeing
with regards to this issue.
Once we have identified what the issue is we can then work on fixing it.
-
Fix does not work.
I have the latest version for autofs and ypbind and I have to manually
restart autofs everytime after login.
autofs is not able to read configuration files from ypbind during boot.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I just wanted to comment that I find it troubling that this bug is closed and
has low urgency. I am not a developer, just a user.
My company runs a small computer lab for our clients, it is used by 150+ users.
It uses NIS for it's logins and NFS for the user's home directories. Any time
that
On Thu, 2012-05-03 at 06:14 +, dm wrote:
> No, it doesn't work. I have to restart ypbind before login. The same
> bug arises some weeks before in 11.10 and was fixed after 2 weeks. The
> bug is very annoying. Please fix it soon. I'm using a rather up to date
> system (12.04 with latest patches
No, it doesn't work. I have to restart ypbind before login. The same
bug arises some weeks before in 11.10 and was fixed after 2 weeks. The
bug is very annoying. Please fix it soon. I'm using a rather up to date
system (12.04 with latest patches).
--
You received this bug notification because yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22/03/12 17:02, kenjo wrote:
> On Thu, 2012-03-22 at 15:06 +, James Page wrote:
>> kenjo
>>
>> autofs does not need to do this - its already done by the
>> start-ypbind configuration.
>
> ok then I said it before upstart is a complete myster
On Thu, 2012-03-22 at 15:06 +, James Page wrote:
> kenjo
>
> autofs does not need to do this - its already done by the start-ypbind
> configuration.
ok then I said it before upstart is a complete mystery to me.
so when autofs is started start-ypbind is actually blocking autofs ??
and only wh
kenjo
autofs does not need to do this - its already done by the start-ypbind
configuration.
the above does work (and is what start-ypbind does) - its just
supplementary and not required.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I do not understand this fix.
autofs needs to wait for ypbind to be able to get the auto.master map
file out of nis.
So what is preventing autofs from starting before it can read out the
auto.master file ?
is the runlevel waiting on ypbind ?? I simply don't understand how to get
upstart to te
autofs5 (5.0.6-0ubuntu5) precise; urgency=low
* d/autofs5.autofs.upstart: Drop wait-for-state from configuration as
waiting for NIS to start is already handled in the NIS package by
the start-ypbind upstart configuration which supports autofs
(LP: #958704).
Marking 'Fixed Released'.
I think this a bug 962001 might be the same issue.
The latest update to autofs uses a new upstart feature called wait-for-
state to coordinate between ypbind and autofs - I think its targetting
the wrong state causing autofs not to start.
** Changed in: autofs (Ubuntu)
Importance: Undecided =>
Confirmed - I think that the wait-for-start in the autofs configuration
is not required - this is already handled by the start-ypbind
configuration which waits for ypbind to get to running start before
autofs will startup - and will correctly detect if its already running.
--
You received this bu
Main problem for delays is actually the network.
I added eth0 in /etc/network/interfaces and now there is no delay at
boot.
autofs is still not started and I have to do
start autofs
and in another terminal
restart ypbind
to make autofs actually start.
then I can
start lightdm
then I can login
13 matches
Mail list logo
