similar to: Reloading services after SIGHUP

I've been running Samba & Squid on a RH linux server for years. I'm currently running: kernel - 2.4.9-31 squid - 2.4STABLE-6 /home - 100 GB Reiserfs partition I just upgraded samba from 2.0.10 to 2.2.5 this morning. Now, the server is running out of filedescriptors. I have never had this problem before. What is 2.2.5 doing differently? How can I resolve this problem? Please help,

samba 2.2.4 on RedHat 7.1 everything is working. wbinfo -t reports a good secret. users can access shares. the samba server shows up in the browser & server manager. However, this server is not able to change the password on it's machine account. I log the following errors once a day: May 29 08:16:33 rhtemp1 smbd[5056]: domain_client_validate: unable to fetch domain sid. May 29

I've been using 2.0.x on my servers for a couple of years & am a very, very happy customer (thanks Samba team). There are only 2, albiet small, annoyances. 1) Any account administration results in changes having to be made on both the NT domain & linux server. 2) I can't do permissions for a "group of groups" on the linux server. It seems that winbind might be able to

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

Anybody else seen this one? We're running Dovecot 1.0.rc7 on a different port on our live server (we're generally live with 1.0.beta5) and after a HUP to reload the user database (in a passwd-file) this morning we got:- > dovecot: Sep 22 07:45:05 Info: IMAP 14482 someuser xxx.xxx.xxx.xxx : Disconnected in IDLE > dovecot: Sep 22 07:45:05 Warning: imap-login: SSL_read() syscall

Just a few quick questions: If I make changes to smb.conf, do I need to restart the SMB and NMB services, or is it like Vixie Cron, where it'll re-read the file and adapt changes every minute? Why do I have multiple NMB instances running, but only one SMB? Thanks for the help! Aton

Hello, OpenSSH 2.5.1p1 running under AIX 4.3.3ML06. When I send a HUP signal to the parent sshd, that parent process dies, it's children get "adopted" by init, and the following message is put in the error log ... Mar 13 12:01:48 whippet sshd[31644]: Received SIGHUP; restarting. Mar 13 12:01:48 whippet sshd[31644]: RESTART FAILED: av[0]='sshd', error: No such file or

Hello people This is on OpenBSD/sparc64. After chickening along with 0.99 for a while, I finally upgraded to 1.0-test. I started out with test73, which worked fine. With the upgrade to test76, I lost the ability to SIGHUP dovecot when I rotated it's logfile. Dovecot would just die abruptly, not a trace in the log. I just upgraded to test77, but the problem is still there. I've put

From: Simon Perreault <nomis80 at lqt.ca> > Sure, theoretically it would be possible, but how would you restart this one? > [nomis80 at poste10-153 ~]$ sudo lsof | grep libc | grep init > init 1 root mem REG 253,0 1521500 999437 /lib/tls/libc-2.3.5.so I need to verify the post-install script for the glibc RPM, but I believe it SIGHUPs the process -- and

I'm a new Samba user running 2.05a. How do I view the # of connections to a share? That is, what is the equivalent to NT's Server Manager -> Shares?

The stub domain device model needs to trap the termination signal so as to actually destroy the stub domain. SIGKILL can''t be trapped, SIGTERM is caught by SDL and so may be unnoticed. SIGHUP can be trapped and is not caught by SDL (and by default causes a process termination without core). Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 2407a61c0d30

Hi, I search in archive list if there any reason why is removed in openssh newer than 2.9.9 from function 'void session_close_by_channel(int id, void *arg)' sending of SIGTEMR and SIGHUP signals to child as was in 2.9.9 version? See follow sniped code from 2.9.9 sources: ---- openssh-2.9.9/session.c ---------------------------------------- void session_close_by_channel(int id, void

We've been successfully running Samba 2.0.5a for a while now on Linux and Solaris servers with Win98 and NT clients. We're using non-encrypted passwords. Recently, two NT clients have been exhibiting the following error message on reconnecting a share a bootup: \\Pike is not accessible. A remote procedure call (RPC) protocol error occurrred. If you continue to boot, Pike can then

Hello, I noticed some random crashes after sending SIGHUP to the daemon (especially when some connections are continually failling). Playing around with gdb, it seems that after SIGHUP, all the "outgoing" information of the connections is being cleared, but later on it is being used in other places while still equal to NULL. The attached patch tries to fix this by avoiding these

Hello, the manpage of ices0 states that on SIGHUP, it'll reopen config and playlist. However, if I change the playlist and HUP, it seems it's still using the old one. Is this expected beharviour and I'm just missing something? Thanks for any insight, Frank

Howdy! the setup: RH-VALE 6.2.4 running samba2.2.2 cvs from 11/24/2001... user running NT 4.0 SP6a the problem: I have a user that cannot print - She can add the printer but can't print. log for that machine shows the following: ... normal looking connections to obtain drivers - all look OK - no complaints.. .. then this - libsmb/namequery.c:name_query(415) Got a positive name query

Just started building the new network with automatic updates and noticed a very weird thing: when master tincd was reloaded (which sends updates), it stopped sending updates. Debugging session revealed that lookup_config(config_tree, NAME) returned NULL when NAME was any configuration item from our host file _after_ SIGHUP. Before it, it returned valid value. I see config_tree is appended with

I have a script that normally runs my snapshot that I haven't used for the past several days because something seemed to be going wrong and I wanted to run things manually. But running the script twice today, I got: > snaphome Found 15 mounted dated, snaps or snap archives ?[snapper#2120]base_mp=/home 1 snap dated today. (Use: '--force=force_create_snap' to force another snap.)

I have the sshd daemon located at /sbin/ssh_22 in this scenario (because I have more than one daemon with separate executable images). After upgrading from 3.6.1p2 to 3.7p1, with the /sbin/ssh_22 copy replaced by mv (not by writing over the existing image), I do SIGHUP and get this message logged: Sep 16 15:07:36 vega sshd_22[22552]: Received SIGHUP; restarting. Sep 16 15:07:36 vega

Hi, I have a couple of ideas how to fix it, but I'm trying to figure out what's going on first. I mainly start this program (sidekiq) on Debian systems, and it might be my first time running it under CentOS, so my conjecture is that it has to do with differences between distributions... Now then, when I run it this way: ssh user at example.com '. ~/.bash_profile && rvm 2.3.1