comp.unix.programmer

• Thread Index

---

• Re: pthread_cancel causing infinite memory allocation loop
  • From: Edwin van den Oetelaar
• Re: Error: Unexpected symbol: "spu_t".
  • From: Fred Kleinschmidt
• getpriority and renice command
  • From: Neo
• Re: pipes
  • From: Rainer Weikusat
• Error: Unexpected symbol: "spu_t".
  • From: Navaneet
• Re: daemonizing without setsid()
  • From: Ivan Gotovchits
• Re: Problem using 'make'
  • From: chr . ott
• getpriority and renice
  • From: Neo
• Re: pthread_cancel causing infinite memory allocation loop
  • From: Måns Rullgård
• pthread_cancel causing infinite memory allocation loop
  • From: captain_oldfield
• read always returns EOF on TLSv1 socket?
  • From: yermej
• Re: pipes
  • From: fjblurt
• Re: pipes
  • From: Bahadir
• Re: pipes
  • From: Alex Fraser
• Re: pipes
  • From: Captain Dondo
• Re: Problem using 'make'
  • From: Henry Townsend
• Re: daemonizing without setsid()
  • From: Geoff Clare
• Re: pipes
  • From: Golden California Girls
• Re: raw socket question
  • From: Rainer Temme
• Re: Problem using 'make'
  • From: Gianni Mariani
• Problem using 'make'
  • From: chr . ott
• Re: pipes
  • From: moi
• raw socket question
  • From: sinbad
• Re: Portable time profiling function
  • From: Logan Shaw
• Re: pipes
  • From: Logan Shaw
• Re: pipes
  • From: Logan Shaw
• Re: daemonizing without setsid()
  • From: Barry Margolin
• Re: pipes
  • From: fjblurt
• Re: multi-process locking
  • From: Rainer Weikusat
• Re: pipes
  • From: CptDondo
• Re: pipes
  • From: moi
• Re: putenv for AIX and ifdef for AIX
  • From: Mark Holland
• Re: pipes
  • From: CptDondo
• Re: multi-process locking
  • From: Chris Friesen
• Re: pipes
  • From: Rainer Weikusat
• Re: multi-process locking
  • From: Rainer Weikusat
• Re: Portable time profiling function
  • From: Rick Jones
• multi-process locking
  • From: Ivan Novick
• Re: Portable time profiling function
  • From: Ivan Novick
• Re: pipes
  • From: CptDondo
• putenv for AIX and ifdef for AIX
  • From: ClownPleco
• Re: pipes
  • From: Maxim Yegorushkin
• Re: pipes
  • From: Rainer Weikusat
• Re: pipes
  • From: Rainer Weikusat
• Re: pipes
  • From: Ivan Gotovchits
• Re: pipes
  • From: Maxim Yegorushkin
• Re: pipes
  • From: Maxim Yegorushkin
• Re: Portable time profiling function
  • From: Ivan Gotovchits
• Re: pipes
  • From: Ivan Gotovchits
• Re: daemonizing without setsid()
  • From: ta0kira
• Re: daemonizing without setsid()
  • From: ta0kira
• Re: pipes
  • From: jellybean stonerfish
• Re: Portable time profiling function
  • From: Logan Shaw
• Re: pipes
  • From: Barry Margolin
• Portable time profiling function
  • From: Bin Chen
• Re: daemonizing without setsid()
  • From: Jim Cochrane
• Re: pipes
  • From: CptDondo
• Re: iopl() vs. ioperm()
  • From: Måns Rullgård
• iopl() vs. ioperm()
  • From: philbo30
• Re: pipes
  • From: Maxim Yegorushkin
• pipes
  • From: CptDondo
• Re: exception handling around a signal handler
  • From: Brilte
• Re: exception handling around a signal handler
  • From: Rainer Weikusat
• Re: exception handling around a signal handler
  • From: Rainer Weikusat
• Re: exception handling around a signal handler
  • From: moi
• Re: fwrite
  • From: fjblurt
• Re: daemonizing without setsid()
  • From: Giorgos Keramidas
• Re: daemonizing without setsid()
  • From: Barry Margolin
• Re: fwrite
  • From: Barry Margolin
• Re: daemonizing without setsid()
  • From: David Schwartz
• Re: Partial writes with writev() on TCP sockets
  • From: David Schwartz
• Re: exception handling around a signal handler
  • From: Gianni Mariani
• Re: exception handling around a signal handler
  • From: Brilte
• Re: exception handling around a signal handler
  • From: Ulrich Eckhardt
• Re: fwrite
  • From: Spoon
• Re: fwrite
  • From: Al Balmer
• Re: daemonizing without setsid()
  • From: Giorgos Keramidas
• Re: daemonizing without setsid()
  • From: Henry Townsend
