[Bug 569757] Re: NIS upstart dependancy broken for lucid
Hopefully this works. I'm attaching a working nis.conf and nis- wait.conf based on the comments so far. Put the files in /etc/init and that should be all that's necessary for most configurations. You shouldn't even need to remove the /etc/rc?.d nis links since it should just determine it's already started and exit. The start line I used in nis.conf is based on the ypbind.conf file that Paul Elliott wrote, but the rest of the script is from Clint Byrum's suggestion. I also modified the nis-wait.conf to include cron and atd. No, this isn't a perfect answer, but it works for me. I don't know if it's a complete enough suggestion to cover Maciej Puzio's case but it might be. ** Attachment added: NIS upstart job https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+attachment/2070218/+files/nis.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
** Attachment added: NIS-wait upstart job https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+attachment/2070219/+files/nis-wait.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
Hopefully this works. I'm attaching a working nis.conf and nis- wait.conf based on the comments so far. Put the files in /etc/init and that should be all that's necessary for most configurations. You shouldn't even need to remove the /etc/rc?.d nis links since it should just determine it's already started and exit. The start line I used in nis.conf is based on the ypbind.conf file that Paul Elliott wrote, but the rest of the script is from Clint Byrum's suggestion. I also modified the nis-wait.conf to include cron and atd. No, this isn't a perfect answer, but it works for me. I don't know if it's a complete enough suggestion to cover Maciej Puzio's case but it might be. ** Attachment added: NIS upstart job https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+attachment/2070218/+files/nis.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
** Attachment added: NIS-wait upstart job https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+attachment/2070219/+files/nis-wait.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
atd is another one that needs to wait for ypbind. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
atd is another one that needs to wait for ypbind. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
Re: the linked branch, here is a quick review of things I'd suggest changing: * I understand that the package doesn't use debhelper. But to repeat all of the hard work that has gone into dh_installinit would be asking for bugs later. So you'd also need to add debhelper to the build-depends. After that add a call to dh_installinit and the #DEBHELPER# tag to the end of postinst. Also if you do this, the files are named incorrectly. Rename *.conf to nis.*.upstart . This will trigger dh_installinit to do its magic. Then you can remove all of the lines that install the upstart files in /etc/init. * start/stop/reload/restart $job in maintainer scripts is going to cause issues. You should at the very least use invoke-rc.d, per Debian Policy 9.3.3. Further, this is all handled by dh_installinit... * the removal of the old /etc/init.d/nis may accidentally remove the user's local changes to said file, which is in fact a conffile and so must be handled delicately. dh_installinit handles this as well, as long as you don't pass --upstart-only, which you wouldn't as that is only for things that are upstart specific (like wait jobs). * default env values can and should be set with env stanzas.. so instead of putting START_YPBIND=false in the first lines of pre- start.. just put env START_YPBIND=false in the upstart job. This is really just a nit.. as this just makes the job run a tiny bit faster (these variables are parsed out at job load time by upstart instead of by the shell). * changelog target should be natty since we'll have to fix this there first. * Given the previous discussions, each of these needs a wait job that is started and waited for by anything needing NIS. One easy way to get most of the jobs out there is by blocking runlevel 2. This would work: # ypbind-wait start on starting rc RUNLEVEL=2 stop on started ypbind or stopped ypbind env WAITER= instance $WAITER$UPSTART_EVENTS task normal ext 2 script ... normal wait job stuff The instance argument allows anything that is started before runlevel 2 to block on ypbind as well by doing: start ypbind-wait WAITER=autofs This will work as a stop gap until we solve the issue more elegantly with exported variables and a generic waiter job. ** Tags added: upstart -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
Re: the linked branch, here is a quick review of things I'd suggest changing: * I understand that the package doesn't use debhelper. But to repeat all of the hard work that has gone into dh_installinit would be asking for bugs later. So you'd also need to add debhelper to the build-depends. After that add a call to dh_installinit and the #DEBHELPER# tag to the end of postinst. Also if you do this, the files are named incorrectly. Rename *.conf to nis.*.upstart . This will trigger dh_installinit to do its magic. Then you can remove all of the lines that install the upstart files in /etc/init. * start/stop/reload/restart $job in maintainer scripts is going to cause issues. You should at the very least use invoke-rc.d, per Debian Policy 9.3.3. Further, this is all handled by dh_installinit... * the removal of the old /etc/init.d/nis may accidentally remove the user's local changes to said file, which is in fact a conffile and so must be handled delicately. dh_installinit handles this as well, as long as you don't pass --upstart-only, which you wouldn't as that is only for things that are upstart specific (like wait jobs). * default env values can and should be set with env stanzas.. so instead of putting START_YPBIND=false in the first lines of pre- start.. just put env START_YPBIND=false in the upstart job. This is really just a nit.. as this just makes the job run a tiny bit faster (these variables are parsed out at job load time by upstart instead of by the shell). * changelog target should be natty since we'll have to fix this there first. * Given the previous discussions, each of these needs a wait job that is started and waited for by anything needing NIS. One easy way to get most of the jobs out there is by blocking runlevel 2. This would work: # ypbind-wait start on starting rc RUNLEVEL=2 stop on started ypbind or stopped ypbind env WAITER= instance $WAITER$UPSTART_EVENTS task normal ext 2 script ... normal wait job stuff The instance argument allows anything that is started before runlevel 2 to block on ypbind as well by doing: start ypbind-wait WAITER=autofs This will work as a stop gap until we solve the issue more elegantly with exported variables and a generic waiter job. ** Tags added: upstart -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
On my mail server postfix and dovecot depend on nis. Currently this particular dependency is handled properly, because all three daemons are started by means of /etc/rc?.d in the correct order. Please correct me if I am wrong, but I worry that the solution suggested by Clint Byrum in #18 might cause nis to race with postfix or, if postfix is converted to native upstart, with dovecot. Anyway, the start condition for nis-wait would have to be extended to list all possible nis dependencies, and there could be plenty of them, seeing that nis provides very basic system information such as users, groups, etc. So we would have start on starting gdm or starting autofs or starting postfix or starting dovecot or starting kdeinit4 or starting ..., and so on. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 569757] Re: NIS upstart dependancy broken for lucid
On Feb 7, 2011, at 4:03 PM, Maciej Puzio 569...@bugs.launchpad.net wrote: On my mail server postfix and dovecot depend on nis. Currently this particular dependency is handled properly, because all three daemons are started by means of /etc/rc?.d in the correct order. Please correct me if I am wrong, but I worry that the solution suggested by Clint Byrum in #18 might cause nis to race with postfix or, if postfix is converted to native upstart, with dovecot. Right, good point. I've been monkeying with this, and i think the real need is to be able to make sure that anything that needs access to users and groups is blocked by nis, or ldap, or winbind, or puppet... Whatever you use to provide users and groups, has to run first. The appropriate thing to do is to Develop a policy of variable exporting in upstart jobs. env NEEDS_ID=1 export NEEDS_ID adding that to all the services that need Ident would be awfully painful. But having the generic network-services job that has been proposed set it would allow us to just have postfix follow that job, and have nis, winbind, etc use start on starting NEEDS_ID=1 If something else like autofs needs to start before generic network services it will have to export this variable. This decouples the consumers and providers. -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid Status in “nis” package in Ubuntu: Triaged Bug description: Binary package hint: nis NIS does not work on lucid: without upstart, it starts anytime, unrelated to net-device-up events. If the passwd/shadow is provided through NIS, it seems completly random, whether username resolution is provided to gdm. The only fix seems an upstart startscript. To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscribe -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
On my mail server postfix and dovecot depend on nis. Currently this particular dependency is handled properly, because all three daemons are started by means of /etc/rc?.d in the correct order. Please correct me if I am wrong, but I worry that the solution suggested by Clint Byrum in #18 might cause nis to race with postfix or, if postfix is converted to native upstart, with dovecot. Anyway, the start condition for nis-wait would have to be extended to list all possible nis dependencies, and there could be plenty of them, seeing that nis provides very basic system information such as users, groups, etc. So we would have start on starting gdm or starting autofs or starting postfix or starting dovecot or starting kdeinit4 or starting ..., and so on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 569757] Re: NIS upstart dependancy broken for lucid
On Feb 7, 2011, at 4:03 PM, Maciej Puzio 569...@bugs.launchpad.net wrote: On my mail server postfix and dovecot depend on nis. Currently this particular dependency is handled properly, because all three daemons are started by means of /etc/rc?.d in the correct order. Please correct me if I am wrong, but I worry that the solution suggested by Clint Byrum in #18 might cause nis to race with postfix or, if postfix is converted to native upstart, with dovecot. Right, good point. I've been monkeying with this, and i think the real need is to be able to make sure that anything that needs access to users and groups is blocked by nis, or ldap, or winbind, or puppet... Whatever you use to provide users and groups, has to run first. The appropriate thing to do is to Develop a policy of variable exporting in upstart jobs. env NEEDS_ID=1 export NEEDS_ID adding that to all the services that need Ident would be awfully painful. But having the generic network-services job that has been proposed set it would allow us to just have postfix follow that job, and have nis, winbind, etc use start on starting NEEDS_ID=1 If something else like autofs needs to start before generic network services it will have to export this variable. This decouples the consumers and providers. -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid Status in “nis” package in Ubuntu: Triaged Bug description: Binary package hint: nis NIS does not work on lucid: without upstart, it starts anytime, unrelated to net-device-up events. If the passwd/shadow is provided through NIS, it seems completly random, whether username resolution is provided to gdm. The only fix seems an upstart startscript. To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
I wanted to add cron to the list of things that have a race condition with NIS on startup, as I don't think cron has been mentioned in any of the other postings on this issue. If a NIS user has installed a crontab on a NIS client, and NIS has not started by the time cron starts, the result is that user's crontab will be ignored (the condition is logged in the system logs). The user then has to manually resubmit the crontab before cron will reconsider it. Regards, Jim. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
I wanted to add cron to the list of things that have a race condition with NIS on startup, as I don't think cron has been mentioned in any of the other postings on this issue. If a NIS user has installed a crontab on a NIS client, and NIS has not started by the time cron starts, the result is that user's crontab will be ignored (the condition is logged in the system logs). The user then has to manually resubmit the crontab before cron will reconsider it. Regards, Jim. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
So, a couple of points regarding this bug.. Re: Wishlist .. I have to agree that this is a regression from the previous LTS, and that it is caused by a race condition. Race conditions are hard to reproduce without introducing something synthetic to slow one of the racers down, but in this case, its clear, nis must delay the start up of a few things like gdm and autofs. I'm raising that to High since nis users really can't be sure their system will boot properly. Re: moving everything into upstart. This should be done, and on cursory examination, the linked branch looks like it is on the right track. However, doing so in an LTS as an SRU is highly invasive. We can possibly use a similar trick as we used for statd and portmap to block at a certain point in the boot until nis is started, by removing it from /etc/rc#.d and adding two upstart jobs: # nis start on runlevel [2345] pre-start exec /etc/init.d/nis start post-stop exec /etc/init.d/nis stop #EOF # nis-wait start on starting gdm or starting autofs stop on started nis or stopped nis task normal exit 2 instance $JOB script status nis | grep -q 'start/running' exit 0 start nis || true logger -t nis-wait -p daemon.info blocking $JOB until nis starts... sleep 3600 end script #EOF Since this only affects Ubuntu, and I think the problem is well understood, I'm setting the status to Triaged. ** Changed in: nis (Ubuntu) Status: Confirmed = Triaged ** Changed in: nis (Ubuntu) Importance: Wishlist = High ** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
So, a couple of points regarding this bug.. Re: Wishlist .. I have to agree that this is a regression from the previous LTS, and that it is caused by a race condition. Race conditions are hard to reproduce without introducing something synthetic to slow one of the racers down, but in this case, its clear, nis must delay the start up of a few things like gdm and autofs. I'm raising that to High since nis users really can't be sure their system will boot properly. Re: moving everything into upstart. This should be done, and on cursory examination, the linked branch looks like it is on the right track. However, doing so in an LTS as an SRU is highly invasive. We can possibly use a similar trick as we used for statd and portmap to block at a certain point in the boot until nis is started, by removing it from /etc/rc#.d and adding two upstart jobs: # nis start on runlevel [2345] pre-start exec /etc/init.d/nis start post-stop exec /etc/init.d/nis stop #EOF # nis-wait start on starting gdm or starting autofs stop on started nis or stopped nis task normal exit 2 instance $JOB script status nis | grep -q 'start/running' exit 0 start nis || true logger -t nis-wait -p daemon.info blocking $JOB until nis starts... sleep 3600 end script #EOF Since this only affects Ubuntu, and I think the problem is well understood, I'm setting the status to Triaged. ** Changed in: nis (Ubuntu) Status: Confirmed = Triaged ** Changed in: nis (Ubuntu) Importance: Wishlist = High ** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
How should I go about compiling the packages in the branched repo? I'd like to give them a try, but I've never rolled debian packages before. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
How should I go about compiling the packages in the branched repo? I'd like to give them a try, but I've never rolled debian packages before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
I agree with #15 -- this needs to be fixed in ASAP (and it should be fixed in the LTS version!) I'm responsible for a whole network that relies entirely on the NIS+autofs functionality (home folders, backups, cluster nodes, etc.) If this doesn't work, then it causes all kinds of unforeseen problems. I have a large number of servers that I want to upgrade to Lucid, but I'm reluctant to do this just because of this problem. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
I agree with #15 -- this needs to be fixed in ASAP (and it should be fixed in the LTS version!) I'm responsible for a whole network that relies entirely on the NIS+autofs functionality (home folders, backups, cluster nodes, etc.) If this doesn't work, then it causes all kinds of unforeseen problems. I have a large number of servers that I want to upgrade to Lucid, but I'm reluctant to do this just because of this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
Why is this bug only wishlist? NIS not working properly is a problem in its own right, but the fact that NIS has not been converted to upstart *also* causes problems with autofs - see https://bugs.launchpad.net/ubuntu/+source/nis/+bug/570513 (which is exactly what has bitten us after the upgrade from Hardy). There are still quite a few set-ups (e.g. in small companies) using NIS+autofs and compared to the previous LTS version (Hardy) this is a regression in my opinion. Hence, I would like to add my vote to the necessity of an SRU - this should definitely be fixed in Lucid, given that Lucid is LTS. -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
Why is this bug only wishlist? NIS not working properly is a problem in its own right, but the fact that NIS has not been converted to upstart *also* causes problems with autofs - see https://bugs.launchpad.net/ubuntu/+source/nis/+bug/570513 (which is exactly what has bitten us after the upgrade from Hardy). There are still quite a few set-ups (e.g. in small companies) using NIS+autofs and compared to the previous LTS version (Hardy) this is a regression in my opinion. Hence, I would like to add my vote to the necessity of an SRU - this should definitely be fixed in Lucid, given that Lucid is LTS. -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
is this patch being integrated in 10.10? -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
is this patch being integrated in 10.10? -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
** Branch linked: lp:~omahn/ubuntu/lucid/nis/nis-fix-569757 -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
Branch added that switches to upstart for the NIS package in Maverick. We've had a version of this branch running locally for a couple of months now with no known issues although we are only using the client side of the package. I've done very limited testing of the server side. Feedback appreciated. -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
** Branch linked: lp:~omahn/ubuntu/lucid/nis/nis-fix-569757 -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
Branch added that switches to upstart for the NIS package in Maverick. We've had a version of this branch running locally for a couple of months now with no known issues although we are only using the client side of the package. I've done very limited testing of the server side. Feedback appreciated. -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
In my setup this bug causes excessive boot delays. I want to question the wishlist importance. -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
In my setup this bug causes excessive boot delays. I want to question the wishlist importance. -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
Emil, rather than remove, it would probably be safer to just rename the /etc/init.d/nis script to prevent it firing. We have a local package here with the necessary changes and it appears to work fine. After a bit more testing I'll upload for others to review. -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
Emil, rather than remove, it would probably be safer to just rename the /etc/init.d/nis script to prevent it firing. We have a local package here with the necessary changes and it appears to work fine. After a bit more testing I'll upload for others to review. -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
To test these scripts, you should also remove /etc/init.d/nis, correct? -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
To test these scripts, you should also remove /etc/init.d/nis, correct? -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
** Attachment added: ypbind upstart script http://launchpadlibrarian.net/50135877/ypbind.conf -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
** Attachment added: yppasswd upstart script http://launchpadlibrarian.net/50135878/yppasswdd.conf -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
** Attachment added: ypserv upstart script http://launchpadlibrarian.net/50135885/ypserv.conf -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
** Attachment added: ypxfrd upstart script http://launchpadlibrarian.net/50135892/ypxfrd.conf -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
Please find attached my first attempt at converting the nis init script to upstart jobs. Please can others review and let me know how these look? I've tested the client side (with ypbind) here and that works well. I've done very little testing with the server components other than checking they startup ok with the upstart jobs. -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
** Attachment added: ypbind upstart script http://launchpadlibrarian.net/50135877/ypbind.conf -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
** Attachment added: yppasswd upstart script http://launchpadlibrarian.net/50135878/yppasswdd.conf -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
** Attachment added: ypserv upstart script http://launchpadlibrarian.net/50135885/ypserv.conf -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
** Attachment added: ypxfrd upstart script http://launchpadlibrarian.net/50135892/ypxfrd.conf -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
Please find attached my first attempt at converting the nis init script to upstart jobs. Please can others review and let me know how these look? I've tested the client side (with ypbind) here and that works well. I've done very little testing with the server components other than checking they startup ok with the upstart jobs. -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
Ted: This is plain lucid, I'm not using custom upstart scripts at all. -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
Ahh, so you haven't implemented this? The only fix seems an upstart startscript. -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
Ted: This is plain lucid, I'm not using custom upstart scripts at all. -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
Ahh, so you haven't implemented this? The only fix seems an upstart startscript. -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
harald, can you describe the upstarts startscript you're using? This bug is burning me too. -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
harald, can you describe the upstarts startscript you're using? This bug is burning me too. -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
This will probably get fixed in maverick and probably a SRU will be required. ** Changed in: nis (Ubuntu) Importance: Undecided = Wishlist ** Changed in: nis (Ubuntu) Status: New = Confirmed -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
This will probably get fixed in maverick and probably a SRU will be required. ** Changed in: nis (Ubuntu) Importance: Undecided = Wishlist ** Changed in: nis (Ubuntu) Status: New = Confirmed -- NIS upstart dependancy broken for lucid https://bugs.launchpad.net/bugs/569757 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
