search for: killall

When I started Rails Development, I needed to use ''killall -g dispatch.fcgi'' whenever I made a change to a Model to see the change on my website. Now it seems I need to do this to see any change to the Controller as well. Any ideas of what I am doing wrong??? -- Posted via http://www.ruby-forum.com/.

...t working. One of the troubleshooting items on the wiki states: Rails apps in production mode do not reflect changes made after they start running. So, if you found a bug, fixed it and nothing appeared to happen--this is probably because you haven''t restarted your fcgi processes. Run killall -9 ruby a couple of times. It might also take a couple of browser refreshes for the change to take affect. How do I "Run killall -9 ruby"?? Thanks in advance!! -- Posted via http://www.ruby-forum.com/.

I tried using the killall -USR1 mongrel_rails to check on a problem, and all I get is mongrel_rails: no process killed Nothing shows in the log. Any ideas? I''m using the latest pre-release, and a ''ps'' shows my cluster is running. Cheers, Brett

...tdb_setup_service_state_dir service_start () { # make sure samba is not already started service "$CTDB_SERVICE_SMB" stop > /dev/null 2>&1 if [ -n "$CTDB_SERVICE_NMB" ] ; then service "$CTDB_SERVICE_NMB" stop > /dev/null 2>&1 fi killall -0 -q smbd && { sleep 1 # make absolutely sure samba is dead killall -q -9 smbd } killall -0 -q nmbd && { sleep 1 # make absolutely sure samba is dead killall -q -9 nmbd } # start Samba service. Start it reniced, as under very heavy load # the number of sm...

...log/clamd.clamsmtp/clamsmtpd.log' >> </mail> > The following may help: > > https://bugzilla.redhat.com/show_bug.cgi?id=1376815 > > James Pearson > > Hello, I found your hint several time ago, this didn't solve it ... I don't understand this - killall -HUP clamd.<SERVICE> 2>/dev/null || : + killall -HUP clamd.<SERVICE> > /dev/null 2>&1 || true in the patch as the file has this pkill -SIGHUP -f clamd.clamsmtp >/dev/null 2>&1 || : in comparison /etc/logrotate.d/clamav has this killall...

...tpd ? ??runsv???dovecot???2*[dovecot-auth] ? ? ? ??1203*[imap] ? ? ? ??64*[imap-login] ? ? ? ??64*[managesieve-log] ? ? ? ??64*[pop3-login] ? ? ??svlogd killall dovecot? Is that guaranteed to wipe out ALL child processes as well? I had to use (at least in the past): sv d /var/service/dovecot killall dovecot killall -9 imap-login ps auxwww|grep dovecot to make sure everything would be dead... -- Ralf Hildebrandt Gesch?ftsbereich IT | Abtei...

...le in ... matching ''dispatch.[0-9]*.pid'' based on the suggestion of another post I implemented the following in deploy.rb which does successful terminate all the Ruby process but this includes God. desc "restart override" task :restart, :roles => :app do run "killall -9 /usr/local/bin/ruby" end I don''t think I''m supposed kill God. My mongrel.rb is supposed to just do a god restart mongrels -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscrib...

2017-09-08 13:07 GMT+02:00 Pavel Szalbot <pavel.szalbot at gmail.com>: > OK, so killall seems to be ok after several attempts i.e. iops do not stop > on VM. Reboot caused I/O errors after maybe 20 seconds since issuing the > command. I will check the servers console during reboot to see if the VM > errors appear just after the power cycle and will try to crash the VM after &g...

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' > > smbcontrol smbd reload-config This is the one that should work, this should make smbd reload smb.conf You could try 'smbcontrol all reload-config' You should also...

...tdb_setup_service_state_dir service_start () { # make sure samba is not already started service "$CTDB_SERVICE_SMB" stop > /dev/null 2>&1 if [ -n "$CTDB_SERVICE_NMB" ] ; then service "$CTDB_SERVICE_NMB" stop > /dev/null 2>&1 fi killall -0 -q smbd && { sleep 1 # make absolutely sure samba is dead killall -q -9 smbd } killall -0 -q nmbd && { sleep 1 # make absolutely sure samba is dead killall -q -9 nmbd } # start Samba service. Start it reniced, as under very heavy load # the number of sm...

Oh, and if you don't have killall installed, you can use: ps -ef | grep yum to get the pid and then use: kill -TERM pid or easier even is: kill -TERM `pid of yum` Chris On Fri, Feb 20, 2015 at 4:13 PM, Chris Stone <axisml at gmail.com> wrote: > try CTRL-Z to put that running process in your shell to sleep, then:...

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 "endrotate" in logrotate's (logrotate-3.2-1) man pages; the man examples use "endscr...

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

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

>From the killall man page: killall sends a signal to all processes running any of the specified commands. If no signal name is specified, SIGTERM is sent. ---------- Original Message ---------------------------------- From: "Oscar A. Valdez" <oscar.valdez@plastipak.com.sv...

So, I'm getting an error where the network service and NetworkManager apparently don't agree on how to bring up vlans on bonded nics. Things come up if you 'ifup ..' manually. I thought I'd check if there were any updates, forgetting to fix what NetworkManger had done to /etc/resolv.conf and: http://centos.arvixe.com/7.0.1406/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout

Gandalf, SIGKILL (killall -9 glusterfsd) did not stop I/O after few minutes. SIGTERM on the other hand causes crash, but this time it is not read-only remount, but around 10 IOPS tops and 2 IOPS on average. -ps On Fri, Sep 8, 2017 at 1:56 PM, Diego Remolina <dijuremo at gmail.com> wrote: > I currently only have a...

...domain > >> controllers), differnt versions (4.4.4, 4.6.2...). > >> > >> I have found that changes hosts allow option are not applaying > >> without restart smbd. > >> > >> I have tried: > >> systemctl reload smbd.service > >> killall -1 smbd > >> pkill -HUP smbd > >> smbcontrol smbd reload-config > >> > >> but client I have added does not have access. > >> > >> I see strange messages in system log: > >> > >> Jun 20 15:50:20 nvkzsrv smbd[29943]: [2018/06/20...

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