• Re: fwrite
  • From: Eric Sosman
• Re: exception handling around a signal handler
  • From: Rainer Weikusat
• Re: exception handling around a signal handler
  • From: Rainer Weikusat
• Re: exception handling around a signal handler
  • From: Gianni Mariani
• Re: daemonizing without setsid()
  • From: Ivan Gotovchits
• Re: daemonizing without setsid()
  • From: Ivan Gotovchits
• Re: daemonizing without setsid()
  • From: ilko_partizan
• Re: daemonizing without setsid()
  • From: Casper H . S . Dik
• Re: daemonizing without setsid()
  • From: Ivan Gotovchits
• Re: daemonizing without setsid()
  • From: Casper H . S . Dik
• exception handling around a signal handler
  • From: Brilte
• daemonizing without setsid()
  • From: Ivan Gotovchits
• Re: Partial writes with writev() on TCP sockets
  • From: Ivan Gotovchits
• Re: fwrite
  • From: fjblurt
• fwrite
  • From: Ivan Novick
• Re: vim with bookmarks
  • From: Al Balmer
• Re: vim with bookmarks
  • From: ed
• Re: vim with bookmarks
  • From: Al Balmer
• Re: vim with bookmarks
  • From: ed
• Re: vim with bookmarks
  • From: Tweedale
• vim with bookmarks
  • From: ed
• Re: Partial writes with writev() on TCP sockets
  • From: Frank Cusack
• Re: Partial writes with writev() on TCP sockets
  • From: Olivier Langlois
• Partial writes with writev() on TCP sockets
  • From: Olivier Langlois
• Re: NewsMaestro Usenet Supertool
  • From: Almond
• Re: is a file descriptor a socket?
  • From: Frank Cusack
• Re: How to write a script to kill more than one process matching with grep
  • From: Logan Shaw
• Re: deamon is not getting started with the script(Urgent)
  • From: Barry Margolin
• Re: is a file descriptor a socket?
  • From: Barry Margolin
• Re: is a file descriptor a socket?
  • From: Frank Cusack
• Re: Does kill() remove temporary files?
  • From: David Schwartz
• Re: is a file descriptor a socket?
  • From: David Schwartz
• Re: is a file descriptor a socket?
  • From: Frank Cusack
• Re: is a file descriptor a socket?
  • From: Frank Cusack
• Re: check memory protection
  • From: Scott Lurndal
• Re: check memory protection
  • From: Måns Rullgård
• Re: check memory protection
  • From: Scott Lurndal
• Re: check memory protection
  • From: Måns Rullgård
• Re: How to write a script to kill more than one process matching with grep
  • From: Scott Lurndal
• Re: How to temporarily disable the keyboard
  • From: Scott Lurndal
• Re: How to write a script to kill more than one process matching with grep
  • From: Eric Sosman
• Re: Does kill() remove temporary files?
  • From: Gary R. Schmidt
• Re: How to write a script to kill more than one process matching with grep
  • From: Bit Twister
• deamon is not getting started with the script(Urgent)
  • From: harry
• Re: How to temporarily disable the keyboard
  • From: Army1987
• How to write a script to kill more than one process matching with grep
  • From: mullin
• Re: How to temporarily disable the keyboard
  • From: Army1987
• Re: Does kill() remove temporary files?
  • From: David Schwartz
• Re: How to temporarily disable the keyboard
  • From: David Schwartz
• Re: Does kill() remove temporary files?
  • From: SM Ryan
• Does kill() remove temporary files?
  • From: Army1987
• Re: How to temporarily disable the keyboard
  • From: Army1987
• Re: check memory protection
  • From: Javier
• Re: is a file descriptor a socket?
  • From: Måns Rullgård
• Re: is a file descriptor a socket?
  • From: David Schwartz
• Re: is a file descriptor a socket?
  • From: fjblurt
• Re: multiple pipes and tail -f
  • From: pvsnmp
• is a file descriptor a socket?
  • From: Frank Cusack
• Re: How to temporarily disable the keyboard
  • From: Scott Lurndal
• Re: Is there a pstack for Linux?
  • From: Scott Lurndal
• Re: multiple pipes and tail -f
  • From: Pipe Dope
• Re: How to temporarily disable the keyboard
  • From: Army1987
• Re: How to temporarily disable the keyboard
  • From: Army1987
• Re: How to temporarily disable the keyboard
  • From: David Schwartz
• Is there a pstack for Linux?
  • From: zhliang2004
• Re: multiple pipes and tail -f
  • From: Ivan Gotovchits
• multiple pipes and tail -f
  • From: pvsnmp
• Re: How to temporarily disable the keyboard
  • From: Ivan Gotovchits
• Re: How to temporarily disable the keyboard
  • From: Ivan Gotovchits
• Re: second column of ls -l doesn't show number of hard links
  • From: Ben Bacarisse
• Re: How to temporarily disable the keyboard
  • From: Army1987
• Re: How to temporarily disable the keyboard
  • From: Army1987
• Re: How to temporarily disable the keyboard
  • From: Army1987
• Re: How to temporarily disable the keyboard
  • From: Army1987
• Re: How to temporarily disable the keyboard
  • From: Ivan Gotovchits
• Re: How to temporarily disable the keyboard
  • From: Ivan Gotovchits
• Re: second column of ls -l doesn't show number of hard links
  • From: Barry Margolin
• Re: (POSIX?) Machine independent data passing?
  • From: Logan Shaw
• Re: How to temporarily disable the keyboard
  • From: David Schwartz
• Re: How to temporarily disable the keyboard
  • From: David Schwartz
• Re: check memory protection
  • From: Scott Lurndal
• Re: check memory protection
  • From: Scott Lurndal
• Re: check memory protection
  • From: Chris Friesen
• Re: check memory protection
  • From: Måns Rullgård
• check memory protection
  • From: Javier
• Unix Administrator in Milwaukee
  • From: lubna@xxxxxxxxxxx
• Re: How to temporarily disable the keyboard
  • From: Ben Bacarisse
• Re: How to temporarily disable the keyboard
  • From: Army1987
• Re: (POSIX?) Machine independent data passing?
  • From: Ben Bacarisse
• Re: How to temporarily disable the keyboard
  • From: Ben Bacarisse
• Re: How to temporarily disable the keyboard
  • From: Army1987
• Re: How to temporarily disable the keyboard
  • From: crox
• Re: How to temporarily disable the keyboard
  • From: Army1987
• Re: How to temporarily disable the keyboard
  • From: Army1987
• Re: How to temporarily disable the keyboard
  • From: David Schwartz
• Re: How to temporarily disable the keyboard
  • From: Ivan Gotovchits
• Re: How to temporarily disable the keyboard
  • From: Ivan Gotovchits
• Re: How to temporarily disable the keyboard
  • From: Army1987
• Re: How to temporarily disable the keyboard
  • From: Army1987
• Re: How to temporarily disable the keyboard
  • From: Ivan Gotovchits
• Re: (POSIX?) Machine independent data passing?
  • From: Alan Woodland
• How to temporarily disable the keyboard
  • From: Army1987
• Re: (POSIX?) Machine independent data passing?
  • From: Ivan Gotovchits
• Re: Zombie Process :
  • From: Roy
• Re: (POSIX?) Machine independent data passing?
  • From: Logan Shaw
• Re: (POSIX?) Machine independent data passing?
  • From: Barry Margolin
• Re: Zombie Process :
  • From: David Schwartz
• (POSIX?) Machine independent data passing?
  • From: Alan Woodland
• Re: Zombie Process :
  • From: moi
• Re: Zombie Process :
  • From: David Schwartz
• Re: Linux "frob" of the parallel port control register
  • From: philbo30
• Re: Linux "frob" of the parallel port control register
  • From: John W. Krahn
• Re: Zombie Process :
  • From: Al Balmer
• Re: daemon and the controlling terminal
  • From: ta0kira
• Re: Zombie Process :
  • From: Lew Pitcher
• Re: Attempting to set file descriptors to non blocking: tests fail
  • From: Michael
• Re: Zombie Process :
  • From: Ivan Gotovchits
• Linux "frob" of the parallel port control register
  • From: philbo30
• Re: Attempting to set file descriptors to non blocking: tests fail
  • From: Michael
• Re: Zombie Process :
  • From: nag
• Re: Permission Denied Error on execl !
  • From: Giorgos Keramidas
• Zombie Process :
  • From: Roy
• Re: Permission Denied Error on execl !
  • From: Roy
• Re: BSD TCP/IP stack implementation
  • From: Rainer Weikusat
• Re: Attempting to set file descriptors to non blocking: tests fail
  • From: moi
• Re: daemon and the controlling terminal
  • From: John Tsiombikas
• Re: BSD TCP/IP stack implementation
  • From: John Tsiombikas
• Re: BSD TCP/IP stack implementation
  • From: Ivan Gotovchits
• Re: BSD TCP/IP stack implementation
  • From: Pascal Bourguignon
• Re: BSD TCP/IP stack implementation
  • From: Ian Collins
• Re: daemon and the controlling terminal
  • From: Ivan Gotovchits
• BSD TCP/IP stack implementation
  • From: Ivan Gotovchits
• Re: Asynchromous interprocess message queue (possible with fifo ?)
  • From: ta0kira
• Re: daemon and the controlling terminal
  • From: ta0kira
• Re: Attempting to set file descriptors to non blocking: tests fail
  • From: SM Ryan
