search for: catchsign

...yscall == 200 ! */ + DEBUG(9,("sig_cld_leave_status: syscall %d restarted\n",scp->sc_syscall)); + } +#endif /* * Turns out it's *really* important not to * restore the signal handler here if we have real POSIX @@ -134,5 +147,5 @@ void CatchChildLeaveStatus(void) { - CatchSignal(SIGCLD, sig_cld_leave_status); + CatchSignal(SIGCLD, SIGNAL_CAST sig_cld_leave_status); } diff -u --recursive --new-file source/smbd/open.c source.new/smbd/open.c --- source/smbd/open.c Thu Dec 31 03:37:01 1998 +++ source.new/smbd/open.c Sun Jan 24 23:32:32 1999 @@ -225,8 +225,10 @@ */...

(using samba-2.0.7 on Debian Linux 2.2.15) Hi, I'm wondering how do I get around the problem when you smbmount a share on a win32 machine and that machine reboots, the mount becomes a blackhole. If you attempt an 'ls', 'df' or anything that would access that mount point the program then goes into a state of void and cannot be killed, leaving the proc open until reboot

...we are no longer interactive */ + pstrcpy(remote_machine, "smbmount"); /* sneaky ... */ + setup_logging("mount.smbfs",False); + reopen_logs(); + closed = 1; - dbf = NULL; - close_our_files(c?c->fd:-1); } -#endif - /* Wait for a signal from smbfs ... */ - CatchSignal(SIGUSR1, &usr1_handler); - pause(); -#ifdef SMBFS_DEBUG - DEBUG(2,("mount.smbfs: got signal, getting new socket\n")); -#endif - c = do_connection(service); + /* Wait for a signal from smbfs ... but don't continue + until we actually get a new connection. */...

...------------------------- --- smbmount.c.ORIG Thu Nov 11 00:00:00 1999 +++ smbmount.c Tue Jun 13 14:00:23 2000 @@ -342,7 +342,7 @@ close_our_files(c?c->fd:-1); } #endif - +failed: /* Wait for a signal from smbfs ... */ CatchSignal(SIGUSR1, &usr1_handler); pause(); @@ -350,6 +350,7 @@ DEBUG(2,("mount.smbfs: got signal, getting new socket\n")); #endif c = do_connection(service); + if(c==NULL) goto failed; } smb_umount(mount_point);...

...ompt with R CMD INSTALL <packagename> however, the C files within the source directory all compiles until it hits a file called cheapcgi.c, where the following error is given: gcc -I"c:/R/include"??????? -O3 -Wall? -std=gnu99 -c cheapcgi.c -o cheapcgi.o cheapcgi.c: In function 'catchSignal': cheapcgi.c:538: error: 'SIGBUS' undeclared (first use in this function) cheapcgi.c:538: error: (Each undeclared identifier is reported only once cheapcgi.c:538: error: for each function it appears in.) cheapcgi.c:546: error: 'SIGKILL' undeclared (first use in this function)...

...g_cld_leave_status: syscall %d >restarted\n",scp->sc_syscall)); >+ } >+#endif > /* > * Turns out it's *really* important not to > * restore the signal handler here if we have real POSIX >@@ -134,5 +147,5 @@ > > void CatchChildLeaveStatus(void) > { >- CatchSignal(SIGCLD, sig_cld_leave_status); >+ CatchSignal(SIGCLD, SIGNAL_CAST sig_cld_leave_status); > } >diff -u --recursive --new-file source/smbd/open.c source.new/smbd/open.c >--- source/smbd/open.c Thu Dec 31 03:37:01 1998 >+++ source.new/smbd/open.c Sun Jan 24 23:32:32 1999 >@@ -225,8...