comp.unix.programmer

• Thread Index

---

• Re: gethostbyname
  • From: Ian Collins
• Re: error on second write to tape on 64bit linux system
  • From: David Mathog
• Re: error on second write to tape on 64bit linux system
  • From: Scott Lurndal
• Re: error on second write to tape on 64bit linux system
  • From: David Mathog
• Re: error on second write to tape on 64bit linux system
  • From: David Mathog
• error on second write to tape on 64bit linux system
  • From: David Mathog
• Re: send and receive buffer size befor and after connection.
  • From: Rick Jones
• Re: gethostbyname
  • From: Rick Jones
• Simple way to mix I/O multiplexing and signals
  • From: Rainer Weikusat
• Re: gethostbyname
  • From: James Kanze
• Re: How to call functions with variable number of arguments?
  • From: Eric Sosman
• Re: file deletion in a directory with some conditions .
  • From: John Gordon
• Re: gethostbyname
  • From: jellybean stonerfish
• Re: gethostbyname
  • From: Rainer Weikusat
• send and receive buffer size befor and after connection.
  • From: lak
• Re: gethostbyname
  • From: lak
• Re: How to call functions with variable number of arguments?
  • From: Kenny McCormack
• file deletion in a directory with some conditions .
  • From: aki
• Re: gethostbyname
  • From: Ian Collins
• gethostbyname
  • From: lak
• Re: sending recv() data to a file
  • From: Gordon Burditt
• Re: How can I get daylight saving start/end dates?
  • From: Gordon Burditt
• Re: TCP server eating up the whole CPU
  • From: Rainer Weikusat
• Re: TCP server eating up the whole CPU
  • From: arnuld
• Re: TCP server eating up the whole CPU
  • From: Rainer Weikusat
• Re: TCP server eating up the whole CPU
  • From: arnuld
• Re: TCP server eating up the whole CPU
  • From: Rainer Weikusat
• Re: TCP server eating up the whole CPU
  • From: arnuld
• Re: TCP server eating up the whole CPU
  • From: malc
• Re: sending recv() data to a file
  • From: arnuld
• Re: How can I get daylight saving start/end dates?
  • From: thagor2008
• Re: How can I get daylight saving start/end dates?
  • From: Gordon Burditt
• How can I get daylight saving start/end dates?
  • From: thagor2008
• Re: why i cant find function names in stack trace with gdb
  • From: Bin Chen
• Re: TCP server eating up the whole CPU
  • From: arnuld
• Re: sending recv() data to a file
  • From: Gordon Burditt
• Re: why i cant find function names in stack trace with gdb
  • From: Gordon Burditt
• Re: sending recv() data to a file
  • From: arnuld
• Re: timeval structure on Solaris 10
  • From: Ian Collins
• Re: why i cant find function names in stack trace with gdb
  • From: e2point
• Re: why i cant find function names in stack trace with gdb
  • From: Bin Chen
• Re: sending recv() data to a file
  • From: Gordon Burditt
• Re: why i cant find function names in stack trace with gdb
  • From: Gordon Burditt
• Re: File Unique ID
  • From: David Schwartz
• Re: How to call functions with variable number of arguments?
  • From: fjblurt
• Re: How to call functions with variable number of arguments?
  • From: fjblurt
• Re: File Unique ID
  • From: fjblurt
• Re: timeval structure on Solaris 10
  • From: fjblurt
• Re: timeval structure on Solaris 10
  • From: Ian Collins
• Re: why i cant find function names in stack trace with gdb
  • From: e2point
• Re: why i cant find function names in stack trace with gdb
  • From: Jens Thoms Toerring
• Re: sending recv() data to a file
  • From: K-mart Cashier
• why i cant find function names in stack trace with gdb
  • From: e2point
• Re: TCP server eating up the whole CPU
  • From: malc
• Re: TCP server eating up the whole CPU
  • From: arnuld
• Re: performance implications of releasing resources and context switches
  • From: Ambrose Silk
• Re: TCP server eating up the whole CPU
  • From: Rainer Weikusat
• Re: TCP server eating up the whole CPU
  • From: arnuld
• Re: TCP server eating up the whole CPU
  • From: arnuld
• Re: TCP server eating up the whole CPU
  • From: arnuld
• Re: performance implications of releasing resources and context switches
  • From: Rainer Weikusat
• Re: TCP server eating up the whole CPU
  • From: Bin Chen
• TCP server eating up the whole CPU
  • From: arnuld
• Re: sending recv() data to a file
  • From: arnuld
• Re: good stuff on thread programming
  • From: Bin Chen
• Software Package Free! ... about our Free Software
  • From: hpeeeter1
• Re: performance implications of releasing resources and context switches
  • From: Silverlock
• Re: File Unique ID
  • From: phil-news-nospam
• good stuff on thread programming
  • From: sinbad
• Re: performance implications of releasing resources and context switches
  • From: Ambrose Silk
• Re: File Unique ID
  • From: Bin Chen
• Re: performance implications of releasing resources and context switches
  • From: David Schwartz
• Re: File Unique ID
  • From: David Schwartz
• Re: File Unique ID
  • From: David Schwartz
• Re: File Unique ID
  • From: Ambrose Silk
• Re: performance implications of releasing resources and context switches
  • From: Gordon Burditt
• Re: File Unique ID
  • From: Gordon Burditt
• Re: File Unique ID
  • From: guenther@xxxxxxxxx
• Re: File Unique ID
  • From: David Schwartz
• Re: performance implications of releasing resources and context switches
  • From: fjblurt
• Re: performance implications of releasing resources and context switches
  • From: Ambrose Silk
• Re: File Unique ID
  • From: Ambrose Silk
• Re: File Unique ID
  • From: David Schwartz
• Re: performance implications of releasing resources and context switches
  • From: fjblurt
• Re: File Unique ID
  • From: David Schwartz
• performance implications of releasing resources and context switches
  • From: Ambrose Silk
• Re: File Unique ID
  • From: Ambrose Silk
• Re: File Unique ID
  • From: K-mart Cashier
• Re: File Unique ID
  • From: Scott Lurndal
• Re: File Unique ID
  • From: David Schwartz
• Re: File Unique ID
  • From: edwin ng
• Re: File Unique ID
  • From: Jens Thoms Toerring
• File Unique ID
  • From: Bercea Gabriel
• Re: sending recv() data to a file
  • From: fjblurt
• Re: sending recv() data to a file
  • From: arnuld
• Now registers the member to bestow 100 integrals! PayPal
  • From: yuwenwu006
• Re: UNIX file I/O
  • From: Rainer Weikusat
• Re: gettext base language: Does it have to be english
  • From: James Kanze
• Re: gdb vs fortran RTL -- fight for SIGSEGV
  • From: Ron Ford
• Re: gettext base language: Does it have to be english
  • From: ckirchho
• Re: UNIX file I/O
  • From: Jens Thoms Toerring
• Re: UNIX file I/O
  • From: Phil Hobbs
• China monopoly Jordans 23 Fusion AF1 Coach Shoes Coach Sandals Gucci boots Timberland Boots at best price!
  • From: www.getvogue.com
• Re: Spawning process with environment variables
  • From: Rainer Weikusat
• Re: gettext base language: Does it have to be english
  • From: James Kanze
• Re: gettext base language: Does it have to be english
  • From: Bin Chen
• Re: IP_HDRINCL
  • From: lak
• Re: IP_HDRINCL
  • From: David Schwartz
• Re: UNIX file I/O
  • From: David Schwartz
• Re: sending recv() data to a file
  • From: David Schwartz
• Re: UNIX file I/O
  • From: Jens Thoms Toerring
• UNIX file I/O
  • From: alexandrug
• Re: Xlib: XQueryPointer() and Button4Mask/Button5Mask
  • From: dj3vande
• Re: Xlib: XQueryPointer() and Button4Mask/Button5Mask
  • From: regis
• Re: Xlib: XQueryPointer() and Button4Mask/Button5Mask
  • From: regis
• Re: Xlib: XQueryPointer() and Button4Mask/Button5Mask
  • From: dj3vande
• Re: Xlib: XQueryPointer() and Button4Mask/Button5Mask
  • From: regis
• Re: sending recv() data to a file
  • From: phil-news-nospam
• Re: Spawning process with environment variables
  • From: Drew Lawson
• Re: Spawning process with environment variables
  • From: Ben Bacarisse
• Re: sending recv() data to a file
  • From: fjblurt
• gettext base language: Does it have to be english
  • From: ckirchho
• Re: Spawning process with environment variables
  • From: Rainer Weikusat
• Re: Spawning process with environment variables
  • From: Drew Lawson
• Re: Spawning process with environment variables
  • From: Ben Bacarisse
• Re: Spawning process with environment variables
  • From: Drew Lawson
• Re: sending recv() data to a file
  • From: Ben Bacarisse
• Re: Xlib: XQueryPointer() and Button4Mask/Button5Mask
  • From: Jens Thoms Toerring
• Re: Spawning process with environment variables
  • From: Rainer Weikusat
• Re: Spawning process with environment variables
  • From: Rainer Weikusat
• Re: sending recv() data to a file
  • From: arnuld
• Re: sending recv() data to a file
  • From: fjblurt
• Re: sending recv() data to a file
  • From: arnuld
• Re: IP_HDRINCL
  • From: lak
• Re: gdb vs fortran RTL -- fight for SIGSEGV
  • From: Paul Pluzhnikov
• Re: Spawning process with environment variables
  • From: fjblurt
• Re: gdb vs fortran RTL -- fight for SIGSEGV
  • From: Paul Pluzhnikov
• Re: gdb vs fortran RTL -- fight for SIGSEGV
  • From: fjblurt
• Re: Spawning process with environment variables
  • From: Bin Chen
• Re: Spawning process with environment variables
  • From: Ben Bacarisse
• Re: Xlib: XQueryPointer() and Button4Mask/Button5Mask
  • From: regis
• Re: Spawning process with environment variables
  • From: Scott Lurndal
• Re: send & MSG_DONTWAIT
  • From: David Schwartz
• Re: Spawning process with environment variables
  • From: Ben Bacarisse
• Re: Spawning process with environment variables
  • From: Rainer Weikusat
• Re: Spawning process with environment variables
  • From: Scott Lurndal
• Re: netstat output
  • From: Rick Jones
• Re: send & MSG_DONTWAIT
  • From: Rick Jones
• Re: Spawning process with environment variables
  • From: Jens Thoms Toerring
• Re: Spawning process with environment variables
  • From: Drew Lawson
• Re: send & MSG_DONTWAIT
  • From: Kyku
• Re: Spawning process with environment variables
  • From: Jens Thoms Toerring
• Re: IP_HDRINCL
  • From: Barry Margolin
• Re: Spawning process with environment variables
  • From: Rainer Weikusat
• Re: Xlib: XQueryPointer() and Button4Mask/Button5Mask
  • From: Scott Lurndal
• Re: gdb vs fortran RTL -- fight for SIGSEGV
  • From: Jacek Dziedzic
• Re: Spawning process with environment variables
  • From: Jens Thoms Toerring
• Re: gdb vs fortran RTL -- fight for SIGSEGV
  • From: Jacek Dziedzic
• Re: Spawning process with environment variables
  • From: Rainer Weikusat
• Re: Xlib: XQueryPointer() and Button4Mask/Button5Mask
  • From: Jens Thoms Toerring
• Re: Spawning process with environment variables
  • From: Rainer Weikusat
• Re: Spawning process with environment variables
  • From: dj3vande
• Re: Xlib: XQueryPointer() and Button4Mask/Button5Mask
  • From: dj3vande
• Re: Spawning process with environment variables
  • From: Sasha
• Xlib: XQueryPointer() and Button4Mask/Button5Mask
  • From: regis
• Re: sending recv() data to a file
  • From: Rainer Weikusat
• Re: sending recv() data to a file
  • From: phil-news-nospam
• adidas adicolor shoes PayPal
  • From: kjldf
• Re: Spawning process with environment variables
  • From: Rainer Weikusat
• Spawning process with environment variables
  • From: Sasha
• Intrusion Detection Strategies
  • From: arigano.spagety@xxxxxxxxx
• Re: netstat output
  • From: lak
• IP_HDRINCL
  • From: lak
• Re: netstat output
  • From: lak
• Re: sending recv() data to a file
  • From: David Schwartz
• Re: sending recv() data to a file
  • From: arnuld
• prada shoes snea kers cheap dior fendi puma whol esale from www.jumpmanlocker.com.cn
  • From: jumpmanlocker6
• Buy/sell/trade your used stuff and promote your small business to others in your area
  • From: busybeejoe
• netstat output
  • From: Naga
• machine figure
  • From: mcjason
• Re: Is Message passing good approach for multi-threaded applications?
  • From: William Ahern
• Re: Is Message passing good approach for multi-threaded applications?
  • From: phil-news-nospam
• Re: Problem with read(2) and pseudo-terminals
  • From: Edd
• Re: Is Message passing good approach for multi-threaded applications?
  • From: David Schwartz
• Re: Is Message passing good approach for multi-threaded applications?
  • From: John Koleszar
• Re: gdb vs fortran RTL -- fight for SIGSEGV
  • From: fjblurt
• Re: Is Message passing good approach for multi-threaded applications?
  • From: Rainer Weikusat
• Re: Is Message passing good approach for multi-threaded applications?
  • From: Moi
• Re: Is Message passing good approach for multi-threaded applications?
  • From: John Koleszar
• Re: Problem with read(2) and pseudo-terminals
  • From: Geoff Clare
• Re: why no palloc() ("permanent alloc")?
  • From: phil-news-nospam
• Re: why no palloc() ("permanent alloc")?
  • From: Rainer Weikusat
• Re: Is Message passing good approach for multi-threaded applications?
  • From: Bin Chen
• paypal wholesale women Prada
  • From: darenwu10086
• paypal wholesale High Prada
  • From: darenwu10086
• paypal wholesale Prada
  • From: darenwu10086
• Re: gdb vs fortran RTL -- fight for SIGSEGV
  • From: Paul Pluzhnikov
• Re: Duplicate symbols across shared libraries
  • From: Paul Pluzhnikov
• Re: Quick (hopefully) question regarding dlopen
  • From: S James S Stapleton
• Re: AF_UNIX connect()/bind()/listen() race
  • From: David Schwartz
• Re: Quick (hopefully) question regarding dlopen
  • From: David Schwartz
• AF_UNIX connect()/bind()/listen() race
  • From: Dan Colascione
• Re: why no palloc() ("permanent alloc")?
  • From: Eric Sosman
• Re: Quick (hopefully) question regarding dlopen
  • From: Marc
• Re: why no palloc() ("permanent alloc")?
  • From: Bernie Ohls
• Re: how big can automatic (stack) arrays be
  • From: phil-news-nospam
• Re: why no palloc() ("permanent alloc")?
  • From: phil-news-nospam
• Re: Is Message passing good approach for multi-threaded applications?
  • From: David Schwartz
• Re: Is Message passing good approach for multi-threaded applications?
  • From: David Schwartz
• Re: how big can automatic (stack) arrays be
  • From: David Schwartz
• Re: why no palloc() ("permanent alloc")?
  • From: David Schwartz
• Re: how big can automatic (stack) arrays be
  • From: Rainer Weikusat
• Re: why no palloc() ("permanent alloc")?
  • From: Rainer Weikusat
• Re: Quick (hopefully) question regarding dlopen
  • From: S James S Stapleton
• Re: Quick (hopefully) question regarding dlopen
  • From: S James S Stapleton
• Re: how big can automatic (stack) arrays be
  • From: Rainer Weikusat
• gdb vs fortran RTL -- fight for SIGSEGV
  • From: Jacek Dziedzic
• Re: how big can automatic (stack) arrays be
  • From: Rainer Weikusat
• Re: Problem with read(2) and pseudo-terminals
  • From: Edd