• Re: Permission Denied Error on execl !
  • From: John Tsiombikas
• Re: Attempting to set file descriptors to non blocking: tests fail
  • From: Michael
• Re: Attempting to set file descriptors to non blocking: tests fail
  • From: Ben Bacarisse
• Re: Attempting to set file descriptors to non blocking: tests fail
  • From: moi
• Re: Attempting to set file descriptors to non blocking: tests fail
  • From: SM Ryan
• Re: Attempting to set file descriptors to non blocking: tests fail
  • From: moi
• Attempting to set file descriptors to non blocking: tests fail
  • From: Michael
• Re: mmap page cahe on Linux
  • From: moi
• Re: Permission Denied Error on execl !
  • From: moi
• Re: mmap page cahe on Linux
  • From: softari22
• Re: Permission Denied Error on execl !
  • From: Robert Gamble
• Re: Permission Denied Error on execl !
  • From: Roy
• Re: Permission Denied Error on execl !
  • From: Robert Gamble
• Re: Permission Denied Error on execl !
  • From: moi
• Re: Permission Denied Error on execl !
  • From: Roy
• Re: Permission Denied Error on execl !
  • From: moi
• Permission Denied Error on execl !
  • From: Roy
• Re: HTTP over TLS protocol
  • From: Rainer Weikusat
• Re: mmap page cahe on Linux
  • From: moi
• mmap page cahe on Linux
  • From: softari22
• Re: C++ CGI Accessing Webpage
  • From: Logan Shaw
• Re: HTTP over TLS protocol
  • From: Ulrich Eckhardt
• Re: C++ CGI Accessing Webpage
  • From: Russell Wood
• Re: C++ CGI Accessing Webpage
  • From: John Tsiombikas
• Re: C++ CGI Accessing Webpage
  • From: SM Ryan
• Re: C++ CGI Accessing Webpage
  • From: Ian Collins
• Re: C++ CGI Accessing Webpage
  • From: joseph cook
• Re: C++ CGI Accessing Webpage
  • From: Robert Harris
• C++ CGI Accessing Webpage
  • From: joseph cook
• HTTP over TLS protocol
  • From: chsalvia
• Re: second column of ls -l doesn't show number of hard links
  • From: SM Ryan
• Re: second column of ls -l doesn't show number of hard links
  • From: Ben Bacarisse
• Re: second column of ls -l doesn't show number of hard links
  • From: Logan Shaw
• Re: second column of ls -l doesn't show number of hard links
  • From: Robert Gamble
• Re: second column of ls -l doesn't show number of hard links
  • From: Ben Bacarisse
• Re: ABOUT bc command
  • From: Gianni Mariani
• Re: Write to executable which has done execve
  • From: Bronson
• Re: Bash Shell Script Part II
  • From: Ben Bacarisse
• Bash Shell Script Part II
  • From: Ashish
• Re: mmap system call
  • From: Scott Lurndal
• Re: mmap system call
  • From: Gianni Mariani
• Re: ABOUT bc command
  • From: Jens Thoms Toerring
• ABOUT bc command
  • From: mukesh tiwari
• mmap system call
  • From: Rakesh UV
• Re: Write to executable which has done execve
  • From: Giorgos Keramidas
• Re: Write to executable which has done execve
  • From: Frank Cusack
• Re: Linux sysinfo on Solaris?
  • From: Mark Holland
• Re: Write to executable which has done execve
  • From: Scott Lurndal
• Re: Write to executable which has done execve
  • From: Frank Cusack
• Re: Linux sysinfo on Solaris?
  • From: Eric Sosman
• Re: Linux sysinfo on Solaris?
  • From: Alan Woodland
• Re: Simulate qui thread in console app and recieve signals
  • From: Maxim Yegorushkin
• Simulate qui thread in console app and recieve signals
  • From: Bronson
• Re: Write to executable which has done execve
  • From: Bronson
• Re: Linux sysinfo on Solaris?
  • From: Casper H . S . Dik
• Re: Linux sysinfo on Solaris?
  • From: Mark Holland
• Re: Linux sysinfo on Solaris?
  • From: Eric Sosman
• Re: One last questions about daemons
  • From: yellowchart
• Re: malloc_size
  • From: Maxim Yegorushkin
• Re: Implementing an interface
  • From: Jens Thoms Toerring
• Re: Implementing an interface
  • From: bcpkh
• Re: Bash Shell Script
  • From: Måns Rullgård
• Linux sysinfo on Solaris?
  • From: Mark Holland
• Re: Bash Shell Script
  • From: John Tsiombikas (Nuclear / Mindlapse)
• Re: One last questions about daemons
  • From: Alex Fraser
• Re: Bash Shell Script
  • From: Giorgos Keramidas
• Re: Bash Shell Script
  • From: Stephane CHAZELAS
