public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] samba: wsdd started and stopped when samba started or stopped
Date: Fri, 01 Mar 2024 17:17:05 +0100	[thread overview]
Message-ID: <053E52A9-83BD-4067-B86D-650BD2DC5DDC@ipfire.org> (raw)
In-Reply-To: <20240229140937.15643-1-adolf.belka@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2105 bytes --]

Hello,

Hmm, I am not sure whether this change is too confusing…

We normally don’t call one initscript from another one (at least I am not aware).

Would it not be better if we have a check in the wsdd initscript and skip launching the daemon if samba isn’t running? Or should we simply throw away the wsdd initscript and launch the daemon in the samba initscript?

Those options feel slightly cleaner to me. But since I lost the ball on this so badly, maybe I am overlooking the reason why you solved it this way.

-Michael

> On 29 Feb 2024, at 15:09, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> - Add wsdd as a dependency to samba so it will be installed together with samba
> - Add the starting and stopping of wsdd into the samba initscript
> 
> Tested-by: Adolf Belka <adolf.belka(a)ipfire.org>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> lfs/samba                      | 4 ++--
> src/initscripts/packages/samba | 6 +++++-
> 2 files changed, 7 insertions(+), 3 deletions(-)
> 
> diff --git a/lfs/samba b/lfs/samba
> index 76088abfa..df7811313 100644
> --- a/lfs/samba
> +++ b/lfs/samba
> @@ -33,9 +33,9 @@ DL_FROM    = $(URL_IPFIRE)
> DIR_APP    = $(DIR_SRC)/$(THISAPP)
> TARGET     = $(DIR_INFO)/$(THISAPP)
> PROG       = samba
> -PAK_VER    = 99
> +PAK_VER    = 100
> 
> -DEPS       = avahi cups perl-Parse-Yapp perl-JSON
> +DEPS       = avahi cups perl-Parse-Yapp perl-JSON wsdd
> 
> SERVICES   = samba
> 
> diff --git a/src/initscripts/packages/samba b/src/initscripts/packages/samba
> index 93f14cd29..99b9929cf 100644
> --- a/src/initscripts/packages/samba
> +++ b/src/initscripts/packages/samba
> @@ -42,6 +42,8 @@ case "$1" in
> 
> boot_mesg "Starting winbind..."
> loadproc /usr/sbin/winbindd
> + 
> + /etc/rc.d/init.d/wsdd start
> ;;
> 
> stop)
> @@ -53,7 +55,9 @@ case "$1" in
> 
> boot_mesg "Stopping winbind..."
> killproc /usr/sbin/winbindd
> -                ;;
> + 
> + /etc/rc.d/init.d/wsdd stop
> +              ;;
> 
> reload)
> boot_mesg "Reloading smbd..."
> -- 
> 2.44.0
> 


       reply	other threads:[~2024-03-01 16:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240229140937.15643-1-adolf.belka@ipfire.org>
2024-03-01 16:17 ` Michael Tremer [this message]
2024-03-01 17:13   ` Adolf Belka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=053E52A9-83BD-4067-B86D-650BD2DC5DDC@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox