*** This bug is a duplicate of bug 50430 ***
https://bugs.launchpad.net/bugs/50430
Please undo the duplicate status of this bug.
This bug still exists in Precise 12.04 and 12.04.1: when I start my
system autofs cannot see any maps that are stored in NIS.
--
You received this bug
*** This bug is a duplicate of bug 50430 ***
https://bugs.launchpad.net/bugs/50430
Please undo the duplicate status of this bug.
This bug still exists in Precise 12.04 and 12.04.1: when I start my
system autofs cannot see any maps that are stored in NIS.
--
You received this bug
*** This bug is a duplicate of bug 50430 ***
https://bugs.launchpad.net/bugs/50430
** Changed in: autofs (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
*** This bug is a duplicate of bug 50430 ***
https://bugs.launchpad.net/bugs/50430
** Changed in: autofs (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 50430 ***
https://bugs.launchpad.net/bugs/50430
Chuck, can you please undo the duplicate status of this bug? This is
NOT a duplicate of bug 50430
--
Autofs fails to start with maps from NIS
https://bugs.launchpad.net/bugs/213574
You received this bug
*** This bug is a duplicate of bug 50430 ***
https://bugs.launchpad.net/bugs/50430
Chuck, can you please undo the duplicate status of this bug? This is
NOT a duplicate of bug 50430
--
Autofs fails to start with maps from NIS
https://bugs.launchpad.net/bugs/213574
You received this bug
*** This bug is a duplicate of bug 50430 ***
https://bugs.launchpad.net/bugs/50430
I assume there's a conceptual bug, not to fix in any single package:
NetworkManager is basically incompatible with sysV init. This also
applies to sysV powered by upstart. Unless a consistent event-driven
model
I assume there's a conceptual bug, not to fix in any single package:
NetworkManager is basically incompatible with sysV init. This also
applies to sysV powered by upstart. Unless a consistent event-driven
model is in place NetworkManager may be fine for the occasional network-
hopping Laptop but
*** This bug is a duplicate of bug 50430 ***
https://bugs.launchpad.net/bugs/50430
On Tue, 2009-10-13 at 18:16 +, Chuck Short wrote:
*** This bug is a duplicate of bug 50430 ***
https://bugs.launchpad.net/bugs/50430
** This bug has been marked a duplicate of bug 50430
NIS has
*** This bug is a duplicate of bug 50430 ***
https://bugs.launchpad.net/bugs/50430
** This bug has been marked a duplicate of bug 50430
NIS has problems starting before the network comes up
--
Autofs fails to start with maps from NIS
https://bugs.launchpad.net/bugs/213574
You received
*** This bug is a duplicate of bug 50430 ***
https://bugs.launchpad.net/bugs/50430
On Tue, 2009-10-13 at 18:16 +, Chuck Short wrote:
*** This bug is a duplicate of bug 50430 ***
https://bugs.launchpad.net/bugs/50430
** This bug has been marked a duplicate of bug 50430
NIS has
I think many newer environments are switching from NIS to
ActiveDirectory (in Windows deployments) or LDAP, for both user account
info as well as things like automount.
I've never used a setup like that so I can't say whether it works better
or not with networkmanager.
Certainly it's ridiculous
Yep, Paul, that's how I'm perceiving this problem.
I'm not going stop using NIS anytime soon.. I have too many classic
machines that I have to use on my network including HPUX 10, Solaris
2.5.1 and FreeBSD 5.4
--
Autofs fails to start with maps from NIS
https://bugs.launchpad.net/bugs/213574
Hi Paul.
I was able to work around this - and the key is your comment:
It worked on Ubuntu, too, until network manager came along.
I uninstalled NM (apt-get remove).
Then manually configured my eth0 for DHCP and it works like a champ.
I did add that -no-dbus to the YPBINDARGS in
I have tried all of the workarounds I have seen so far:
- add scripts to restart autofs in if-up.d/if-down.d
- add -no-dbus to YPBINDARGS
- change the order in /etc/rc2.d (at least 2 varieties of this one)
None of these work for me.
Is there a known, reliable workaround for this yet?
Nope. Pretty sad. I guess no one at Canonical / Ubuntu cares much
about legacy UNIX environments based on NIS. RedHat, SuSE, etc. have
had this working out of the box for years and years. It worked on
Ubuntu, too, until network manager came along.
What I do on my systems is create a new
This is an important bug to me and anyone working with more than just a
single-user machine.
--
Autofs fails to start with maps from NIS
https://bugs.launchpad.net/bugs/213574
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The following fixes it for me in 8.10.
Basically, if you change the startup script sequence so that nis runs
after NetworkManager, you should be okay.
check what sequence number the NetworkManager startup script has:
ls /etc/rc2.d/*NetworkManager
/etc/rc2.d/S28NetworkManager
It should be 28.
I'm not so sure that's it. There's no NetworkManager in /etc/init.d at
all in 8.04, which I'm using, and it still has this problem.
--
Autofs fails to start with maps from NIS
https://bugs.launchpad.net/bugs/213574
You received this bug notification because you are a member of Ubuntu
Bugs,
I have 5 labs of computers previously running 7.04 with YP/autofs which
will be running 8.04 LTS this year. I found moving S18nis and S19autofs
to S40nis and S41autofs works. I think anywhere after S24dhcdbd might do
the trick but the 40's were otherwise unused so I put them there.
--
Autofs
** Changed in: autofs (Ubuntu)
Importance: Undecided = Low
--
Autofs fails to start with maps from NIS
https://bugs.launchpad.net/bugs/213574
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
: Autofs fails to start with maps from NIS
To: [EMAIL PROTECTED]
Date: Wednesday, September 3, 2008, 4:21 PM
Same problem here. After the system boots, autofs needs to
be manually
started.
--
Autofs fails to start with maps from NIS
https://bugs.launchpad.net/bugs/213574
You received
Same problem here. After the system boots, autofs needs to be manually
started.
--
Autofs fails to start with maps from NIS
https://bugs.launchpad.net/bugs/213574
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
It is a more general issue : autofs with network maps tends to not start
correctly with network manager. As a workaround, I use a script in
/etc/network/if-up.d :
8
#!/bin/sh
AUTOFS=/etc/init.d/autofs
if [ ! -x $AUTOFS ]; then
exit 0
fi
$AUTOFS start
I don't think adding this to if-up.d is robust. There could easily be a
timing issue here where the facility that distributes your maps, which
also cannot be started until the interface comes up, will not be started
before the autofs script asks for them. For example, with NIS, after
the
same problem here
--
Autofs fails to start with maps from NIS
https://bugs.launchpad.net/bugs/213574
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Note that using a local files is not a reasonable workaround for
enterprise environments... the whole point of using NIS is to centralize
management of the maps.
At the moment I cannot recommend Hardy to any environment that relies on
NIS distribution of automount maps (which is actually, as I
Yes I have been hitting the same problem, automount can't seem to use my
nis maps. I swtiched to using an auto.master and auto.home file setup
and everything sprung into life.
--
Autofs fails to start with maps from NIS
https://bugs.launchpad.net/bugs/213574
You received this bug notification
My problem is that nis doesn't seem to start at all, but if I wait until the
system is booted, and manually start NIS, it starts ok.
I have network manager installed, but I am using a fixed IP address for eth0
--
Autofs fails to start with maps from NIS
https://bugs.launchpad.net/bugs/213574
I too face the same problem in 8.04. my home directory doesn't get auto
mounted when I configure my system to use NIS.
Note : This functionality used to work in 7.10
I had to manually create auto.home to temporarily over come the problem.
It'd be good if this is fixed.
--
Autofs fails to start
30 matches
Mail list logo
