search for: hupped

Hi, I've recently benchmarked btrfs v0.11 & v0.12 against ext2, ext3, ext4, jfs, reiserfs and xfs. OS: Ubuntu Hardy Kernel: 2.6.24(-5-server) Hardware: --------- Fu-Si Primergy RX330 S1 * AMD Opteron 2210 1.8 GHz * 1 GB RAM * 3 x 73 GB, 3Gb/s, hot plug, 10k rpm, 3.5" SAS HDD * LSI RAID 128 MB Fu-Si Econel 200 * Intel Xeon 5110 * 512 MB RAM

Hello I'm running CentOS 5.3 with httpd-2.2.3-22.el5.centos.x86_64 and php-5.1.6-23.2.el5_3.x86_64. When the logrotate scripts run and send the HUP signal to httpd, the httpd process quits instead of reloading. The only thing I can find in the logs is this: [Sun Apr 19 04:02:04 2009] [notice] seg fault or similar nasty error detected in the parent process There wasn't any segfault

Hi, I need to re-open the thread blow. The situation is still the same. The HUP signal does not trigger reloading of subnet declarations in own hosts file (Version 1.0.35). After a quick view to the source code, file src/net.c shows in line 658 would reload subnets when using StrictSubnets only. But why? With StrictSubnets it doesn't make sense to me. I did a quick check and removed the if

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?

I've just updated a few CentOS 5.3 servers to 5.4. One of them were a Apache Webserver. Doing a diff/check on the new ".rpmnew" config files that are made, I saw that the logrotate command for apache was changed. In 5.3 it did a reload, but in 5.4 it does a hard kill: CentOS 5.3: /var/log/httpd/*log { missingok notifempty sharedscripts postrotate

Currently, on deploys we''re sending HUP to the "old" master to reload the config, and then we send it a USR2 to reload the app code. Is this redundant -- i.e. does USR2 reload the unicorn config, or just the application code? I am under the impression that USR2 forks a new master from the old, and only reloads app code, and not the unicorn config, but I just wanted to double

rh60/caldera1.3 2.0.x (before 2.0.5) PROBLEM: samba didn't reopen then logs after HUP. I posted about this to samba-bugs; AT corrected the problem in 2.0.5-preXX, but not completely it seems. 2.0.5 PROBLEM: samba reopens the logs after a HUP but logs only the first connection to the new log, then it keeps logging to the old one. Here is what I see: # pwd /var/log/samba # smbclient|grep

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

Hi everyone again. I run tinc with the following command: /usr/sbin/tincd -d1 --logfile=/var/log/tinc.log That creates the file "/var/log/tinc.log" correctly and reports into it. Well, because I want to have a log file by day, I have created a logrotate file (/etc/logrotate.d/tinc) that contains the following lines: ----------------------------------------- /var/log/tinc.log {

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

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

Hi: I noticed in an icecast2 log that a HUP will reload the server config. This is a nice feature. Are there any configuration options that won't take effect with such a reload, or will it completely take effect? If the ports have changed, for example, will these change? Geoff. <p> -- Geoff Shang <gshang@uq.net.au> ICQ number 43634701 Make sure your E-mail can be read by

With the latest version of Mongrel, will Mongrel reopen log files when sent a HUP signal? I would like to do a log rotate, but would prefer not to restart the mongrel instances as monit is watching after them all. monit is great for restarting the individual instances, but I would prefer not to do a restart all through monit. I would be curious if this is advisable. -- ----- Christopher

Hi folks, I''ve experimented a problem while deploying my app, I''ve sent the HUP signal to the master process, I''ve checked everything is ok: new master and workers are spawned and the old ones are killed(I''ve checked the PIDs), but the new code deployed isn''t reflected in the living site, so I''ve to stop and start again unicorn in order to see

Noticed the following on the CLI: Received HUP signal -- Reloading configs == Parsing '/etc/asterisk/extconfig.conf': Found == Parsing '/etc/asterisk/manager.conf': Found <snip> How do I track down the source of the HUP? There are no indications in any log files and I do not have any cron entries for * (RHv9). Is asterisk doing this for some reason via internal

Hi, I''m trying to use mongrel 0.3.13 with Rail 1.0 Believe it or not, on OS/X it works well for weeks at a time. On linux I''m getting Input/output errors after anything from a few hours to days, never more than a week. Once they start they don''t stop. The only pattern I''ve seen is that it always (seems) to happen while rendering an rhtml file.

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 have this strange problem where when I try to reload my config by sending a HUP to the icecast process it produces this in the error.log file: [2004-01-15 21:06:07] INFO connection/connection_accept_loop Scheduling config reread ... [2004-01-15 21:06:07] EROR event/event_config_read Error parsing config, not replacing existing config [2004-01-15 21:06:07] EROR event/event_config_read Parse

Hi, If sshd is started with 'sshd', restarting with kill -HUP will fail. I've included the most obvious patch, but making sure that the full pathname is in saved_argv[0] just might be more secure. Cheers, Han Holl --- sshd.c.orig Mon Feb 19 10:55:54 2001 +++ sshd.c Mon Feb 19 10:56:15 2001 @@ -208,7 +208,7 @@ { log("Received SIGHUP; restarting.");

Hi, We couldn't delete any files and directories when connecting glusterfs to windows via NFS. We could make/change files and directories. Although it has written that glusterfs can be connected with windows NFS client in the page shown below. Any ideas to workaround/fix this ?