similar to: nmbd daemon dies

https://bugzilla.samba.org/show_bug.cgi?id=9502 Summary: Deamon deadlock at stop (SIGINT caught) Product: rsync Version: 3.0.7 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: jurij at ocslab.com

As I know runnig of Nmbd at Acitve Directory mode is quite unofficial now (but possible) . I will not ask why it is not reccomded to run Nmbd within Samba4 started at AD mode. But if somebody can tell, you are wellcome. But when nmb code implementation is planned to AD part ? That is when nmb functionnality adding to Samba4 acting as AD is planned ? To bring possibiity to use full-forced

https://bugzilla.mindrot.org/show_bug.cgi?id=1692 Summary: sshd sometimes dies when sent multiple SIGHUPs in quick succession Product: Portable OpenSSH Version: 5.3p1 Platform: Other URL: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug /497781 OS/Version: Linux Status: NEW

Hello Rsync PRO?s, i?m satisfied with the rsync features...never seen a better replication tool....!! ;-) But i have some problems...:-( OK, here me installation: - one Compac Proliant ML370 with cached SCSI HDDs and 1,2GHz and 1gb RAM... on this machine we have the Rsync deamon runnig to export the data we want to replicate - now we have 68 other NAS machines in our branch offices and this NAS

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

Hi there, ive got a nasty little problem with my Samba 2.2.1, running on a lfs system with kernel 2.2.18 and glibc 2.2.2 . At boottime i first load smbd with option -D and after that nmbd -D. But immediatly after that nmbd crashes without saying a word. Then i found something very interesting in the logs, here an excerpt of log.nmbd : --------------- snip --------------- [2001/10/10 14:04:07,

Hi guys, I got a weird problem over here and couldn't find any solution in several days searching. If I switch my server on (Debian 5.0), the machine boots successfully, samba logs tell me [2009/03/05 09:13:30, 0] smbd/server.c:main(1213) smbd version 3.2.5 started. Copyright Andrew Tridgell and the Samba Team 1992-2008 and [2009/03/05 09:13:30, 0] nmbd/nmbd.c:main(849) nmbd

hi, i upgraded to samba 2.2.7 and since this nmbd (configured to start from xinetd) doesn't start! i sent SIGHUP to xinetd and can see that configuration is ok (netbios-ns is readjusted) but nmbd doesn't start!! when i start nmbd by hand with "-D" i see many messages from xinetd in /var/log/secure: Dec 3 12:05:39 atpcw6yc xinetd[1724]: START: netbios-ns pid=1973

Hi, I'm having problems getting nmbd running. Server is RH7.3 + ACL patches. The problem is that the nmbd deamon crashes with the following error : [2002/10/09 04:42:43, 0] nmbd/nmbd.c:main(794) Netbios nameserver version 2.2.5 started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2002/10/09 04:42:47, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(234)

Every day, I get this error message. It's always around 4:02AM. Jul 6 04:02:10 print-server nmbd[3069]: [2006/07/06 04:02:10, 0] nmbd/nmbd.c:process(596) Jul 6 04:02:10 print-server nmbd[3069]: Got SIGHUP dumping debug info. Jul 6 04:02:10 print-server nmbd[3069]: [2006/07/06 04:02:10, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(284) Jul 6 04:02:10 print-server nmbd[3069]:

My client Windows XP boxes are failing to register with my WINS server (running nmbd from Samba). I'm puzzled how to figure out what I'm doing wrong. Background: I'm setting up BackupPC to back up my Windows clients using rsync. I've installed cwRsync to the clients. BackupPC uses nmblookup to find the client's IP address given its Windows NETBIOS name. I'm

https://bugzilla.samba.org/show_bug.cgi?id=4139 Summary: Generator process (running as daemon) hangs after kill SIGINT. Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

appro@fy.chalmers.se wrote: > > No, it's not:-) > > static int sig_pipe(void) > { > BlockSignals( True, SIGPIPE ); > > DEBUG( 0, ("Got SIGPIPE\n") ); > if ( !is_daemon ) > exit(1); > BlockSignals( False, SIGPIPE ); > #ifndef DONT_REINSTALL_SIG >

Hi all. Running 2.0.4b on a (now) solaris 2.6 box. Since the upgrade the smbd & nmbd daemons won't start. I tried starting smbd by hand, running it through truss. Here's the last few lines: getuid() = 0 [0] fstat(3, 0xEFFFF858) = 0 write(3, " [", 1) = 1 write(3, " 1 9 9 9 / 0

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've had Samba 1.9.18p3 running on a FreeBSD 2.2.7 box at home for months without problems, but after installing 1.9.18p10 on a 2.2.7 box, with the same smb.conf (except for an IP change in the interfaces config and the Netbios server name), I keep getting the following entry in log.nmb immediately after boot: root@gw# cat log.nmb 1998/10/24 00:36:51 netbios nameserver version 1.9.18p10

hi.... I'm using Wine 20030408 on FreeBSD 4.6.2 I believe the instalation is ok (made by ports....) I've to run some applications wich does some file manipulations, such as creating and removing.... Creating a file is ok, but when it tries to remove it, the app shows a message box sayng it was not possible to rename the file . Disk access error. (actually, it creates a file and add

Hello, The attached patch should fix Debian bug #128632 (http://bugs.debian.org/128632). This bug happened because if an error occurred in writefd_unbuffered (such as the remote end closing the socket), it would call rprintf, which would call io_multiplexing_write, which would in turn call writefd_unbuffered, which would then just sit in a loop trying to write to the broken socket. Also, we

Hi! I have a programm with code like this (this is example, the real code is at http://fresh.t-systems-sfr.com/linux/src/.warix/logserial-0.4.2.tar.gz.html): #################### void shutdown(int sig) { switch (sig) { default: fprintf(stderr, "Got signal %d. Exit\n", sig); break; } exit(EXIT_SUCCESS); } int main(void) { chproc = fork(); if

using latest binaries this program dies off, I read somewhere this was fixed in this version 3.0.4 ? but still dies ? -- Regards, Res