similar to: Start and stop the samba server

Date: Wed, 23 Sep 1998 21:38:54 -0500 > From: "Daryl L. Biberdorf" <darylb@superserve.com> > To: samba@sam > Subject: machine name lookups > Message-ID: <3.0.5.32.19980923213854.008144b0@pop.a001.sprintmail.com> > > > We have been looking for a way to notify our users when they > are running low on disk quota, without sending them mail. > WinPopup

I have a UNIX server, running SUNOS 5.5, that keeps dropping of the NT brows list, in all other ways it is working normally. I have found that the only way to bring it back is to reboot the UNIX server. Any ideas? chas

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' >

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 >>

While the Samba server is running, does it ever refresh the contents of the smb.conf file, or do you have to restart the server for it to see changes to the smb.conf file? Thanks in advance. Jeff Rasnick Software Technologies, Inc. www.softtechks.com -------------- next part -------------- HTML attachment scrubbed and removed

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 '/var/log/clamd.clamsmtp/clamsmtpd.log ' </mail> content of /etc/logrotate.d/clamsmtp /var/log/clamd.clamsmtp/clamsmtpd.log { monthly notifempty missingok

The 2.04b rpm for rh60 ships with and installs a config file for logrotate (the samba.log file in the packaging/RedHat section). ===== /var/log/samba/log.nmb { postrotate /usr/bin/killall -HUP nmbd endrotate } /var/log/samba/log.smb { postrotate /usr/bin/killall -HUP smbd endrotate } ===== 1) I think that the use of "endrotate" is wrong. There is no

On Thu, 21 Jun 2018 09:54:06 +0200 john doe via samba <samba at lists.samba.org> wrote: > Bottom posting > > On 6/21/2018 9:38 AM, adam_xu--- via samba wrote: > > Hi, Rowland, I have the same issue too. I can't find any useful > > info after I ran 'man smbcontrol', could you give us a clearer > > answer. Thanks. > > > > > > >

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.

Miredo is run as a server from the command line: /usr/sbin/miredo The man page says the signal SIGTERM stops the server. How do I send SIGTERM to the server? Or SIGHUP, as I want to make a change to the config file. And once I get this as I want it, how do I run it at system boot?

2017-09-08 13:21 GMT+02:00 Pavel Szalbot <pavel.szalbot at gmail.com>: > Gandalf, isn't possible server hard-crash too much? I mean if reboot > reliably kills the VM, there is no doubt network crash or poweroff > will as well. IIUP, the only way to keep I/O running is to gracefully exiting glusterfsd. killall should send signal 15 (SIGTERM) to the process, maybe a bug in signal

I recently decided to set up a Linux machine with the intent to run samba on it. I am running Mandrake 10 and I have installed the latest version of samba from the website. But I can't seem to get samba and swat to work. Because when I go to http://localhost:901 <http://localhost:901/> I receive an error, informing me that it cannot be reached. This is what I have done so

Good time! After upgrading samba 4.5.10 to 4.9.13, name resolution in AD hangs. # /etc/init.d/samba status ?* status: crashed But the domain itself works, but hangs when resolving user names. What can be done? [2019/10/13 12:24:52.896473, 10, pid=17379, effective(0, 0), real(0, 0), class=ldb] ../lib/ldb-samba/ldb_wrap.c:77(ldb_wrap_debug) ? ldb: Added timed event

I have samba installed on a web server (behind a firewall). It's working fine with all the WINS networking here (eg, password authentication from the NT servers, etc). I (we) want this web server - a linux redhat 5.x box currently running samba-1.9.18p8 - to have as few actual unix login accounts as possible. What I want/need to do is to allow LOTS of people in the faculty here

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

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

Howdy, I'm looking for a way to restrict which ssh keys are forwarded to a given remote host because we have several ssh domains. That is, I have two keys which I use throughout the day: .ssh/network-a-2014-10-12 .ssh/network-b-2014-11-22 I need to forward my network A key to the ssh gateway host for Network A to allow me to log into hosts on the other side of the gateway but I

2.0.5 (on linux) has a small annoyance in that, when the log files get rotated, kill -HUP won't point the daemons to the new log files. They keeps logging to the old ones until they are stopped/started. Does 2.0.6 fix this?

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'm looking at astcc and it seems that setting up a script that will allow multiple people to access a calling card simultaneously would be fairly difficult. Before I endevour to develop this, has anyone already done it/looked at this/can point me in the right direction? Thanks. -- Mike Nugent <asterisk@illuminatus.org>