Re: Upstart (now, a very modest suggestion)
> So, I'm testing samba on a Lucid alpha 3, and I decide to restart the > smbd daemon: > sudo /etc/init.d/samba restart > sudo: /etc/init.d/samba: command not found > Oops, I guess it's a service now? > sudo service samba restart > samba: unrecognized service > So of course it only took a little digging to discover that smbd and > nmbd are now services started separately, and that (bizarrely) there is > now a winbind daemon which is still started from /etc/init.d, but > nevertheless a bit unnerving. (And why and since when has winbind been a > separate daemon, anyway?! But I digress.) I assume that the samba job has been split into two because there was a problem with nmbd not starting when smbd and nmbd were launched through samba. If you look at the respective conf files, you will see that nmbd requires a nic other than lo to be up before starting. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Upstart (now, a very modest suggestion)
On Fri, 2010-03-05 at 12:27 -0600, Patrick Goetz wrote: > So of course it only took a little digging to discover that smbd and > nmbd are now services started separately, and that (bizarrely) there is > now a winbind daemon which is still started from /etc/init.d, but > nevertheless a bit unnerving. (And why and since when has winbind been a > separate daemon, anyway?! But I digress.) > > During the transition from Debianized Sys V Init to Upstart, how > difficult would it be to keep the comfortable old /etc/init.d scripts in > place, but so that these scripts simply tell command line users > something like: > > pgo...@data:~$ sudo /etc/init.d/samba restart > > The samba daemons are now started individually as services: try > service smbd restart > and/or > service nmbd restart > Oh, and note that winbindd is now a separate process -- happy debugging! > > > Again, some people, possibly myself, are old, feeble-minded, and > distracted with lots of problems that go beyond the function of basic > linux server services, hence discomfited when start/stop/restart > commands that have worked for 10 years are suddenly missing with no > explanation of how to proceed in the new world order. > That's exactly what we've done for the most part: quest scott# /etc/init.d/cron restart Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service cron restart Since the script you are attempting to invoke has been converted to an Upstart job, you may also use the restart(8) utility, e.g. restart cron cron start/running, process 20151 Scott -- Scott James Remnant sc...@ubuntu.com signature.asc Description: This is a digitally signed message part -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Upstart (now, a very modest suggestion)
On Fri, 05 Mar 2010 13:54:48 -0500 Ben Gamari wrote: > Excerpts from Patrick Goetz's message of Fri Mar 05 13:27:52 -0500 > 2010: > > So of course it only took a little digging to discover that smbd > > and nmbd are now services started separately, and that (bizarrely) > > there is now a winbind daemon which is still started > > from /etc/init.d, but nevertheless a bit unnerving. (And why and > > since when has winbind been a separate daemon, anyway?! But I > > digress.) > > With all due respect, you are using alpha software. Documentation is > generally one of the last things to be completed. I would hope these > init changes will be thoroughly documented before release. Moreover, > it sounds like most of what confused you were changes in Samba's > packaging, not upstart itself. At the same time, it never hurts to be reminded, most of all about missing docs. > > > > Again, some people, possibly myself, are old, feeble-minded, and > > distracted with lots of problems that go beyond the function of > > basic linux server services, hence discomfited when > > start/stop/restart commands that have worked for 10 years are > > suddenly missing with no explanation of how to proceed in the new > > world order. > > > Certainly, but if you are having difficulty with this, you probably > ought to stick with releases. I am sorry, but I do not agree. The difficulty one (be it Patrick, or whoever) is having on a development release will probably be even greater after a release. Even more, we *need* testers, and we *need* to have feedback. Feedback after the release of a version will probably only be acted on for the next release, while feedback during development allows for (possible) action in time for the release. I would rather have a lot of (even misguided) feedback than none at all (and, by the way, I think Patrick is raising some good points). Cheers, ..C.. signature.asc Description: PGP signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Upstart (now, a very modest suggestion)
Excerpts from Patrick Goetz's message of Fri Mar 05 13:27:52 -0500 2010: > So of course it only took a little digging to discover that smbd and > nmbd are now services started separately, and that (bizarrely) there is > now a winbind daemon which is still started from /etc/init.d, but > nevertheless a bit unnerving. (And why and since when has winbind been a > separate daemon, anyway?! But I digress.) With all due respect, you are using alpha software. Documentation is generally one of the last things to be completed. I would hope these init changes will be thoroughly documented before release. Moreover, it sounds like most of what confused you were changes in Samba's packaging, not upstart itself. > > During the transition from Debianized Sys V Init to Upstart, how > difficult would it be to keep the comfortable old /etc/init.d scripts in > place, but so that these scripts simply tell command line users > something like: > Just use the service command. It's the way things are going to work moving forward. It wouldn't be difficult to write wrapper scripts, but we really do need to move beyond SysV. > > Again, some people, possibly myself, are old, feeble-minded, and > distracted with lots of problems that go beyond the function of basic > linux server services, hence discomfited when start/stop/restart > commands that have worked for 10 years are suddenly missing with no > explanation of how to proceed in the new world order. > Certainly, but if you are having difficulty with this, you probably ought to stick with releases. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Upstart (now, a very modest suggestion)
So, I'm testing samba on a Lucid alpha 3, and I decide to restart the smbd daemon: sudo /etc/init.d/samba restart sudo: /etc/init.d/samba: command not found Oops, I guess it's a service now? sudo service samba restart samba: unrecognized service So of course it only took a little digging to discover that smbd and nmbd are now services started separately, and that (bizarrely) there is now a winbind daemon which is still started from /etc/init.d, but nevertheless a bit unnerving. (And why and since when has winbind been a separate daemon, anyway?! But I digress.) During the transition from Debianized Sys V Init to Upstart, how difficult would it be to keep the comfortable old /etc/init.d scripts in place, but so that these scripts simply tell command line users something like: pgo...@data:~$ sudo /etc/init.d/samba restart The samba daemons are now started individually as services: try service smbd restart and/or service nmbd restart Oh, and note that winbindd is now a separate process -- happy debugging! Again, some people, possibly myself, are old, feeble-minded, and distracted with lots of problems that go beyond the function of basic linux server services, hence discomfited when start/stop/restart commands that have worked for 10 years are suddenly missing with no explanation of how to proceed in the new world order. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