• Re: Duplicate symbols across shared libraries
  • From: Giorgos Keramidas
• Duplicate symbols across shared libraries
  • From: Brian Cole
• Re: Is Message passing good approach for multi-threaded applications?
  • From: Bin Chen
• Re: Quick (hopefully) question regarding dlopen
  • From: Bin Chen
• Re: Problem with read(2) and pseudo-terminals
  • From: Bin Chen
• Problem with read(2) and pseudo-terminals
  • From: Edd
• Re: how big can automatic (stack) arrays be
  • From: Don Morris
• Re: how big can automatic (stack) arrays be
  • From: Dirk Noß
• Re: how big can automatic (stack) arrays be
  • From: James Kanze
• Re: Steam tube guyes who developed tcp/ip on bsd
  • From: John Gordon
• Quick (hopefully) question regarding dlopen
  • From: S James S Stapleton
• Re: Is Message passing good approach for multi-threaded applications?
  • From: dj3vande
• cheap air jordan 22 PayPal
  • From: yuwenwu010
• Re: Is Message passing good approach for multi-threaded applications?
  • From: David Schwartz
• ioctl SIOCGSTAMP and sent packets..
  • From: frakie
• Is Message passing good approach for multi-threaded applications?
  • From: Behzad
• Re: files "." and ".." from readdir()
  • From: Geoff Clare
• Re: how big can automatic (stack) arrays be
  • From: Rainer Weikusat
• Re: how big can automatic (stack) arrays be
  • From: Don Morris
• Re: how big can automatic (stack) arrays be
  • From: James Kanze
• Re: how big can automatic (stack) arrays be
  • From: Rainer Weikusat
• Re: how big can automatic (stack) arrays be
  • From: James Kanze
• Re: how big can automatic (stack) arrays be
  • From: viza
• Re: how big can automatic (stack) arrays be
  • From: David Schwartz
• Re: Loose source option
  • From: lak
• SO_DEBUG in UDP socket
  • From: lak
• SO_DEBUG in UDP socket
  • From: lak
• Re: File Status programatically
  • From: fjblurt
• Re: how big can automatic (stack) arrays be
  • From: fjblurt
• Re: how big can automatic (stack) arrays be
  • From: Don Morris
• Re: how big can automatic (stack) arrays be
  • From: James Kanze
• cheap DG belt PayPal gift discount
  • From: yuwenwu006
• Re: why no palloc() ("permanent alloc")?
  • From: Bernie Ohls
• Re: files "." and ".." from readdir()
  • From: Rainer Weikusat
• Re: why no palloc() ("permanent alloc")?
  • From: phil-news-nospam
• We have many new activities on the website. PayPal
  • From: kjldf
• Re: files "." and ".." from readdir()
  • From: phil-news-nospam
• Re: how big can automatic (stack) arrays be
  • From: Rainer Weikusat
• how big can automatic (stack) arrays be
  • From: viza
• Re: files "." and ".." from readdir()
  • From: Rainer Weikusat
• Re: why no palloc() ("permanent alloc")?
  • From: Rainer Weikusat
• Re: why no palloc() ("permanent alloc")?
  • From: Paul Pluzhnikov
• Re: why no palloc() ("permanent alloc")?
  • From: Barry Margolin
• keyboard control in X windows
  • From: MarkA
• Re: why no palloc() ("permanent alloc")?
  • From: Joachim Schmitz
• Re: why no palloc() ("permanent alloc")?
  • From: Joachim Schmitz
• Re: why no palloc() ("permanent alloc")?
  • From: phil-news-nospam
• Re: why no palloc() ("permanent alloc")?
  • From: Joachim Schmitz
• Re: why no palloc() ("permanent alloc")?
  • From: phil-news-nospam
• Re: why no palloc() ("permanent alloc")?
  • From: David Schwartz
• Re: why no palloc() ("permanent alloc")?
  • From: Boon
• Re: why no palloc() ("permanent alloc")?
  • From: rahul
• why no palloc() ("permanent alloc")?
  • From: Bernie Ohls
• Re: files "." and ".." from readdir()
  • From: phil-news-nospam
• Re: difference between send and writev
  • From: Barry Margolin
• Re: difference between send and writev
  • From: K-mart Cashier
• Re: Steam tube guyes who developed tcp/ip on bsd
  • From: Barry Margolin
• Re: difference between send and writev
  • From: Barry Margolin
• Re: files "." and ".." from readdir()
  • From: Barry Margolin
• Re: difference between send and writev
  • From: Gordon Burditt
• Steam tube guyes who developed tcp/ip on bsd
  • From: nix
• Re: List of running processes in C++
  • From: Moi
• difference between send and writev
  • From: suesweet008
• difference between send and writev
  • From: susan
• Re: List of running processes in C++
  • From: jbo5112
• Re: files "." and ".." from readdir()
  • From: Rainer Weikusat
• Re: files "." and ".." from readdir()
  • From: phil-news-nospam
• We have many new activities on the website. PayPal
  • From: kjldf
• Re: Questions about getopt() (Linux)
  • From: berndj
• Re: files "." and ".." from readdir()
  • From: James Kanze
• Re: Loose source option
  • From: lak
• Re: files "." and ".." from readdir()
  • From: Geoff Clare
• Re: sending recv() data to a file
  • From: Jens Thoms Toerring
• sending recv() data to a file
  • From: arnuld
• Re: files "." and ".." from readdir()
  • From: phil-news-nospam
• Re: files "." and ".." from readdir()
  • From: phil-news-nospam
• Re: Question on ACE 's alternative and distributed computing?
  • From: Terry
• Re: Loose source option
  • From: Barry Margolin
• Re: Loose source option
  • From: Frank Cusack
• Re: Loose source option
  • From: Barry Margolin
• Re: IPPROTO_RAW
  • From: Barry Margolin
• 7 Unix Admin needed for contract position in Texas and Georgia - secret or interim clearance rqd
  • From: Gwenna Hunter
• moving pairs
  • From: mcjason
• Free Money Making Website
  • From: kowsi
• Free Money Making Website
  • From: kowsi
• Re: Loose source option
  • From: Frank Cusack
• Re: Dynamic aligned memory allocation
  • From: Moi
• Re: files "." and ".." from readdir()
  • From: Scott Lurndal
• Re: Questions about getopt() (Linux)
  • From: Rainer Weikusat
• Re: files "." and ".." from readdir()
  • From: Wayne C. Morris
• Re: File Status programatically
  • From: Gordon Burditt
• Re: Questions about getopt() (Linux)
  • From: Kenny McCormack
• Re: File Status programatically
  • From: Ralf Becker
• Re: files "." and ".." from readdir()
  • From: Måns Rullgård
• Re: files "." and ".." from readdir()
  • From: phil-news-nospam
• Re: what is Delivered-To: user:X.com@Y.com
  • From: Doug McIntyre
• what is Delivered-To: user:X.com@Y.com
  • From: jhl@xxxxxxxx
• Re: File Status programatically
  • From: Maxim Yegorushkin
• File Status programatically
  • From: Gamitech
• Re: Questions about getopt() (Linux)
  • From: Rainer Weikusat
• Re: Questions about getopt() (Linux)
  • From: Kenny McCormack
• Re: Questions about getopt() (Linux)
  • From: Kenny McCormack
• Re: echo client using threads
  • From: David Schwartz
• Re: Dynamic aligned memory allocation
  • From: Rainer Weikusat
• Re: Dynamic aligned memory allocation
  • From: Marco
• Re: Dynamic aligned memory allocation
  • From: Maxim Yegorushkin
• Re: Dynamic aligned memory allocation
  • From: Maxim Yegorushkin
• Question on ACE 's alternative and distributed computing?
  • From: Terry
• Re: Dynamic aligned memory allocation
  • From: Marco
• Re: Dynamic aligned memory allocation
  • From: Marco
• Re: files "." and ".." from readdir()
  • From: Måns Rullgård
• Save your computer , download files and musics
  • From: busiown
• Re: echo client using threads
  • From: arnuld
• Loose source option
  • From: lak
• Re: IPPROTO_RAW
  • From: lak
• Re: files "." and ".." from readdir()
  • From: Barry Margolin
• files "." and ".." from readdir()
  • From: phil-news-nospam
• Re: IPPROTO_RAW
  • From: Barry Margolin
• Re: web server with pool of thread ...again
  • From: Mr_John
• Re: List of running processes in C++
  • From: Moi
• Re: send & MSG_DONTWAIT
  • From: Rainer Weikusat
• Re: List of running processes in C++
  • From: jbo5112
• web server with pool of thread ...again
  • From: Mr_John
• Re: Making GNU gettext work
  • From: Scott Lurndal
• Re: Dynamic aligned memory allocation
  • From: Maxim Yegorushkin
• IPPROTO_RAW
  • From: lak
• Re: Dynamic aligned memory allocation
  • From: Moi
• Re: Questions about getopt() (Linux)
  • From: Rainer Weikusat
• Re: Questions about getopt() (Linux)
  • From: berndj
• Re: Dynamic aligned memory allocation
  • From: Marco
• Re: send & MSG_DONTWAIT
  • From: Rainer Weikusat
• Re: echo client using threads
  • From: David Schwartz
• Re: Making GNU gettext work
  • From: Daniel Kraft
• Re: echo client using threads
  • From: David Schwartz
• Re: echo client using threads
  • From: arnuld
• Re: echo client using threads
  • From: David Schwartz
• Re: echo client using threads
  • From: arnuld
• Re: SO_DEBUG
  • From: Ian Collins
• SO_DEBUG
  • From: lak
• Re: echo client using threads
  • From: arnuld
• Re: Making GNU gettext work
  • From: Scott Lurndal
• Making GNU gettext work
  • From: Daniel Kraft
• Re: send & MSG_DONTWAIT
  • From: David Schwartz
• Re: send & MSG_DONTWAIT
  • From: Rainer Weikusat
• Re: send & MSG_DONTWAIT
  • From: David Schwartz
• Re: echo client using threads
  • From: David Schwartz
• Re: Dynamic aligned memory allocation
  • From: Maxim Yegorushkin
• Re: echo client using threads
  • From: arnuld
• Re: echo client using threads
  • From: Jens Thoms Toerring
• Re: echo client using threads
  • From: arnuld
• Re: echo client using threads
  • From: arnuld
• Re: echo client using threads
  • From: Jens Thoms Toerring
• Re: echo client using threads
  • From: Jens Thoms Toerring
• Re: echo client using threads
  • From: Ike Naar
• Re: echo client using threads
  • From: Jens Thoms Toerring
• Re: echo client using threads
  • From: arnuld
• Dynamic aligned memory allocation
  • From: Marco
• Re: send & MSG_DONTWAIT
  • From: Rainer Weikusat
• Re: echo client using threads
  • From: arnuld
• Re: echo client using threads
  • From: David Schwartz
• echo client using threads
  • From: arnuld
• unix information
  • From: pavan
• Re: List of running processes in C++
  • From: David Schwartz
• Re: Pls sanity check: semtimedop(2) for FreeBSD
  • From: Michael B Allen
• Re: List of running processes in C++
  • From: jbo5112
• Re: List of running processes in C++
  • From: jbo5112
• Re: send & MSG_DONTWAIT
  • From: David Schwartz
• Re: Pls sanity check: semtimedop(2) for FreeBSD
  • From: Moi
• Re: Pls sanity check: semtimedop(2) for FreeBSD
  • From: ppi
• Re: send & MSG_DONTWAIT
  • From: Rainer Weikusat
• Re: send & MSG_DONTWAIT
  • From: Kyku
• CAR CHEAP INSURANCE
  • From: nancygroup2
• Re: send & MSG_DONTWAIT
  • From: Rainer Weikusat
• Wrong ACS_HLINE in ncurses-program on Televideo tvi 990
  • From: j . rupp
• Re: send & MSG_DONTWAIT
  • From: Barry Margolin
• Re: scandir(3) prototype arg 4
  • From: Barry Margolin
• Re: send & MSG_DONTWAIT
  • From: David Schwartz
• Re: send & MSG_DONTWAIT
  • From: Kyku
• Re: send & MSG_DONTWAIT
  • From: David Schwartz
• Re: send & MSG_DONTWAIT
  • From: Kyku
• Re: send & MSG_DONTWAIT
  • From: Alex Fraser
• send & MSG_DONTWAIT
  • From: Kyku
• Re: scandir(3) prototype arg 4
  • From: phil-news-nospam
• Re: scandir(3) prototype arg 4
  • From: Barry Margolin
• scandir(3) prototype arg 4
  • From: phil-news-nospam
• Pls sanity check: semtimedop(2) for FreeBSD
  • From: Michael B Allen
• Re: Louisianassa poliittinen laki kouluopetuksesta
  • From: Aleksi Jäntti
• DOT graph node properties
  • From: Stephan Ceram
• Re: linux - directory operations in c
  • From: phil-news-nospam
• Re: crashed unix process
  • From: ppi
• Re: killing process on AIX
  • From: Henrik Goldman
• Re: linux - directory operations in c
  • From: Scott Lurndal
• Re: crashed unix process
  • From: Rainer Weikusat
• Re: killing process on AIX
  • From: ppi
• Re: crashed unix process
  • From: ppi
• Re: linux - directory operations in c
  • From: Scott Lurndal
• Re: traceroute
  • From: Maxim Yegorushkin
• Re: opendir
  • From: Jon
• Re: determining Cygwin environment
  • From: Ralf Fassel
• Re: determining Cygwin environment
  • From: Gary R. Schmidt
• traceroute
  • From: lak
• Re: determining Cygwin environment
  • From: Bernie Ohls
• Re: determining Cygwin environment
  • From: Maxim Yegorushkin
• Re: List of running processes in C++
  • From: Maxim Yegorushkin
• Re: opendir
  • From: Ian Collins
• Re: opendir
  • From: Jon
• Re: opendir
  • From: Ian Collins
• Re: List of running processes in C++
  • From: David Schwartz
• Re: interposing library calls - here is one I want to do
  • From: David Schwartz
• Re: opendir
  • From: Jon
• List of running processes in C++
  • From: jbo5112
• Re: determining Cygwin environment
  • From: phil-news-nospam
• Re: linux - directory operations in c
  • From: phil-news-nospam
• Re: opendir
  • From: phil-news-nospam
• Re: opendir
  • From: Barry Margolin
• Re: Static library works everywhere but server
  • From: drhowarddrfine
• killing process on AIX
  • From: Henrik Goldman
• Re: Static library works everywhere but server
  • From: Gordon Burditt
• determining Cygwin environment
  • From: Bernie Ohls
• Re: opendir
  • From: MK
• wow am i sorry Jens
  • From: MK
• Re: linux - directory operations in c
  • From: shakahshakah@xxxxxxxxx
• Re: opendir
  • From: Eric Sosman
• Re: linux - directory operations in c
  • From: MK
• opendir
  • From: MK
• Re: linux - directory operations in c
  • From: Jens Thoms Toerring
• Re: linux - directory operations in c
  • From: Scott Lurndal
• Re: interposing library calls - here is one I want to do
  • From: Giorgos Keramidas
• Re: linux - directory operations in c
  • From: MK
• Re: Static library works everywhere but server
  • From: Jens Thoms Toerring
• Re: linux - directory operations in c
  • From: Jens Thoms Toerring
• Static library works everywhere but server
  • From: drhowarddrfine
• Re: Questions about getopt() (Linux)
  • From: Michael Kerrisk
• Re: crashed unix process
  • From: Rainer Weikusat
• crashed unix process
  • From: sinbad
• Re: linux - directory operations in c
  • From: Barry Margolin
• Re: linux - directory operations in c
  • From: MK
• Re: sending echo to all clients
  • From: David Schwartz
• Re: using socket fd to another pid (?)
  • From: Beagle
• Re: sending echo to all clients
  • From: K-mart Cashier
• Re: what are .Plo files
  • From: Måns Rullgård
• Re: interposing library calls - here is another one
  • From: David Schwartz
• Re: sending echo to all clients
  • From: David Schwartz
• Re: what are .Plo files
  • From: phil-news-nospam
• Re: what are .Plo files
  • From: Måns Rullgård
• Re: linux - directory operations in c
  • From: phil-news-nospam
• Re: Questions about getopt() (Linux)
  • From: Thomas E. Dickey
• Re: using socket fd to another pid (?)
  • From: Barry Margolin
• Re: Questions about getopt() (Linux)
  • From: Geoff Clare
• Re: linux - directory operations in c
  • From: Jens Thoms Toerring
• Re: Questions about getopt() (Linux)
  • From: Rainer Weikusat
• Re: linux - directory operations in c
  • From: MK
• linux - directory operations in c
  • From: MK
• Re: opendir
  • From: MK
• Re: Please help me in writing script
  • From: Jim Cochrane
• Re: interposing library calls - here is one I want to do
  • From: phil-news-nospam
• Re: interposing library calls - here is one I want to do
  • From: phil-news-nospam
• what are .Plo files
  • From: Sumit
• Re: Questions about getopt() (Linux)
  • From: Michael Kerrisk
• Re: interposing library calls - here is one I want to do
  • From: Paul Pluzhnikov
• Re: using socket fd to another pid (?)
  • From: David Schwartz
• Re: interposing library calls - here is one I want to do
  • From: David Schwartz
• Re: interposing library calls - here is one I want to do
  • From: Gordon Burditt
• Re: gdbm or berkeley DB? and C++ interface
  • From: Christof Meerwald
• Re: Questions about getopt() (Linux)
  • From: Kenny McCormack
• interposing library calls - here is another one
  • From: phil-news-nospam
• Re: Questions about getopt() (Linux)
  • From: Thomas E. Dickey
• Re: interposing library calls - here is one I want to do
  • From: phil-news-nospam
• Re: Questions about getopt() (Linux)
  • From: Thomas E. Dickey
• Re: interposing library calls - here is one I want to do
  • From: Bernie Ohls
• Re: using socket fd to another pid (?)
  • From: malc
• Re: Questions about getopt() (Linux)
  • From: Geoff Clare
• Re: who command
  • From: viza
• Re: libevent not found
  • From: Wolfgang Riedel
• Re: libevent not found
  • From: Jens Thoms Toerring
• Questions about getopt() (Linux)
  • From: Kenny McCormack
• Re: sending echo to all clients
  • From: arnuld
• who command
  • From: sinbad
• Re: libevent not found
  • From: asit
• Re: Remove msgget() queue from child?
  • From: rahul
• interposing library calls - here is one I want to do
  • From: phil-news-nospam
• Re: using socket fd to another pid (?)
  • From: Scott Lurndal
• Re: using socket fd to another pid (?)
  • From: malc
• using socket fd to another pid (?)
  • From: Beagle
• Re: Remove msgget() queue from child?
  • From: Jens Thoms Toerring
• Re: sending echo to all clients
  • From: phil-news-nospam
• Re: Error checking with execlp()
  • From: phil-news-nospam
• Re: Remove msgget() queue from child?
  • From: Hallvard B Furuseth
• Re: Remove msgget() queue from child?
  • From: phil-news-nospam
• Re: Remove msgget() queue from child?
  • From: Jens Thoms Toerring
• Re: server address and port
  • From: Mr_John
• Remove msgget() queue from child?
  • From: Hallvard B Furuseth
• Re: rsh cannot find executable
  • From: Jens Thoms Toerring
• Re: rsh cannot find executable
  • From: Scott Lurndal
• rsh cannot find executable
  • From: uwcssa@xxxxxxxxx
• Re: libevent not found
  • From: John Gordon
• libevent not found
  • From: asit
• Re: server address and port
  • From: Gordon Burditt
• Re: server address and port
  • From: Mr_John
• Addons on traceroute
  • From: lak
• Re: Audit Reports
  • From: Kingmaker
• Re: Wait_event_timeout kernel macro doubt
  • From: Marco
• Re: Wait_event_timeout kernel macro doubt
  • From: Rainer Weikusat
• Re: Error checking with execlp()
  • From: Rainer Weikusat
• Re: Question about struct in shared memory (C on linux)
  • From: Ian Collins
• Re: Wait_event_timeout kernel macro doubt
  • From: Marco
• Re: sending echo to all clients
  • From: arnuld
• Re: server address and port
  • From: Barry Margolin
• Re: Error checking with execlp()
  • From: Barry Margolin
• Re: Wait_event_timeout kernel macro doubt
  • From: David Schwartz
• server address and port
  • From: Mr_John
• Re: Solaris 5.10 cpu hike --- _flockget
  • From: Casper H . S . Dik
• Wait_event_timeout kernel macro doubt
  • From: Marco
• Re: iovecs don't print right
  • From: David Schwartz
• Re: dlopen dumps
  • From: Rainer Weikusat
• Re: Debugging an exec'ed process
  • From: Paul Pluzhnikov
• Re: iovecs don't print right
  • From: Jens Thoms Toerring
• Traceroute using IP option
  • From: lak
• Re: iovecs don't print right
  • From: nobody+cplusplus
• Re: iovecs don't print right
  • From: nobody+cplusplus
• Re: iovecs don't print right
  • From: nobody+cplusplus