• Re: One last questions about daemons
  • From: Logan Shaw
• Re: Bash Shell Script
  • From: Jim Cochrane
• Re: Write to executable which has done execve
  • From: Frank Cusack
• Re: Write to executable which has done execve
  • From: Bronson
• Re: One last questions about daemons
  • From: Scott Lurndal
• Re: One last questions about daemons
  • From: David Schwartz
• Re: Write to executable which has done execve
  • From: David Schwartz
• Re: How to know the function name by function pointer's address
  • From: Pascal Bourguignon
• Re: How to know the function name by function pointer's address
  • From: Chisin
• Re: malloc_size
  • From: Gary R. Schmidt
• malloc_size
  • From: chsalvia
• Re: Write to executable which has done execve
  • From: Bronson
• Re: Implementing an interface
  • From: Jens Thoms Toerring
• Re: daemon and the controlling terminal
  • From: James Carlson
• Re: One last questions about daemons
  • From: K-mart Cashier
• Re: Write to executable which has done execve
  • From: Logan Shaw
• Implementing an interface
  • From: bcpkh
• Re: Write to executable which has done execve
  • From: Pascal Bourguignon
• Re: Write to executable which has done execve
  • From: Bronson
• Re: Bash Shell Script
  • From: Stephane CHAZELAS
• Re: computer programings
  • From: Russell Wood
• Re: Bash Shell Script
  • From: Jim Cochrane
• Re: One last questions about daemons
  • From: Logan Shaw
• Re: Write to executable which has done execve
  • From: Pascal Bourguignon
• Re: Write to executable which has done execve
  • From: David Schwartz
• Write to executable which has done execve
  • From: Bronson
• Re: One last questions about daemons
  • From: David Schwartz
• Re: Keep a fifo's name until the close of its last connected fd
  • From: David Schwartz
• Re: Program to scan directories
  • From: Bill Marcum
• Re: One last questions about daemons
  • From: Erik Max Francis
• Re: Debugger to watch memory content
  • From: Paul Pluzhnikov
• Re: One last questions about daemons
  • From: Barry Margolin
• Re: One last questions about daemons
  • From: Barry Margolin
• Re: One last questions about daemons
  • From: K-mart Cashier
• Re: One last questions about daemons
  • From: Pascal Bourguignon
• computer programings
  • From: joh
• One last questions about daemons
  • From: K-mart Cashier
• Re: Debugger to watch memory content
  • From: Måns Rullgård
• Re: Bash Shell Script
  • From: Robert Harris
• Debugger to watch memory content
  • From: Tim Frink
• Re: Bash Shell Script
  • From: Stephane CHAZELAS
• Re: Bash Shell Script
  • From: Gary R. Schmidt
• Re: Bash Shell Script
  • From: Robert Harris
• Re: Bash Shell Script
  • From: Stephane CHAZELAS
• Re: Bash Shell Script
  • From: Robert Harris
• Re: (Free|Net|Open)BSD behavior
  • From: Jens Thoms Toerring
• Re: (Free|Net|Open)BSD behavior
  • From: Jens Thoms Toerring
• Re: Bash Shell Script
  • From: Jim Cochrane
• Re: (Free|Net|Open)BSD behavior
  • From: Giorgos Keramidas
• Re: Keep a fifo's name until the close of its last connected fd
  • From: Barry Margolin
• Re: How do you get ECONNRESET on recv?
  • From: Barry Margolin
• Re: fork on multiple cpu server
  • From: Barry Margolin
• Re: daemon and the controlling terminal
  • From: Barry Margolin
• Re: Keep a fifo's name until the close of its last connected fd
  • From: David Schwartz
• Re: Bash Shell Script
  • From: John Gordon
• Re: Bash Shell Script
  • From: Robert Harris
• Bash Shell Script
  • From: Ashish
• Re: How do you get ECONNRESET on recv?
  • From: Rick Jones
• make fails building gsoap on AIX 5.1
  • From: endaman
• Re: scp with xargs
  • From: Ulrich Eckhardt
• Re: (Free|Net|Open)BSD behavior
  • From: Jens Thoms Toerring
• Re: using PACKET_STATISTICS to get packet drop count
  • From: Spoon
• Re: program logic based on endianness
  • From: Pascal Bourguignon
• Re: program logic based on endianness
  • From: Eric Sosman
• program logic based on endianness
  • From: sam_cit
• Re: Does sigwait catch SIGCHLD?
  • From: Maxim Yegorushkin
• Re: How to know the function name by function pointer's address
  • From: Pascal Bourguignon
• Re: How to know the function name by function pointer's address
  • From: Maxim Yegorushkin
• Re: How to know the function name by function pointer's address
  • From: Gianni Mariani
• How to set non standard baudrates for tty device.
  • From: venu
• Re: (Free|Net|Open)BSD behavior
  • From: Giorgos Keramidas
• How to know the function name by function pointer's address
  • From: Chisin
• Re: Does sigwait catch SIGCHLD?
  • From: guenther@xxxxxxxxx
• Re: (Free|Net|Open)BSD behavior
  • From: Jens Thoms Toerring
• Re: Context of error messages with respect to BSD sockets
  • From: Michael
• Re: A process is getting killed
  • From: Bin Chen
• Re: A process is getting killed
  • From: Rainer Weikusat
• Re: A process is getting killed
  • From: Ian Collins
• A process is getting killed
  • From: monty
• Re: fork on multiple cpu server
  • From: Logan Shaw
• Re: using PACKET_STATISTICS to get packet drop count
  • From: Bin Chen
• Re: Does sigwait catch SIGCHLD?
  • From: Bin Chen
• Re: daemon and the controlling terminal
  • From: K-mart Cashier
• Re: daemon and the controlling terminal
  • From: K-mart Cashier
• scp with xargs
  • From: kimberly . shaffer
• Re: How do you get ECONNRESET on recv?
  • From: Barry Margolin
• Re: daemon and the controlling terminal
  • From: Barry Margolin
• Re: How do you get ECONNRESET on recv?
  • From: Rick Jones
• Re: How do you get ECONNRESET on recv?
  • From: Barry Margolin
• Re: Context of error messages with respect to BSD sockets
  • From: Barry Margolin
• daemon and the controlling terminal
  • From: K-mart Cashier
• Re: Keep a fifo's name until the close of its last connected fd
  • From: Barry Margolin
• Re: (Free|Net|Open)BSD behavior
  • From: Giorgos Keramidas
• (Free|Net|Open)BSD behavior
  • From: Jens Thoms Toerring
• using PACKET_STATISTICS to get packet drop count
  • From: phuong.d.nguyen
• Does sigwait catch SIGCHLD?
  • From: chsalvia
• Re: How do you get ECONNRESET on recv?
  • From: James Carlson
• Re: How do you get ECONNRESET on recv?
  • From: Rick Jones
• Re: grep to find content in between curly braces, "{" and "},"
  • From: James Antill
• Re: grep to find content in between curly braces, "{" and "},"
  • From: Stephane CHAZELAS
• grep to find content in between curly braces, "{" and "},"
  • From: krisworld
• Re: How do you get ECONNRESET on recv?
  • From: Andrei Voropaev
• Re: fork on multiple cpu server
  • From: Chris Friesen
• How do you get ECONNRESET on recv?
  • From: chsalvia
• Re: Context of error messages with respect to BSD sockets
  • From: Michael
• Re: fork on multiple cpu server
  • From: Jens Thoms Toerring
• fork on multiple cpu server
  • From: sc_wizard29@xxxxxxxxxxx
• Re: Program to scan directories
  • From: Paul Uiterlinden
• Re: Context of error messages with respect to BSD sockets
  • From: Michael
• Re: Keep a fifo's name until the close of its last connected fd
  • From: code17
• Re: Keep a fifo's name until the close of its last connected fd
  • From: code17
• Re: Keep a fifo's name until the close of its last connected fd
  • From: code17
• Re: Keep a fifo's name until the close of its last connected fd
  • From: code17
• Re: Context of error messages with respect to BSD sockets
  • From: Rainer Weikusat
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: Sheth Raxit
• Context of error messages with respect to BSD sockets
  • From: Michael
• Re: Keep a fifo's name until the close of its last connected fd
  • From: David Schwartz
• Re: shell scripting
  • From: harry
• Re: Keep a fifo's name until the close of its last connected fd
  • From: Barry Margolin
• Re: Keep a fifo's name until the close of its last connected fd
  • From: SM Ryan
• Re: simple question about implicit declaration error
  • From: michael
• Re: Program to scan directories
  • From: David Schwartz
• Re: Keep a fifo's name until the close of its last connected fd
  • From: Eric Sosman
• Re: Keep a fifo's name until the close of its last connected fd
  • From: Jens Thoms Toerring
• Re: Keep a fifo's name until the close of its last connected fd
  • From: code17
• Re: Keep a fifo's name until the close of its last connected fd
  • From: code17
• Re: Keep a fifo's name until the close of its last connected fd
  • From: Jens Thoms Toerring
• Re: Keep a fifo's name until the close of its last connected fd
  • From: code17
• Re: Keep a fifo's name until the close of its last connected fd
  • From: Eric Sosman
• Re: Keep a fifo's name until the close of its last connected fd
  • From: Mark Rafn
• Re: Keep a fifo's name until the close of its last connected fd
  • From: code17
• Re: Keep a fifo's name until the close of its last connected fd
  • From: Jens Thoms Toerring
