Re: Bug#34408: samba: sambaconfig hoses inetd.conf if interrupted at first prompt (fwd)
On Mon, Mar 15, 1999 at 10:02:48AM +0000, Julian Gilbey wrote:
> Note that you can do the following if the former is the case:
>
> cp /etc/inetd.conf /etc/inetd.conf.samba
> update-inetd --file /etc/inetd.conf.samba --other-options ...
> update-inetd --file /etc/inetd.conf.samba --other-options ...
> mv /etc/inetd.conf.samba /etc/inetd.conf
>
> In that way, you never touch /etc/inetd.conf until your new version is
> completely ready.
Hmm. I'd assume that update-inetd locks inetd.conf so that two instances
won't collide. (Big assumption? I haven't looked at the code.) But if
you do what you have here, what happens if update-inetd gets run by
some{one|thing} else? If inetd is only supposed to be modified by
update-inetd, I would think that modifying it with mv (which is
essentially what's happening above) would be a Bad Thing?
Mike Stone
Reply to: