similar to: RH 7.1 & Samba HELP

I am running Redhat 7.1 and am trying to use V scripts to start samba as a Daemon. I have put the script in /etc/init.d and put a symbolic link in /etc/rc3.d with the file name S70samba (so it's /etc/rc3.d/S70samba points to /etc/init.d) But it will not start during boot! Does anyone have a script that I can use, I think the one I have is screwy.

hi all, I noticed that when I upgraded from Samba 2.0.7 (redhat 7.0) to samba 2.2.1a I lost this nice little script that came with redhat to start and stop the samba server. I would type in /usr/sbin/samba start and get a response like... /usr/sbin/smbd start (OK) /usr/sbin/nmbd start (OK) I liked that...does any one have a substitute that I could use for 2.2.1a? Thanks Carl

Hi. I'm getting messages to the effect: Inetd: /usr/local/samba/lib/nmbd: Hangup Last messages repeat 319 times I start samba from inetd. Should I be starting it as a daemon or starting it in init.d? If starting it as a daemon in in init.d, does someone have a script that can let me use? I'm running samba on an a Sun E450, with Solaris 2.7. Thanks. grant

I'm having problems when I restart the smb server with it not coming back up. As near as I can tell it's actually NMBD that's having the issue. I'm running RedHat 9.0 on a Compaq ML-370 with Dual 1.2GHz P3s and I just upgraded Samba to 2.2.8a-1 after having this same problem with 2.2.7a When I issue: #service smb restart It says that it shut down and restarted ok, but then nobody

Hello People, /etc/rc.d/init.d/smb status yields the following output: smbd (pid 31224 31209 31102 31098 31077 31069 31056 3237 3171 3154 3147 3144 3131 3129 3128 3124 3119 3091 3077 2590 2582 2564 2491 2468 1964) is running... nmbd (pid 31062 31061) is running... In total 25 smbd's and 2 nmbd's, while only five or six users actually use the samba-server. This many processes causes

I am using Suse V8 with KDE3 and running Samba 2.2.3a, and very much feeling my way as I get into Linux. Using Swat I checked Status and it said smbd running, nmbd not running. If I use KDE process table I can see nmbd as PID 714 and smbd as PID 719. I cannot start or restart nmbd from Swat ? Any clues as to what the problem is here? John This email has been pre-scanned using the

Hi during Startup of SuSE-Linux 7.2 Prof. the PC is sometimes ( 1 of 10 times) stopping by start smbd. Reset knop the help only. I have this problem with the samba version in SuSE package and version 2.2.5 too. In the file ../rc3.d/S12smb I added 2 lines to see if nmbd and smbd are startet. I see nmbd is starting always, the text "SAMBA smbd gestartet" is in case of fault not printing.

Is there a good way to stop and restart the samba server... for example to have it re read the smb.conf, without rebooting the actual pc? if I should kill a process should I kill them all ??? if so is there an efficent way to do this? thanks in advance Robert

Hello, If I make a change to the smb.conf file. Can I simply invoke 'smbcontrol all reload-config', or must I kill all samba services and restart them? -- -James

Hello there! After much trial and error, scouring the net and books for samba setups/faqs/resources, etc - I seem to have Samba setup with winbind more or less correctly - There seems to be a couple bugs though. The goal is to have a windows workstation-like Linux box to access the NT 4.0 domain. Logging into the Linux box (physically) with domain user accounts, accessing domain printers,

Hi Is it possible to send SIGHUP to the parant process to let samba reread the smb.conf file, or is any way to let samba reread this file without restarting samba regards Alaa

On Thu, 21 Jun 2018 19:17:14 +0700 Vladimir Eltsov via samba <samba at lists.samba.org> wrote: > Hello. > > I have read man smbcontrol. > > I wrote in start message: > > > I have tried: > > systemctl reload smbd.service > > killall -1 smbd > > pkill -HUP smbd Forget 'systemctl reload' Forget 'killall' Forget 'pkill' >

How are you verifying? Have you tried using top and looking for smbd and nmbd? Swat may be giving you erroneous info if that is what you are using to verify. Hope this helps... -----Original Message----- From: Alvaro Lassance [mailto:lassance@sidercom.com.br] Sent: Thursday, January 03, 2002 10:35 AM To: samba@lists.samba.org Subject: Samba Start Hello all! I am trying to start Samba 2.2.2

Dear All: --- Summary, especially for openssh list (to test/reproduce): THANK YOU for all your help. Please extract into /home/username/nx on both host and client. cp ssh to a file named mxssh in that directory. Run (with an _n_ below) Start server on the remote host by typing ./server & Now do: ./nxssh hostname If you killall client on the remote end, it reconnects "seamlessly"

Can you try this and adjust the path's in it. #/etc/logrotate.d/samba /var/log/samba/log.smbd { weekly missingok rotate 7 postrotate [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/smbd.pid ] || /usr/bin/smbcontrol smbd reload-config endscript compress delaycompress notifempty } /var/log/samba/log.nmbd {

I know about this param, I configured it and log.smbd, log.nmbd and others are rotated, log.samba is not. ----- Original Message ----- > From: "samba" <samba at lists.samba.org> > To: "Lorenzo Milesi" <maxxer at yetopen.it>, "samba" <samba at lists.samba.org> > Sent: Thursday, May 21, 2020 7:29:04 PM > Subject: Re: [Samba] log.samba

Ubuntu 14.04, ctdb 2.5.1 from the ubuntu package. samba 4.1.11 with cluster support from source. Error upon startup only. Restarting ctdb on that node clears the error. The other node with the same config is OK. Any ideas? Cheers, Steve smb.conf [global] workgroup = ALTEA realm = ALTEA.SITE security = ADS kerberos method = secrets and keytab netbios name = SMBCLUSTER disable netbios = Yes

On 01.05.2017 13:15, James Pearson wrote: > Walter.H at mathemainzel.info: >> I get regularily such a mail >> >> <mail> >> Anacron job 'cron.daily' on .... >> >> /etc/cron.daily/logrotate: >> >> error: error running non-shared postrotate script for >> /var/log/clamd.clamsmtp/clamsmtpd.log of >>

I'm building a RedHat fileserver using an HP LH3 fileserver. I can't get the sbmd running however. The trial machine we've been running for 4 months now has the same setup and works perfectly. nmbd runs ok, but when I look at log.smb, it says bind failed on port 139_0.0.0.0 address already in use. But in inetd.conf there's only smbd on port 139. This is a fresh

ctdb 2.5.3 dual node file server with 4.1.9 serving AD domain Hi We have enabled the script at: /etc/cdb/events.d/50.samba but when we are the enabled node, it starts not only smbd but also nmbd. This doesn't make sense in an AD domain. I've tried disabling nmbd starting under openSUSE's systemd but ctdb overrides that, I've had a look at the script but can't decipher the bit