• Re: Keep a fifo's name until the close of its last connected fd
  • From: SM Ryan
• Re: problem of linking libraries with GC_MALLOC
  • From: SM Ryan
• Re: Program to scan directories
  • From: Stephane CHAZELAS
• Re: Program to scan directories
  • From: Stephane CHAZELAS
• Keep a fifo's name until the close of its last connected fd
  • From: code17
• Keep a fifo's name until the close of its last connected fd
  • From: code17
• Re: Program to scan directories
  • From: vonrog
• Re: Program to scan directories
  • From: vonrog
• Re: Program to scan directories
  • From: Stephane CHAZELAS
• Re: Program to scan directories
  • From: vonrog
• Re: Program to scan directories
  • From: Lew Pitcher
• Re: Program to scan directories
  • From: Stephane CHAZELAS
• Re: Program to scan directories
  • From: vonrog
• Re: Program to scan directories
  • From: Lew Pitcher
• Re: Program to scan directories
  • From: Stephane CHAZELAS
• Program to scan directories
  • From: vonrog
• Program to scan directories
  • From: vonrog
• Re: simple question about implicit declaration error
  • From: Gary R. Schmidt
• Re: simple question about implicit declaration error
  • From: Jens Thoms Toerring
• simple question about implicit declaration error
  • From: michael
• Re: shell scripting
  • From: TW
• problem of linking libraries with GC_MALLOC
  • From: jitender001001
• Re: shell scripting
  • From: Glenn Hutchings
• shell scripting
  • From: harry
• Re: How to find out date of craetion of directory in Unix.
  • From: jellybean stonerfish
• Re: Asynchromous interprocess message queue (possible with fifo ?)
  • From: toby
• Re: Script to edit a file
  • From: Giorgos Keramidas
• Re: Script to edit a file
  • From: John W. Krahn
• Re: Script to edit a file
  • From: SM Ryan
• Re: Script to edit a file
  • From: Henry Townsend
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: David Schwartz
• Re: Script to edit a file
  • From: Benjamin
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: James Carlson
• Re: Script to edit a file
  • From: Pascal Bourguignon
• Script to edit a file
  • From: Benjamin
• Re: How to find out date of craetion of directory in Unix.
  • From: Pascal Bourguignon
• Re: How to find out date of craetion of directory in Unix.
  • From: Lew Pitcher
• Re: File System and Performance
  • From: Casper H . S . Dik
• Re: How to find out date of craetion of directory in Unix.
  • From: Ian Collins
• Re: File System and Performance
  • From: Ian Collins
• How to find out date of craetion of directory in Unix.
  • From: Nikki
• Re: File System and Performance
  • From: Sheth Raxit
• Re: File System and Performance
  • From: Ian Collins
• File System and Performance
  • From: Sheth Raxit
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: Ian Collins
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: monty
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: Rainer Weikusat
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: Ian Collins
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: David Schwartz
• Re: Asynchromous interprocess message queue (possible with fifo ?)
  • From: William Pursell
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: William Pursell
• Re: Getting du down to a specified amount
  • From: Gordon Burditt
• Re: Asynchromous interprocess message queue (possible with fifo ?)
  • From: SM Ryan
• Re: Getting du down to a specified amount
  • From: David Schwartz
• Re: Asynchromous interprocess message queue (possible with fifo ?)
  • From: code17
• Re: Asynchromous interprocess message queue (possible with fifo ?)
  • From: Eric Sosman
• Asynchromous interprocess message queue (possible with fifo ?)
  • From: code17
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: David Schwartz
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: Maxim Yegorushkin
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: Stephane CHAZELAS
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: monty
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: James Carlson
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: Bin Chen
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: Spoon
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: monty
• Re: socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: Maxim Yegorushkin
• socket(AF_INET,SOCK_STREAM,0) function is returning with the errono 24
  • From: monty
• Re: Returning data from a sub-process to its parent.
  • From: remi.chateauneu@xxxxxxxxx
• Re: Reverse DNS
  • From: Rainer Weikusat
• Re: Reverse DNS
  • From: Barry Margolin
• Re: Autoupdate of current executed file
  • From: Barry Margolin
• Re: Reverse DNS
  • From: Logan Shaw
• Re: Reverse DNS
  • From: Gordon Burditt
• Reverse DNS
  • From: Bin Chen
• Re: Returning data from a sub-process to its parent.
  • From: Pascal Bourguignon
• Re: Returning data from a sub-process to its parent.
  • From: William Pursell
• Returning data from a sub-process to its parent.
  • From: remi.chateauneu@xxxxxxxxx
• Re: Autoupdate of current executed file
  • From: Bronson
• Re: I have no idea how to attack this problem
  • From: Spoon