• Re: iovecs don't print right
  • From: phil-news-nospam
• Re: Error checking with execlp()
  • From: phil-news-nospam
• Re: Error checking with execlp()
  • From: phil-news-nospam
• Re: Error checking with execlp()
  • From: phil-news-nospam
• Re: iovecs don't print right
  • From: Stephane CHAZELAS
• iovecs don't print right
  • From: nobody+cplusplus
• Re: dlopen dumps
  • From: Raxit@xxxxxxxxxxxx
• Re: dlopen dumps
  • From: Jens Thoms Toerring
• Re: Error checking with execlp()
  • From: Barry Margolin
• dlopen dumps
  • From: Raxit@xxxxxxxxxxxx
• Re: Error checking with execlp()
  • From: Rainer Weikusat
• Re: Question about struct in shared memory (C on linux)
  • From: David Schwartz
• Re: Error checking with execlp()
  • From: Barry Margolin
• Re: Error checking with execlp()
  • From: Giorgos Keramidas
• Re: Question about struct in shared memory (C on linux)
  • From: Phil
• Re: Question about struct in shared memory (C on linux)
  • From: Jens Thoms Toerring
• Re: Question about struct in shared memory (C on linux)
  • From: ppi
• Question about struct in shared memory (C on linux)
  • From: hugo.arregui@xxxxxxxxx
• Job Posting: TSM/Tivoli Storage Specialist
  • From: Sapphire
• Re: Error checking with execlp()
  • From: phil-news-nospam
• Re: How do you implement graphical interfaces for the following scenario.
  • From: Jens Thoms Toerring
• Re: Error checking with execlp()
  • From: Rainer Weikusat
• Re: Error checking with execlp()
  • From: phil-news-nospam
• Re: Please help me in writing script
  • From: Injam
• How do you implement graphical interfaces for the following scenario.
  • From: K-mart Cashier
• Re: Error checking with execlp()
  • From: Barry Margolin
• Re: Please help me in writing script
  • From: Injam
• Balenciaga Lune Moon Patent Leather Bag Purple - www.luxury-gift.org
  • From: yxs078
• Police Sunglasses SG_RPS0804017 - www.luxury-gift.org
  • From: yxs078
• Re: Error checking with execlp()
  • From: phil-news-nospam
• Re: Error checking with execlp()
  • From: phil-news-nospam
• Re: Please help me in writing script
  • From: John W. Krahn
• Re: what 64 mean in fopen64?
  • From: Medvedev
• behavior of /dev/stdout
  • From: lhyatt@xxxxxxxxxxxxx
• Re: sending echo to all clients
  • From: K-mart Cashier
• Please help me in writing script
  • From: Injam
• Re: who sets the default library path?
  • From: Jens Thoms Toerring
• Re: who sets the default library path?
  • From: Doug McIntyre
• Re: what 64 mean in fopen64?
  • From: viza
• who sets the default library path?
  • From: Lalatendu Das
• Re: what 64 mean in fopen64?
  • From: Jens Thoms Toerring
• Re: sending echo to all clients
  • From: Moi
• Re: what 64 mean in fopen64?
  • From: viza
• Re: sending echo to all clients
  • From: David Schwartz
• Re: The Minutiae of a TCP Client
  • From: Rainer Weikusat
• Re: Error checking with execlp()
  • From: Rainer Weikusat
• Re: The Minutiae of a TCP Client
  • From: Barry Margolin
• Re: Error checking with execlp()
  • From: Barry Margolin
• Re: what 64 mean in fopen64?
  • From: David Schwartz
• what 64 mean in fopen64?
  • From: Medvedev
• Re: Audit Reports
  • From: shakahshakah@xxxxxxxxx
• The Minutiae of a TCP Client
  • From: Minimiscience
• Re: sending echo to all clients
  • From: arnuld
• Re: Audit Reports
  • From: Scott Lurndal
• Re: sending echo to all clients
  • From: arnuld
• Re: Need Shell Script help
  • From: shakahshakah@xxxxxxxxx
• Re: Error checking with execlp()
  • From: Rainer Weikusat
• Re: mutex: busy waitting or sleep??
  • From: Eric Sosman
• Re: sending echo to all clients
  • From: David Schwartz
• Re: Need Shell Script help
  • From: John W. Krahn
• Re: sending echo to all clients
  • From: arnuld
• Re: Make file problem
  • From: Jens Thoms Toerring
• Audit Reports
  • From: Kingmaker
• mutex: busy waitting or sleep??
  • From: Xend
• Make file problem
  • From: KIRAN
• Re: Error checking with execlp()
  • From: Rainer Weikusat
• Re: Need Shell Script help
  • From: Robert Harris
• Re: sending echo to all clients
  • From: David Schwartz
• Need Shell Script help
  • From: injam4u
• Re: sending echo to all clients
  • From: arnuld
• Re: sending echo to all clients
  • From: arnuld
• Re: sending echo to all clients
  • From: David Schwartz
• Re: Increment counter upon each execution of shell script
  • From: Ben Bacarisse
• Re: gdbm or berkeley DB? and C++ interface
  • From: Steven Woody
• Re: Error checking with execlp()
  • From: Barry Margolin
• Re: Error checking with execlp()
  • From: Barry Margolin
• Re: Increment counter upon each execution of shell script
  • From: Jens Thoms Toerring

We are proud to have Web Hosting and Rack Housing from 9 Net Avenue Deutschland.
(17)