�ncelikle yardimlariniz icin tesekkur ederim.
Signal handler bolumune SIGPIPE'i da ekledim.
Buna ragmen signali handle edemiyorum. Process yine kapaniyor.
Yoksa yanlis mi handle ediyorum?
Asagida signal handler ile ilgili kodlari ekledim:
daemonize fonksiyonunda yer alan signal catch bolumu:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
void daemonize(void)
{
...
signal(SIGPIPE,signal_handler); /* catch broken pipe signal*/
signal(SIGHUP,signal_handler); /* catch hangup signal */
signal(SIGTERM,signal_handler); /* catch kill signal */
...
}
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
signal_handler fonsiyonu:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
void signal_handler(int sig)
{
switch(sig) {
case SIGPIPE:
log_msg(logfile, "Broken Pipe signal catched");
close(client_sock);
break;
case SIGHUP:
log_msg(logfile,"Hangup signal catched");
readconfig(conf_file);
log_msg(logfile,"Configuration Reloaded");
break;
case SIGTERM:
log_msg(logfile,"Terminate signal catched");
log_msg(logfile,"Closing active sessions...");
close(server_sock);
log_msg(logfile,"Bye bye");
log_msg(logfile,"******************************\n");
exit(0);
break;
}
}
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
*********** REPLY SEPARATOR ***********
On 20.03.2004 at 09:02 Murat Balaban wrote:
>Selamlar,
>
>karsi taraftan close(2) edilmis bir soket'e yazmaya devam edildigi zaman, o prosese
>SIGPIPE yollanir. Eger bu sinyal yakalanmiyorsa, proses terminate eder. Boyle
>olmamasi icin, SIGPIPE icin bir handler olusturun.
>
>Bundan boyle, bunun gibi durumlarda, send(2) EPIPE donecektir, prosesiniz
>olmeyecektir.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Liste arsivi: http://lists.enderunix.org ve
http://www.mail-archive.com/[EMAIL PROTECTED]
http://ipucu.EnderUNIX.org - ihtiyac duyacaginiz kisa bilgiler bu sitede!