• Re: Autoupdate of current executed file
  • From: Barry Margolin
• Re: Getting du down to a specified amount
  • From: syrbenders
• Autoupdate of current executed file
  • From: Bronson
• Re: Getting du down to a specified amount
  • From: Logan Shaw
• Re: Getting du down to a specified amount
  • From: Golden California Girls
• Re: Getting du down to a specified amount
  • From: Henry Townsend
• Re: Serial I/O troubles re: VTIME
  • From: Frank Cusack
• Re: Getting du down to a specified amount
  • From: Logan Shaw
• Re: Getting du down to a specified amount
  • From: Eric Sosman
• Getting du down to a specified amount
  • From: jnbbender
• Serial I/O troubles re: VTIME
  • From: Josiah Allen
• Re: Trying to grok Sys V message queue overflow behavior
  • From: Richard Eich
• Re: Trying to grok Sys V message queue overflow behavior
  • From: Scott Lurndal
• Re: Trying to grok Sys V message queue overflow behavior
  • From: Richard Eich
• Re: Problem with fork()
  • From: William Pursell
• Re: Trying to grok Sys V message queue overflow behavior
  • From: Maxim Yegorushkin
• Trying to grok Sys V message queue overflow behavior
  • From: Richard Eich
• Re: memory fragmentation with malloc
  • From: Rainer Weikusat
• Re: how to order ld to use a specific libstdc++ version ?
  • From: Paul Pluzhnikov
• Re: memory fragmentation with malloc
  • From: Rainer Weikusat
• Re: memory fragmentation with malloc
  • From: G. Maly
• Re: strange csh script behavior only in certain account
  • From: Michael Zawrotny
• Re: memory fragmentation with malloc
  • From: Giorgos Keramidas
• Re: Problem with fork()
  • From: Army1987
• Re: how to order ld to use a specific libstdc++ version ?
  • From: Maxim Yegorushkin
• Re: memory fragmentation with malloc
  • From: G. Maly
• Re: memory fragmentation with malloc
  • From: Rainer Weikusat
• Re: Scatter-gather I/O and copies
  • From: Barry Margolin
• Re: How to check whether a file ID is a terminal?
  • From: Roger Leigh
• Re: strange csh script behavior only in certain account
  • From: Ben Bacarisse
• Re: Problem with fork()
  • From: William Pursell
• Re: strange csh script behavior only in certain account
  • From: chengen . li
• Re: memory fragmentation with malloc
  • From: Giorgos Keramidas
• Re: Question regarding UNIX access() call
  • From: Fantoosh B
• Re: Question regarding UNIX access() call
  • From: Fantoosh B
• Re: strange csh script behavior only in certain account
  • From: Ben Bacarisse
• Re: Question regarding UNIX access() call
  • From: Casper H . S . Dik
• Re: Problem with fork()
  • From: Army1987
• Re: strange csh script behavior only in certain account
  • From: Bill Marcum
• Re: strange csh script behavior only in certain account
  • From: Robert Harris
• Re: Scatter-gather I/O and copies
  • From: Rainer Weikusat
• Re: strange csh script behavior only in certain account
  • From: chengen . li
• Re: memory fragmentation with malloc
  • From: G. Maly
• Re: strange csh script behavior only in certain account
  • From: Robert Harris
• Re: Problem with fork()
  • From: James Carlson
• Problem with fork()
  • From: Army1987
• strange csh script behavior only in certain account
  • From: chengen . li
• Re: Scatter-gather I/O and copies
  • From: Richard
• Re: Scatter-gather I/O and copies
  • From: Spoon
• Re: Scatter-gather I/O and copies
  • From: Rainer Weikusat
• Re: Scatter-gather I/O and copies
  • From: Richard
• Re: memory fragmentation with malloc
  • From: Rainer Weikusat
• Re: memory fragmentation with malloc
  • From: G. Maly
• Re: Scatter-gather I/O and copies
  • From: Rainer Weikusat
• Re: memory fragmentation with malloc
  • From: Giorgos Keramidas
• Re: memory fragmentation with malloc
  • From: G. Maly
• Re: deletion of the last node in the single linked list...
  • From: James Antill
• Re: memory fragmentation with malloc
  • From: Paul Pluzhnikov
• Re: memory fragmentation with malloc
  • From: Paul Pluzhnikov
• Re: Question regarding UNIX access() call
  • From: guenther@xxxxxxxxx
• Re: Scatter-gather I/O and copies
  • From: Barry Margolin
• Question regarding UNIX access() call
  • From: Fantoosh B

• Security
• UNIX
• Linux
• Coding
• Usenet

• Mailing-Lists
• Newsgroups
• About
• Privacy
• Search
• Imprint

unix.derkeiler.com  > Newsgroups  > comp.unix.programmer  > 2007-08