comp.unix.programmer

• Thread Index

---

• Re: select function result is inconsistent with description man page
  • From: David Schwartz
• Re: Signal Handlers - sort of mystified by this
  • From: Bjorn Reese
• Re: select function result is inconsistent with description man page
  • From: Valentin Nechayev
• select function result is inconsistent with description man page
  • From: hao
• select function result is inconsistent with description man page
  • From: hao
• sema_wait not return as expected
  • From: hao
• sema_wait not return as expected
  • From: hao
• Re: SOCK_DGRAM and TCP
  • From: Barry Margolin
• Re: Signal Handlers - sort of mystified by this
  • From: Valentin Nechayev
• Re: SOCK_DGRAM and TCP
  • From: Maxim Yegorushkin
• Re: File write time
  • From: Kurtis D. Rader
• Re: Signal Handlers - sort of mystified by this
  • From: Chad
• Re: Signal Handlers - sort of mystified by this
  • From: SM Ryan
• Re: AWK - regular expression
  • From: shakahshakah@xxxxxxxxx
• Re: Signal Handlers - sort of mystified by this
  • From: joe
• Re: Finding mac address on solaris 10
  • From: jamesonang@xxxxxxxxx
• Re: How can I do this
  • From: Chris F.A. Johnson
• Re: Signal Handlers - sort of mystified by this
  • From: loic-dev
• Re: Signal Handlers - sort of mystified by this
  • From: Barry Margolin
• Re: How can I do this
  • From: Barry Margolin
• AWK - regular expression
  • From: friend_05
• Re: Recording read hits on a file
  • From: scott . myron
• Re: Signal Handlers - sort of mystified by this
  • From: Markus Elfring
• Re: Signal Handlers - sort of mystified by this
  • From: joe
• Re: Signal Handlers - sort of mystified by this
  • From: Rich Teer
• Re: Recording read hits on a file
  • From: Rich Teer
• Re: Signal Handlers - sort of mystified by this
  • From: Casper H . S . Dik
• Re: Signal Handlers - sort of mystified by this
  • From: "Nils O. Selåsdal"
• Re: Signal Handlers - sort of mystified by this
  • From: SM Ryan
• Re: Recording read hits on a file
  • From: chotch
• Signal Handlers - sort of mystified by this
  • From: Chad
• How can I do this
  • From: integer
• Re: Finding mac address on solaris 10
  • From: Robert Harris
• Re: Finding mac address on solaris 10
  • From: Carlos
• Re: SOCK_DGRAM and TCP
  • From: Rahul
• Re: how to use rar with mknod ?
  • From: Pascal Bourguignon
• Re: Finding mac address on solaris 10
  • From: John Smith
• Re: Finding mac address on solaris 10
  • From: jamesonang@xxxxxxxxx
• Re: Recording read hits on a file
  • From: Mark Rafn
• Re: Recording read hits on a file
  • From: Rich Teer
• Re: Recording read hits on a file
  • From: Rich Teer
• Re: Recording read hits on a file
  • From: John Gordon
• Recording read hits on a file
  • From: chotch
• Finding mac address on solaris 10
  • From: John Smith
• Re: Logging error messages in a Daemon Program
  • From: Rich Teer
• Re: Casting between 64bit and 32bit
  • From: Valentin Nechayev
• Logging error messages in a Daemon Program
  • From: mshetty
• Re: how to use rar with mknod ?
  • From: Giorgos Keramidas
• Re: Remote synchronization
  • From: Maxim Yegorushkin
• Re: Remote synchronization
  • From: John Smith
• Re: Casting between 64bit and 32bit
  • From: Bjorn Reese
• Remote synchronization
  • From: Kelvin Moss
• Re: how to use rar with mknod ?
  • From: Victor Wagner
• Re: Casting between 64bit and 32bit
  • From: Casper H . S . Dik
• Re: Casting between 64bit and 32bit
  • From: Casper H . S . Dik
• Re: File write time
  • From: john_chen
• Re: how to use rar with mknod ?
  • From: Pascal Bourguignon
• Re: Casting between 64bit and 32bit
  • From: "Nils O. Selåsdal"
• Re: Casting between 64bit and 32bit
  • From: Valentin Nechayev
• Re: Casting between 64bit and 32bit
  • From: John Smith
• Re: Non-PIC libstdc++ under Linux x86_64
  • From: John Smith
• Re: Casting between 64bit and 32bit
  • From: Valentin Nechayev
• Re: About NETBIOS i
  • From: jamesonang@xxxxxxxxx
• Re: About NETBIOS i
  • From: jamesonang@xxxxxxxxx
• Re: how to use rar with mknod ?
  • From: Colossus
• Re: About NETBIOS i
  • From: makuchaku
• About NETBIOS i
  • From: jamesonang@xxxxxxxxx
• AC_SYS_LARGEFILE in configure.in but...
  • From: Colossus
• C++ library for ptrace
  • From: makuchaku
• Re: File write time
  • From: Kurtis D. Rader
• Re: File write time
  • From: Pascal Bourguignon
• File write time
  • From: john_chen
• Re: Non-PIC libstdc++ under Linux x86_64
  • From: Paul Pluzhnikov
• Re: SOCK_DGRAM and TCP
  • From: Maxim Yegorushkin
• SOCK_DGRAM and TCP
  • From: Alex Vinokur
• SOCK_DGRAM and TCP
  • From: Alex Vinokur
• Re: __dirstream???
  • From: Alex Fraser
• __dirstream???
  • From: Final
• Re: problem while running a STL CPP application Compiled using gcc in Solaris environment.
  • From: Fletcher Glenn
• Re: problem while running a STL CPP application Compiled using gcc in Solaris environment.
  • From: Maxim Yegorushkin
• Re: using linux commands in C
  • From: goldfita
• Re: Message Catalog File
  • From: tmp123
• Message Catalog File
  • From: param
• Re: Casting between 64bit and 32bit
  • From: Bjorn Reese
• Re: some confused warning
  • From: Final
• Non-PIC libstdc++ under Linux x86_64
  • From: John Smith
• Re: Casting between 64bit and 32bit
  • From: John Smith
• Re: some confused warning
  • From: Lew Pitcher
• problem while running a STL CPP application Compiled using gcc in Solaris environment.
  • From: Vinu
• Re: some confused warning
  • From: Paul Pluzhnikov
• some confused warning
  • From: Final
• Re: how to use rar with mknod ?
  • From: ujangmz
• Re: Casting between 64bit and 32bit
  • From: Valentin Nechayev
• Re: IPV6 Fragmentation.
  • From: Valentin Nechayev
• Re: select(), sending and receiving data
  • From: Markus Pitha
• Re: Problem using wget
  • From: Bjorn Reese
• Re: help needed: remote application
  • From: Bjorn Reese
• Re: select(), sending and receiving data
  • From: Maxim Yegorushkin
• Re: using linux commands in C
  • From: Francois Goudal
• Re: Problem using wget
  • From: "Nils O. Selåsdal"
• using linux commands in C
  • From: Parthaneela
• Problem using wget
  • From: Yogi
• Re: how to use rar with mknod ?
  • From: Pascal Bourguignon
• how to use rar with mknod ?
  • From: ujangmz
• Re: select(), sending and receiving data
  • From: Alex Fraser
• Re: select(), sending and receiving data
  • From: David Schwartz
• Re: select(), sending and receiving data
  • From: David Schwartz
• Re: Watch Window
  • From: Barry Margolin
• Re: select(), sending and receiving data
  • From: Alex Fraser
• Re: select(), sending and receiving data
  • From: Pascal Bourguignon
• Re: select(), sending and receiving data
  • From: Pascal Bourguignon
• Re: select(), sending and receiving data
  • From: Pascal Bourguignon
• Re: help needed: remote application
  • From: giannizzz
• Re: Diabolical code
  • From: Kevin D . Quitt
• Re: select(), sending and receiving data
  • From: Markus Pitha
• Re: select(), sending and receiving data
  • From: Markus Pitha
• Re: select(), sending and receiving data
  • From: Markus Pitha
• IPV6 Fragmentation.
  • From: Prathap
• Re: select(), sending and receiving data
  • From: Alex Fraser
• Re: select(), sending and receiving data
  • From: "Nils O. Selåsdal"
• Re: about segment fault
  • From: Maxim Yegorushkin
• Re: Casting between 64bit and 32bit
  • From: Maxim Yegorushkin
• Re: Filesystem MTA queue
  • From: Alex Fraser
• Re: select(), sending and receiving data
  • From: Markus Pitha
• Re: Waiting for a child to die
  • From: Rahul
• Filesystem MTA queue
  • From: dgiagio
• Watch Window
  • From: sounak
• select(), sending and receiving data
  • From: Markus Pitha
• Re: select(), sending and receiving data
  • From: Pascal Bourguignon
• Re: Casting between 64bit and 32bit
  • From: Casper H . S . Dik
• Re: Is it possible to write Unix for Unix ???
  • From: Pascal Bourguignon
• Re: about segment fault
  • From: apple.davinci
• Re: Pic vs. non Pic library code?
  • From: Paul Pluzhnikov
• Re: about segment fault
  • From: Paul Pluzhnikov
• Re: about segment fault
  • From: Paul Pluzhnikov
• Re: about segment fault
  • From: apple.davinci
• Re: about segment fault
  • From: apple.davinci
• Re: about segment fault
  • From: apple.davinci
• Re: Casting between 64bit and 32bit
  • From: Maxim Yegorushkin
• Re: Pic vs. non Pic library code?
  • From: Maxim Yegorushkin
• Re: about segment fault
  • From: Maxim Yegorushkin
• Re: Pic vs. non Pic library code?
  • From: Paul Pluzhnikov
• Re: Help with "Concurrent Network Server" Design
  • From: Markus Elfring
• Re: about segment fault
  • From: Paul Pluzhnikov
• Re: a flex question ? ?
  • From: Robert Harris
• Re: Pic vs. non Pic library code?
  • From: John Smith
• Re: a flex question ? ?
  • From: Pascal Bourguignon
• Re: about segment fault
  • From: Gordon Burditt
• a flex question ? ?
  • From: cmk128
• Re: about segment fault
  • From: Paul Pluzhnikov
• Help with "Concurrent Network Server" Design
  • From: animesh
• Re: about segment fault
  • From: apple.davinci
• about segment fault
  • From: apple.davinci
• Re: Pic vs. non Pic library code?
  • From: Paul Pluzhnikov
• Re: Check signal handling
  • From: Markus Elfring
• Re: Pic vs. non Pic library code?
  • From: Henry Townsend
• Re: Casting between 64bit and 32bit
  • From: Rich Teer
• Re: extern int VALUE vs int VALUE
  • From: Daniel C. Bastos
• Re: Casting between 64bit and 32bit
  • From: joe
• Pic vs. non Pic library code?
  • From: John Smith
• Casting between 64bit and 32bit
  • From: John Smith
• Re: mutual exclusion for data structures in shared memory
  • From: Chinlu
• Re: Waiting for a child to die
  • From: Paul Pluzhnikov
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: Daniel C. Bastos
• Re: mutual exclusion for data structures in shared memory
  • From: Markus Elfring
• Re: How do you close a port immediately?
  • From: Daniel C. Bastos
• Re: fundamental data structures in shared memory
  • From: Markus Elfring
• Re: stat function limit for files over 2GB ?
  • From: Jordan Abel
• Re: stat function limit for files over 2GB ?
  • From: Valentin Nechayev
• Re: stat function limit for files over 2GB ?
  • From: Robert Harris
• Re: stat function limit for files over 2GB ?
  • From: Valentin Nechayev
• Re: stat function limit for files over 2GB ?
  • From: Ralf Fassel
• Re: stat function limit for files over 2GB ?
  • From: Robert Harris
• Re: stat function limit for files over 2GB ?
  • From: Colossus
• Re: stat function limit for files over 2GB ?
  • From: Colossus
• Re: stat function limit for files over 2GB ?
  • From: Igmar Palsenberg
• Re: stat function limit for files over 2GB ?
  • From: Colossus
• Re: stat function limit for files over 2GB ?
  • From: Jan Vidar Krey
• Re: stat function limit for files over 2GB ?
  • From: Igmar Palsenberg
• stat function limit for files over 2GB ?
  • From: Colossus
• Re: extern int VALUE vs int VALUE
  • From: Chad
• Re: extern int VALUE vs int VALUE
  • From: Erik Max Francis
• Re: extern int VALUE vs int VALUE
  • From: Chad
• Re: malloc design issues
  • From: Chinlu
• Re: extern int VALUE vs int VALUE
  • From: Erik Max Francis
• Re: extern int VALUE vs int VALUE
  • From: Chad
• Re: Diabolical code
  • From: Gordon Burditt
• Re: malloc design issues
  • From: Chinlu
• Re: malloc design issues
  • From: Chinlu
• Re: malloc design issues
  • From: Markus Elfring
• Re: Diabolical code
  • From: Chuck Dillon
• Re: malloc design issues
  • From: Barry Margolin
• Re: malloc design issues
  • From: Chinlu
• Re: malloc design issues
  • From: Markus Elfring
• Re: Diabolical code
  • From: David Schwartz
• Re: Diabolical code
  • From: Bit Twister
• Re: Diabolical code
  • From: William.Deans@xxxxxxxxx
• Re: another named pipes issue
  • From: Gordon Burditt
• Re: another named pipes issue
  • From: William.Deans@xxxxxxxxx
• Re: Diabolical code
  • From: Giorgos Keramidas
• Re: extern int VALUE vs int VALUE
  • From: Hubble
• Re: shared structures reloaded
  • From: Chinlu
• Re: extern int VALUE vs int VALUE
  • From: Chad
• Re: How to know PID from perl program
  • From: Victor Wagner
• another named pipes issue
  • From: heepa9@xxxxxxxxx
• Re: shared structures reloaded
  • From: Markus Elfring
• Re: extern int VALUE vs int VALUE
  • From: ilko . k . v
• How to know PID from perl program
  • From: saurabhlamgora
• Re: extern int VALUE vs int VALUE
  • From: Hubble
• Re: Give an implementation of Semaphore for a multiprocessor system using BUSY waiting that can be accessed from the threads of the same program.
  • From: Maxim Yegorushkin
• Re: extern int VALUE vs int VALUE
  • From: Maxim Yegorushkin
• extern int VALUE vs int VALUE
  • From: Chad
• Re: Diabolical code
  • From: Måns Rullgård
• Re: dynamic cast for streamed data
  • From: Andrei Voropaev
• Give an implementation of Semaphore for a multiprocessor system using BUSY waiting that can be accessed from the threads of the same program.
  • From: pratimaraj
• Re: what is the difference between static and dynamic libs
  • From: Ralf Fassel
• Re: what is the difference between static and dynamic libs
  • From: Thomas Maier-Komor
• Re: what is the difference between static and dynamic libs
  • From: Roger Leigh
• Re: what is the difference between static and dynamic libs
  • From: Thobias Vakayil
• what is the difference between static and dynamic libs
  • From: puzzlecracker
• Re: shared structures reloaded
  • From: Chinlu
• Re: shared structures reloaded
  • From: Markus Elfring
• Re: Accessing RS-232 Line Status Register using ioctl()?
  • From: Gordon Burditt
• Accessing RS-232 Line Status Register using ioctl()?
  • From: JH Trauntvein
• Re: sendto blocks for unix datagram socket
  • From: David Schwartz
• Re: Diabolical code
  • From: Giorgos Keramidas
• Re: Source for "script" program
  • From: Keith Thompson
• shared structures reloaded
  • From: Chinlu
• Re: data structures on shared memory?
  • From: Markus Elfring
• Diabolical code
  • From: Russell Shaw
• Re: data structures on shared memory?
  • From: RickE
• Re: sendto blocks for unix datagram socket
  • From: "Nils O. Selåsdal"
• Re: sendto blocks for unix datagram socket
  • From: Maxim Yegorushkin
• Re: sendto blocks for unix datagram socket
  • From: girishdkale@xxxxxxxxx
• Re: question on fork function
  • From: apple.davinci
• Re: question on fork function
  • From: "Nils O. Selåsdal"
• question on fork function
  • From: apple.davinci
• Re: ncurses wgetch and flicker.
  • From: Hubble
• Re: sendto blocks for unix datagram socket
  • From: "Nils O. Selåsdal"
• Re: sendto blocks for unix datagram socket
  • From: girishdkale@xxxxxxxxx
• Re: insert # on a matched string
  • From: John W. Krahn
• Re: insert # on a matched string
  • From: Jim Cochrane
• Re: Source for "script" program
  • From: Jordan Abel
• Re: data structures on shared memory?
  • From: Chinlu
• Re: Source for "script" program
  • From: Lorin Hochstein
• ncurses wgetch and flicker.
  • From: sir . eggplantalot
• Re: sendto blocks for unix datagram socket
  • From: David Schwartz
• Re: sendto blocks for unix datagram socket
  • From: Barry Margolin
• Re: TCP/UNIX Question
  • From: Barry Margolin
• Re: TCP/UNIX Question
  • From: Barry Margolin
• Re: sendto blocks for unix datagram socket
  • From: David Schwartz
• Re: TCP/UNIX Question
  • From: David Schwartz
• sendto blocks for unix datagram socket
  • From: girishdkale@xxxxxxxxx
• Re: data structures on shared memory?
  • From: Markus Elfring
• Re: insert # on a matched string
  • From: Ralf Fassel
• Re: insert # on a matched string
  • From: noogie . brown
• Re: insert # on a matched string
  • From: Pascal Bourguignon
• Re: TCP/UNIX Question
  • From: sony . antony
• Re: TCP/UNIX Question
  • From: Eric Sosman
• insert # on a matched string
  • From: blah
• Re: TCP/UNIX Question
  • From: Maxim Yegorushkin
• Re: where is my error
  • From: jamesonang@xxxxxxxxx
• Re: Source for "script" program
  • From: Jordan Abel
• Re: Source for "script" program
  • From: Keith Thompson
• Re: Source for "script" program
  • From: Bjørn Augestad
• Source for "script" program
  • From: Lorin Hochstein
• Re: TCP/UNIX Question
  • From: David Schwartz
• Re: How do you close a port immediately?
  • From: drhowarddrfine
• connection timed out while connecting to localhost
  • From: pratik . ganguly
• connection timed out while connecting on localhost
  • From: prats
• TCP/UNIX Question
  • From: sony . antony
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: Jim Cochrane
• Re: where is my error
  • From: David Schwartz
• where is my error
  • From: jamesonang@xxxxxxxxx
• Re: data structures on shared memory?
  • From: Chinlu
• Re: Reading from serial to an array?
  • From: Pascal Bourguignon
• Re: Reading from serial to an array?
  • From: John Brockmeyer
• Reading from serial to an array?
  • From: Shawn
• Re: data structures on shared memory?
  • From: Thomas Maier-Komor
• Re: weird serial blocking behavior
  • From: Jim Alexander
• Re: data structures on shared memory?
  • From: Chinlu
• Re: weird serial blocking behavior
  • From: Jim Alexander
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: David Schwartz
• Re: data structures on shared memory?
  • From: Gordon Burditt
• Re: data structures on shared memory?
  • From: Chinlu
• Re: data structures on shared memory?
  • From: Gordon Burditt
• Re: data structures on shared memory?
  • From: Chinlu
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: "Nils O. Selåsdal"
• Re: data structures on shared memory?
  • From: Eric Sosman
• Re: How do you close a port immediately?
  • From: Steven
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: Steven
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: Dale Hagglund
• data structures on shared memory?
  • From: Chinlu
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: Dale Hagglund
• Re: How do you close a port immediately?
  • From: Lew Pitcher
• Re: How do you close a port immediately?
  • From: Steven
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: Steven
• Re: How do you close a port immediately?
  • From: Lew Pitcher
• Re: How do you close a port immediately?
  • From: Steffen
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: "Nils O. Selåsdal"
• How do you close a port immediately?
  • From: Steven
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: Steven
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: Jelte
• Re: what happen to heap on programme exit
  • From: Pascal Bourguignon
• Re: what happen to heap on programme exit
  • From: David Schwartz
• Re: what happen to heap on programme exit
  • From: apple.davinci
• Re: what happen to heap on programme exit
  • From: apple.davinci
• Re: no previous prototype for `init_module'
  • From: Maxim Yegorushkin
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: David Schwartz
• Re: what happen to heap on programme exit
  • From: David Schwartz
• Re: what happen to heap on programme exit
  • From: "Nils O. Selåsdal"
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: "Nils O. Selåsdal"
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: Michael Kerrisk
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: jelte . werkhoven
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: Steven
• Re: where's the faq kenneth?
  • From: Michael Kerrisk
• Re: recv() - How do you know the length of buffer that you are going to receive?
  • From: Barry Margolin
• Re: weird serial blocking behavior
  • From: Floyd Davidson
• recv() - How do you know the length of buffer that you are going to receive?
  • From: Steven
• Re: what happen to heap on programme exit
  • From: Barry Margolin
• Re: what happen to heap on programme exit
  • From: Barry Margolin
• Re: what happen to heap on programme exit
  • From: apple.davinci
• Re: what happen to heap on programme exit
  • From: David Schwartz
• Re: what happen to heap on programme exit
  • From: apple.davinci
• Re: what happen to heap on programme exit
  • From: Pascal Bourguignon
• Re: what happen to heap on programme exit
  • From: apple.davinci
• Re: what happen to heap on programme exit
  • From: Pascal Bourguignon
• Re: what happen to heap on programme exit
  • From: apple.davinci
• Re: what happen to heap on programme exit
  • From: Måns Rullgård
• weird serial blocking behavior
  • From: Jim Alexander
• Re: what happen to heap on programme exit
  • From: apple.davinci
• what happen to heap on programme exit
  • From: apple.davinci
• Re: no previous prototype for `init_module'
  • From: Final
• Re: I thought I understood sizeof().
  • From: Paul Pluzhnikov
• Re: Question about creating man pages
  • From: Bjørn Augestad
• Re: I thought I understood sizeof().
  • From: moi
• Re: Where do message queues, named pipes reside?
  • From: "Nils O. Selåsdal"
• Re: Question about creating man pages
  • From: Rich Teer
• Re: I thought I understood sizeof().
  • From: Chad
• Re: I thought I understood sizeof().
  • From: Chad
• Re: Where do message queues, named pipes reside?
  • From: SM Ryan
• Re: Why does strtok() jam on '\'
  • From: Jon Dowland
• Re: Where do message queues, named pipes reside?
  • From: Barry Margolin
• Where do message queues, named pipes reside?
  • From: qazmlp1209
• Re: help needed: remote application
  • From: Pascal Bourguignon
• Re: TCP connection hang problem (resumes upon new TCP request)
  • From: Maxim Yegorushkin
• Re: help needed: remote application
  • From: giannizzz
• Re: Question about creating man pages
  • From: Bjørn Augestad
• Re: Question about creating man pages
  • From: Giorgos Keramidas
• Question about creating man pages
  • From: Bjørn Augestad
• Re: kill all the child processes
  • From: SM Ryan
• ftpd supporting stacking of PAM modules
  • From: pappu72_99
• code with libsysfs functions
  • From: googler
• Re: I thought I understood sizeof().
  • From: Paul Pluzhnikov
• Re: help needed: remote application
  • From: Pascal Bourguignon
• Re: I thought I understood sizeof().
  • From: David Schwartz
• Re: I thought I understood sizeof().
  • From: Keith Thompson
• Re: I thought I understood sizeof().
  • From: Chad
• kill all the child processes
  • From: ajju
• TCP connection hang problem (resumes upon new TCP request)
  • From: changxun
• where's the faq kenneth?
  • From: none
• Re: I thought I understood sizeof().
  • From: David Schwartz
• Re: Having problems linking files ...
  • From: Paul Pluzhnikov
• Re: I thought I understood sizeof().
  • From: Paul Pluzhnikov
• Re: I thought I understood sizeof().
  • From: Paul Pluzhnikov
• Re: I thought I understood sizeof().
  • From: Chad
• Re: I thought I understood sizeof().
  • From: Paul Pluzhnikov
• Re: I thought I understood sizeof().
  • From: Måns Rullgård
• Re: I thought I understood sizeof().
  • From: Bjørn Augestad
• Re: I thought I understood sizeof().
  • From: David Schwartz
• Re: I thought I understood sizeof().
  • From: Måns Rullgård
• Re: how to monitor network status using C/C++ library functions
  • From: Robert Harris
• Re: Having problems linking files ...
  • From: Giorgos Keramidas
• I thought I understood sizeof().
  • From: Chad
• Re: Having problems linking files ...
  • From: Erik Max Francis
• how to monitor network status using C/C++ library functions
  • From: Sumir
• Re: help needed: remote application
  • From: giannizzz
• Re: Having problems linking files ...
  • From: Paul Pluzhnikov
• Re: Having problems linking files ...
  • From: Paul Pluzhnikov
• Re: help needed: remote application
  • From: Bjorn Reese
• help needed: remote application
  • From: giannizzz
• Re: Having problems linking files ...
  • From: Paul Pluzhnikov
• Re: Having problems linking files ...
  • From: ebrahimbandookwala
• Re: Having problems linking files ...
  • From: Erik Max Francis
• Re: Having problems linking files ...
  • From: ebrahimbandookwala
• Re: Having problems linking files ...
  • From: ebrahimbandookwala
• [no subject]
  • From: Unknown
• Re: definition of terminal, et cetera
  • From: Daniel C. Bastos
• Re: Why does strtok() jam on '\'
  • From: Jordan Abel
• Re: Why does strtok() jam on '\'
  • From: Chad
• Freelance Projects available
  • From: Stefan
• Re: Why does strtok() jam on '\'
  • From: Casper H . S . Dik
• Re: Why does strtok() jam on '\'
  • From: Richard Harnden
• Why does strtok() jam on '\'
  • From: Chad
• Re: please what's $$ in yacc
  • From: Thomas Dickey
• Re: function to get current date
  • From: Martin Blume
• Re: no previous prototype for `init_module'
  • From: Maxim Yegorushkin
• Re: Process is getting killed after 5 days
  • From: Maxim Yegorushkin
• function to get current date
  • From: Roman Mashak
• Re: Process is getting killed after 5 days
  • From: Andrei Voropaev
• Re: function to get current date
  • From: Chris McDonald
• Process is getting killed after 5 days
  • From: ramsailu@xxxxxxxxx
• Re: Pseudo-terminal and OpenSSH
  • From: Anders
• Re: Pseudo-terminal and OpenSSH
  • From: Victor Wagner
• no previous prototype for `init_module'
  • From: Final
• A single instance app.
  • From: Chinlu
• Re: Pseudo-terminal and OpenSSH
  • From: Anders
• Re: Pseudo-terminal and OpenSSH
  • From: Anders
• Re: Pseudo-terminal and OpenSSH
  • From: Victor Wagner
• Re: Pseudo-terminal and OpenSSH
  • From: David Schwartz
• Pseudo-terminal and OpenSSH
  • From: Anders
• Re: Needing Inversed database lex/yacc/c code please.
  • From: Pascal Bourguignon
• Needing Inversed database lex/yacc/c code please.
  • From: freeposte
• Re: please what's $$ in yacc
  • From: freeposte
• Re: Newbie question - gcc and variable declaration
  • From: Roger Leigh
• Re: please what's $$ in yacc
  • From: Pascal Bourguignon
• please what's $$ in yacc
  • From: octavio
• Re: Having problems linking files ...
  • From: Paul Pluzhnikov
• Re: error loading shared libraries
  • From: none
• Re: Having problems linking files ...
  • From: ebrahimbandookwala
• Re: Having problems linking files ...
  • From: Paul Pluzhnikov
• Re: error loading shared libraries
  • From: Paul Pluzhnikov
• Re: libsndfile problem
  • From: xucaen
• Re: error loading shared libraries
  • From: none
• Having problems linking files ...
  • From: ebrahimbandookwala
• Re: Newbie question - gcc and variable declaration
  • From: Jordan Abel
• Re: Newbie question - gcc and variable declaration
  • From: Roger Leigh
• Re: Newbie question - gcc and variable declaration
  • From: Måns Rullgård
• Re: Newbie question - gcc and variable declaration
  • From: Pascal Bourguignon
• Re: Newbie question - gcc and variable declaration
  • From: Giorgos Keramidas
• Re: Newbie question - gcc and variable declaration
  • From: Erik Max Francis
• Re: Newbie question - gcc and variable declaration
  • From: Aaron Couts
• Re: Newbie question - gcc and variable declaration
  • From: Aaron Couts
• Re: Newbie question - gcc and variable declaration
  • From: Måns Rullgård
• Re: Newbie question - gcc and variable declaration
  • From: Robert Harris
• Re: Newbie question - gcc and variable declaration
  • From: Roger Leigh
• Newbie question - gcc and variable declaration
  • From: Aaron Couts
• Re: Detect interface failure.
  • From: Prathap
• Re: Why is this value off by one?
  • From: Pascal Bourguignon
• Re: Why is this value off by one?
  • From: Rainer Temme
• Re: segmentation fault
  • From: Fletcher Glenn
• Re: definition of terminal, et cetera
  • From: Thomas Dickey
• Re: Why is this value off by one?
  • From: loic-dev
• Re: Why is this value off by one?
  • From: David Schwartz
• Re: Detect interface failure.
  • From: loic-dev
• Re: Why is this value off by one?
  • From: Alex Fraser
• Re: Why is this value off by one?
  • From: Chad
• Re: Why is this value off by one?
  • From: loic-dev
• Why is this value off by one?
  • From: Chad
• Re: Detect interface failure.
  • From: Prathap
• Re: memory leaks using MySQL 5.0 API
  • From: Markus Elfring
• Re: Detect interface failure.
  • From: loic-dev
• Re: segmentation fault
  • From: "Nils O. Selåsdal"
• Detect interface failure.
  • From: Prathap
• segmentation fault
  • From: Final
• Re: Random Number Generator
  • From: Andrei Voropaev
• Re: Flushing Sockets in C?
  • From: Andrei Voropaev
• Re: Random Number Generator
  • From: Jordan Abel
• Re: Random Number Generator
  • From: Jordan Abel
• Random Number Generator
  • From: morty3e@xxxxxxxxx
• Re: Question on raw socket
  • From: "Nils O. Selåsdal"
• Question on raw socket
  • From: Luke Z. Yang
• Re: tool to view programs trace
  • From: raph
• Re: error loading shared libraries
  • From: Paul Pluzhnikov
• Re: Flushing Sockets in C?
  • From: Barry Margolin
• Re: error loading shared libraries
  • From: David Schwartz
• Re: Flushing Sockets in C?
  • From: David Schwartz
• Re: how to detect Linux
  • From: Roger Leigh
• Re: error loading shared libraries
  • From: none
• Re: Flushing Sockets in C?
  • From: Sparticus
• Re: how to detect Linux
  • From: Jordan Abel
• Re: definition of terminal, et cetera
  • From: Daniel C. Bastos
• Re: Flushing Sockets in C?
  • From: David Schwartz
• Re: Programming a "termin
  • From: eng
• Re: Flushing Sockets in C?
  • From: Sparticus
• Re: Flushing Sockets in C?
  • From: David Schwartz
• Re: Flushing Sockets in C?
  • From: David Schwartz
• Re: Flushing Sockets in C?
  • From: Alex Fraser
• Linux parport write() sends 0 bytes, errno = 0
  • From: BB
• Re: Flushing Sockets in C?
  • From: Sparticus
• Re: Flushing Sockets in C?
  • From: Alex Fraser
• Re: how to detect Linux
  • From: Bjorn Reese
• Re: preprocessor optimisation?
  • From: Bjorn Reese
• Re: how to detect Linux
  • From: Mark Rafn
• Re: named pipes programming problem
  • From: abottchow
• Re: how to detect Linux
  • From: Trofinenco, Cristian
• Re: Flushing Sockets in C?
  • From: Sparticus
• Re: how to detect Linux
  • From: Roger Leigh
• Re: how to detect Linux
  • From: heepa9@xxxxxxxxx
• Re: how to detect Linux
  • From: heepa9@xxxxxxxxx
• Re: how to detect Linux
  • From: Henry Townsend
• Re: how to detect Linux
  • From: #2pencil
• Re: named pipes programming problem
  • From: Alex Fraser
• Re: named pipes block ...when?
  • From: heepa9@xxxxxxxxx
• Re: named pipes block ...when?
  • From: heepa9@xxxxxxxxx
• Re: Flushing Sockets in C?
  • From: Casper H . S . Dik
• how to detect Linux
  • From: heepa9@xxxxxxxxx
• Re: Flushing Sockets in C?
  • From: Maxim Yegorushkin
• Re: Flushing Sockets in C?
  • From: Casper H . S . Dik
• Re: Flushing Sockets in C?
  • From: Maxim Yegorushkin
• Programming a "termin
  • From: Arjun
• Re: named pipes programming problem
  • From: Hubble
• Re: Correct strod return error checking
  • From: Geoff Clare
• Re: return value makes me sad.
  • From: Hubble
• Re: Flushing Sockets in C?
  • From: Konstantin Sorokin
• Re: Flushing Sockets in C?
  • From: Maxim Yegorushkin
• Re: Flushing Sockets in C?
  • From: Alex Fraser
• named pipes programming problem
  • From: abottchow
• Re: Flushing Sockets in C?
  • From: Maxim Yegorushkin
• Re: memory leaks using MySQL 5.0 API
  • From: Roman Mashak
• Re: Flushing Sockets in C?
  • From: David Schwartz
• Re: named pipes block ...when?
  • From: Michael Kerrisk
• preprocessor optimisation?
  • From: ul
• Re: Flushing Sockets in C?
  • From: Gustavo Rios
• memory leaks using MySQL 5.0 API
  • From: Roman Mashak
• Re: what is the difference in permission if we change sticky bit location?
  • From: Bill Marcum
• Re: named pipes block ...when?
  • From: Gordon Burditt
• Re: memory leaks using MySQL 5.0 API
  • From: Gordon Burditt
• Re: named pipes block ...when?
  • From: Barry Margolin
• Flushing Sockets in C?
  • From: Sparticus
• Re: playing with valgrind
  • From: Frank Cusack
• named pipes block ...when?
  • From: heepa9@xxxxxxxxx
• Re: process group management
  • From: eng
• Re: N Rules Never Reduced Error in YACC
  • From: Thomas Maier-Komor
• Re: process group management
  • From: Michael Kerrisk
• Re: process group management
  • From: eng
• N Rules Never Reduced Error in YACC
  • From: SSG
• Re: process group management
  • From: Michael Kerrisk
• Re: Getting output of grep into a variable in C program?
  • From: Maxim Yegorushkin
• Re: what is the best way to find a key.
  • From: Maxim Yegorushkin
• Re: intersting problem
  • From: Maxim Yegorushkin
• Re: Getting output of grep into a variable in C program?
  • From: Hubble
• Re: process group management
  • From: eng
• Re: Getting output of grep into a variable in C program?
  • From: Hubble
• Re: process group management
  • From: Michael Kerrisk
• Re: Question: what function or library to find cpu info?
  • From: Thobias Vakayil
• Re: error loading shared libraries
  • From: Thobias Vakayil
• Re: Escaping backslash [programming question]
  • From: SM Ryan
• Re: C program for getting IP address of standlone box - with no sockets
  • From: SM Ryan
• Re: intersting problem
  • From: Pascal Bourguignon
• Re: Linux programme - different results each run
  • From: David Schwartz
• Re: Question: making a blank directory tree from existing tree (OS X 10.4.3)
  • From: Barry Margolin
• Re: intersting problem
  • From: Måns Rullgård
• Re: what is the best way to find a key.
  • From: Måns Rullgård
• intersting problem
  • From: puzzlecracker
• Re: what is the best way to find a key.
  • From: puzzlecracker
• Re: what is the best way to find a key.
  • From: Roger Leigh
• Re: what is the best way to find a key.
  • From: puzzlecracker
• what is the best way to find a key.
  • From: puzzlecracker
• Re: Problem with linking
  • From: John Smith
• Re: Problem with linking
  • From: Paul Pluzhnikov
• Problem with linking
  • From: John Smith
• Re: Linux programme - different results each run
  • From: Paul Pluzhnikov
• Re: Escaping backslash [programming question]
  • From: slebetman
• Re: Correct strod return error checking
  • From: Chsrs
• Re: Question regarding IPs
  • From: Kenny McCormack
• Re: Question: what function or library to find cpu info?
  • From: Valentin Nechayev
• Re: Correct strod return error checking
  • From: Robert Harris
• Re: Correct strod return error checking
  • From: Robert Harris
• Re: error loading shared libraries
  • From: none
• process group management
  • From: eng
• Re: Question: what function or library to find cpu info?
  • From: ipcress
• Escaping backslash [programming question]
  • From: agarwalpiyush
• Re: Linux programme - different results each run
  • From: Eric Enright
• RPC over streams
  • From: Gustavo Rios
• Linux programme - different results each run
  • From: ulyses
• Re: Getting output of grep into a variable in C program?
  • From: slebetman
• Re: Correct strod return error checking
  • From: Chsrs
• Re: C program for getting IP address of standlone box - with no sockets
  • From: Måns Rullgård
• Getting output of grep into a variable in C program?
  • From: agarwalpiyush
• C program for getting IP address of standlone box - with no sockets
  • From: agarwalpiyush
• Re: Correct strod return error checking
  • From: moi
• Re: Correct strod return error checking
  • From: Chsrs
• Re: Correct strod return error checking
  • From: Robert Harris
• Re: How to provide a file as standard input to the yacc please ?
  • From: Pascal Bourguignon
• Correct strod return error checking
  • From: Chsrs
• Re: complex dictionary search engine with parallel processing???
  • From: moi
• How to provide a file as standard input to the yacc please ?
  • From: freeposte
• Re: Question regarding IPs
  • From: Jordan Abel
• Re: what is the difference in permission if we change sticky bit location?
  • From: Jordan Abel
• Re: complex dictionary search engine with parallel processing???
  • From: Jordan Abel
• Question: what function or library to find cpu info?
  • From: ipcress
• Question regarding IPs
  • From: Chad
• Re: what is the difference in permission if we change sticky bit location?
  • From: Roger Leigh
• Re: error loading shared libraries
  • From: "Nils O. Selåsdal"
• what is the difference in permission if we change sticky bit location?
  • From: puzzlecracker
• Re: Question: making a blank directory tree from existing tree (OS X 10.4.3)
  • From: Henry Townsend
• Re: Question: making a blank directory tree from existing tree (OS X 10.4.3)
  • From: Barry Margolin
• Re: Question: making a blank directory tree from existing tree (OS X 10.4.3)
  • From: Måns Rullgård
• Question: making a blank directory tree from existing tree (OS X 10.4.3)
  • From: Elmer Fudd
• Re: Big/little endian conversion
  • From: Bjorn Reese
• Re: complex dictionary search engine with parallel processing???
  • From: moi
• Re: playing with valgrind
  • From: Roman Mashak
• Re: Is there any way / editor to see code after preprocessing
  • From: Brian Raiter
• Re: playing with valgrind
  • From: Frank Cusack
• Re: what is wrong with the function" nanosleep"
  • From: yezi
• error loading shared libraries
  • From: none
• Re: what is wrong with the function" nanosleep"
  • From: Chris Friesen
• Re: Big/little endian conversion
  • From: David Schwartz
• Re: what is wrong with the function" nanosleep"
  • From: Wayne C. Morris
• Re: Number of elements in an array.
  • From: Jordan Abel
• Re: what is wrong with the function" nanosleep"
  • From: Fletcher Glenn
• what is wrong with the function" nanosleep"
  • From: yezi
• Re: printing
  • From: Simon Elliott
• Re: Big/little endian conversion
  • From: Bjorn Reese
• Re: complex dictionary search engine with parallel processing???
  • From: Richard Harnden
• Re: Big/little endian conversion
  • From: Bjorn Reese
• Re: Big/little endian conversion
  • From: Bjorn Reese
• Re: Post-modernism, Academia, and the Tech Geeking fuckheads
  • From: Luotao Fu
• Re: Is there any way / editor to see code after preprocessing
  • From: Markus Elfring
• Re: Number of elements in an array.
  • From: Roger Leigh
• Number of elements in an array.
  • From: jay
• Re: printing
  • From: Roger Leigh
• Re: recording sound
  • From: Simon Elliott
• playing with valgrind
  • From: Roman Mashak
• Re: printing
  • From: Simon Elliott
• Re: playing with valgrind
  • From: "Nils O. Selåsdal"
• Re: playing with valgrind
  • From: Bjørn Augestad
• Re: Application cannot find shared object
  • From: Paul Pluzhnikov
• Re: Application cannot find shared object
  • From: googler
• Re: Application cannot find shared object
  • From: Paul Pluzhnikov
• Re: Rephrasing my UDP question
  • From: Anthony de Almeida Lopes
• Re: tools. approaches, schemes!!
  • From: Rich Teer
• Re: Rephrasing my UDP question
  • From: Anthony de Almeida Lopes
• Re: Application cannot find shared object
  • From: Robert Harris
• Re: Application cannot find shared object
  • From: googler
• Re: definition of terminal, et cetera
  • From: Pascal Bourguignon
• Re: definition of terminal, et cetera
  • From: Jordan Abel
• Re: definition of terminal, et cetera
  • From: Thomas Dickey
• tools. approaches, schemes!!
  • From: cpluspluskilla
• tools. approaches, schemes!!
  • From: cpluspluskilla
• Re: finding holes in the program
  • From: cpluspluskilla
• Application cannot find shared object
  • From: googler
• Re: sleep( ) misbehaving
  • From: syed
• Re: sleep( ) misbehaving
  • From: syed
• Re: sleep( ) misbehaving
  • From: joe
• Re: sleep( ) misbehaving
  • From: Ralf Fassel
• sleep( ) misbehaving
  • From: syed
• Re: definition of terminal, et cetera
  • From: Daniel C. Bastos
• Re: complex dictionary search engine with parallel processing???
  • From: jodasi
• Re: complex dictionary search engine with parallel processing???
  • From: jodasi
• Re: what the heck ist __attribute??
  • From: Luotao Fu
• Re: Socket inheritance: A tale of two vendors
  • From: David Schwartz
• Re: complex dictionary search engine with parallel processing???
  • From: Jordan Abel
• Re: Version information about libc.a
  • From: Paul Pluzhnikov
• Re: what the heck ist __attribute??
  • From: Luotao Fu
• Re: Version information about libc.a
  • From: Paul Pluzhnikov
• Re: what the heck ist __attribute??
  • From: "Nils O. Selåsdal"
• what the heck ist __attribute??
  • From: Luotao Fu
• Re: Version information about libc.a
  • From: Casper H . S . Dik
• Re: tool to view programs trace
  • From: Nils Weller
• Re: what the heck ist __attribute??
  • From: "Nils O. Selåsdal"
• Re: tool to view programs trace
  • From: Nils Weller
• Re: complex dictionary search engine with parallel processing???
  • From: jodasi
• Re: Socket inheritance: A tale of two vendors
  • From: googlegroups
• Re: Rephrasing my UDP question
  • From: Markus Elfring
• Re: Lex and Yacc
  • From: the_edge123 . nospam
• Re: 64 bit integer
  • From: "Nils O. Selåsdal"
• Lex and Yacc
  • From: None
• Re: setresuid() in multithreaded program - problem receiving SIG33
  • From: Jiri Klimes
• Re: Unsuccessful shmget
  • From: "Nils O. Selåsdal"
• using macro in 'htons()'
  • From: Roman Mashak
• Re: Version information about libc.a
  • From: Anunay
• Re: using macro in 'htons()'
  • From: Barry Margolin
• Re: Unsuccessful shmget
  • From: Barry Margolin
• Re: tool to view programs trace
  • From: Barry Margolin
• Re: finding holes in the program
  • From: cpluspluskilla
• Re: complex dictionary search engine with parallel processing???
  • From: David Schwartz
• Re: complex dictionary search engine with parallel processing???
  • From: Pascal Bourguignon
• complex dictionary search engine with parallel processing???
  • From: jodasi
• Re: Socket inheritance: A tale of two vendors
  • From: David Schwartz
• Unsuccessful shmget
  • From: felixfix
• Re: definition of terminal, et cetera
  • From: Gordon Burditt
• Re: definition of terminal, et cetera
  • From: Brian Raiter
• Re: printing
  • From: Roger Leigh
• Re: tool to view programs trace
  • From: Jordan Abel
• Re: printing
  • From: Simon Elliott
• Re: tool to view programs trace
  • From: Henry Townsend
• Re: Version information about libc.a
  • From: Anthony de Almeida Lopes
• Re: 64 bit integer
  • From: Keith Thompson
• Re: tool to view programs trace
  • From: Jordan Abel
• Re: Socket inheritance: A tale of two vendors
  • From: Chris Friesen
• Re: tool to view programs trace
  • From: Henry Townsend
• Re: pausing and continuing multiple processes (I just don't get it!);
  • From: mirtoni
• Re: Binding to a client port and REUSEADDR
  • From: Matt
• Re: tool to view programs trace
  • From: Jordan Abel
• Re: Version information about libc.a
  • From: Paul Pluzhnikov
• Re: finding holes in the program
  • From: Markus Elfring
• Re: definition of terminal, et cetera
  • From: Floyd L. Davidson
• Re: Binding to a client port and REUSEADDR
  • From: joe
• Re: tool to view programs trace
  • From: Henry Townsend
• Re: Binding to a client port and REUSEADDR
  • From: joe
• Re: definition of terminal, et cetera
  • From: Jordan Abel
• Re: tool to view programs trace
  • From: Jordan Abel
• Re: Socket inheritance: A tale of two vendors
  • From: googlegroups
• Re: Binding to a client port and REUSEADDR
  • From: joe
• Re: Rephrasing my UDP question
  • From: Anthony de Almeida Lopes
• Re: tool to view programs trace
  • From: Rich Teer
• Re: Socket inheritance: A tale of two vendors
  • From: Chris Friesen
• Re: Binding to a client port and REUSEADDR
  • From: Matt
• Re: pausing and continuing multiple processes (I just don't get it!);
  • From: Fletcher Glenn
• Re: Socket inheritance: A tale of two vendors
  • From: googlegroups
• Re: finding holes in the program
  • From: cpluspluskilla
• Re: Socket inheritance: A tale of two vendors
  • From: googlegroups
• Re: Binding to a client port and REUSEADDR
  • From: Hubble
• Re: 64 bit integer
  • From: Jay
• Re: 64 bit integer
  • From: Hubble
• Re: Socket inheritance: A tale of two vendors
  • From: Chris Friesen
• 64 bit integer
  • From: Jay
• Binding to a client port and REUSEADDR
  • From: Matt
• Re: finding holes in the program
  • From: Markus Elfring
• Re: Socket inheritance: A tale of two vendors
  • From: Chuck Dillon
• Re: definition of terminal, et cetera
  • From: Daniel C. Bastos
• How to write and read on network interfaces?
  • From: fabrizio
• Re: gtk2 newbie question
  • From: Gary
• Re: Rephrasing my UDP question
  • From: Alex Fraser
• Which language/toolkit to use for media player?
  • From: John Morey
• Re: gtk2 newbie question
  • From: "Nils O. Selåsdal"
• gtk2 newbie question
  • From: Gary
• Re: pausing and continuing multiple processes (I just don't get it!);
  • From: mirtoni
• Version information about libc.a
  • From: Anunay
• Re: pausing and continuing multiple processes (I just don't get it!);
  • From: mirtoni
• Re: tool to view programs trace
  • From: Thomas Maier-Komor
• Re: Rephrasing my UDP question
  • From: Anthony de Almeida Lopes
• Re: finding holes in the program
  • From: Bit Twister
• Re: tool to view programs trace
  • From: cpluspluskilla
• Re: tool to view programs trace
  • From: Thobias Vakayil
• Re: finding holes in the program
  • From: cpluspluskilla
• Re: finding holes in the program
  • From: Bjørn Augestad
• Re: tool to view programs trace
  • From: Barry Margolin
• Re: UDP Tunneling
  • From: Barry Margolin
• Re: Rephrasing my UDP question
  • From: Barry Margolin
• Re: finding holes in the program
  • From: cpluspluskilla
• Re: finding holes in the program
  • From: cpluspluskilla
• Re: finding holes in the program
  • From: Bjørn Augestad
• Re: Socket inheritance: A tale of two vendors
  • From: Barry Margolin
• tool to view programs trace
  • From: cpluspluskilla
• Re: UDP Tunneling
  • From: Anthony de Almeida Lopes
• Re: finding holes in the program
  • From: cpluspluskilla
• Re: finding holes in the program
  • From: cpluspluskilla
• Re: UDP Tunneling
  • From: Anthony de Almeida Lopes
• Re: Socket inheritance: A tale of two vendors
  • From: googlegroups
• Rephrasing my UDP question
  • From: Anthony de Almeida Lopes
• Re: UDP Tunneling
  • From: Pascal Bourguignon
• Re: Socket inheritance: A tale of two vendors
  • From: Chris Friesen
• Re: UDP Tunneling
  • From: Anthony de Almeida Lopes
• Re: UDP Tunneling
  • From: Pascal Bourguignon
• UDP Tunneling
  • From: Anthony de Almeida Lopes
• Re: definition of terminal, et cetera
  • From: Pascal Bourguignon
• Re: memory allocation issues?
  • From: Paul Pluzhnikov
• Re: malloc/free question
  • From: Brian Raiter
• Socket inheritance: A tale of two vendors
  • From: googlegroups
• Re: pausing and continuing multiple processes (I just don't get it!);
  • From: Fletcher Glenn
• Re: memory allocation issues?
  • From: Paul Pluzhnikov
• Re: definition of terminal, et cetera
  • From: Fletcher Glenn
• definition of terminal, et cetera
  • From: Daniel C. Bastos
• pausing and continuing multiple processes (I just don't get it!);
  • From: mirtoni
• memory allocation issues?
  • From: sunilkher
• Re: malloc/free question
  • From: David Schwartz
• Re: recording sound
  • From: Måns Rullgård
• Re: malloc/free question
  • From: Brian Raiter
• Re: malloc/free question
  • From: David Schwartz
• Re: malloc/free question
  • From: Keith Thompson
• Re: malloc/free question
  • From: David Schwartz
• Re: finding holes in the program
  • From: Giorgos Keramidas
• Re: Integer types "ambiguous"
  • From: Jordan Abel
• Re: finding holes in the program
  • From: Jordan Abel
• Re: malloc/free question
  • From: Brian Raiter
• Re: finding holes in the program
  • From: joe
• Re: setresuid() in multithreaded program - problem receiving SIG33
  • From: Igmar Palsenberg
• Re: setresuid() in multithreaded program - problem receiving SIG33
  • From: Casper H . S . Dik
• Re: finding holes in the program
  • From: Giorgos Keramidas
• Re: finding holes in the program
  • From: Zeljko Vrba
• Re: finding holes in the program
  • From: Chuck Dillon
• Re: trap/signal handler
  • From: Robert Harris
• Re: setresuid() in multithreaded program - problem receiving SIG33
  • From: Jiri Klimes
• recording sound
  • From: thomas jor.
• Re: finding holes in the program
  • From: Ralf Fassel
• Re: setresuid() in multithreaded program - problem receiving SIG33
  • From: Casper H . S . Dik
• Re: finding holes in the program
  • From: Markus Elfring
• trap/signal handler
  • From: davidjeyam
• Re: finding holes in the program
  • From: Bjørn Augestad
• Re: MAC Address
  • From: Henry Townsend
• Re: dynamically allocated memory
  • From: Maxim Yegorushkin
• setresuid() in multithreaded program - problem receiving SIG33
  • From: Jiri Klimes
• Re: finding holes in the program
  • From: Giorgos Keramidas
• Re: finding holes in the program
  • From: Bjørn Augestad
• Re: MAC Address
  • From: Joerg Schmitz-Linneweber
• Re: finding holes in the program
  • From: Wolfgang Riedel
• Re: finding holes in the program
  • From: Måns Rullgård
• Re: MAC Address
  • From: SM Ryan
• MAC Address
  • From: ashishjindal76
• Re: finding holes in the program
  • From: Gianni Mariani
• Re: Need some help with Search
  • From: pankaj_wolfhunter
• Re: Need some help with Search
  • From: pankaj_wolfhunter
• finding holes in the program
  • From: cpluspluskilla
• Re: Big/little endian conversion
  • From: Jordan Abel
• Re: Shell Script and dd command
  • From: pankaj_wolfhunter
• Re: Big/little endian conversion
  • From: Wayne C. Morris
• Re: dynamically allocated memory
  • From: Gordon Burditt
• Re: malloc/free question
  • From: David Schwartz
• Re: dynamically allocated memory
  • From: Jordan Abel
• Re: malloc/free question
  • From: Gordon Burditt
• Re: malloc/free question
  • From: David Schwartz
• Re: dynamically allocated memory
  • From: Gordon Burditt
• Re: malloc/free question
  • From: Gordon Burditt
• Re: fsync, unistd.h on gnu/linux/debian
  • From: Måns Rullgård
• fsync, unistd.h on gnu/linux/debian
  • From: Daniel C. Bastos
• Re: Move existing file
  • From: John Smith
• Re: Is there any way / editor to see code after preprocessing
  • From: John McCallum
• Re: Shell Script and dd command
  • From: Chris F.A. Johnson
• Re: Shell Script and dd command
  • From: "Nils O. Selåsdal"
• Re: Move existing file
  • From: Maxim Yegorushkin
• Re: Shell Script and dd command
  • From: pankaj_wolfhunter
• Re: I don't get the significance of the static option on gcc
  • From: Maxim Yegorushkin
• Re: dynamically allocated memory
  • From: Maxim Yegorushkin
• Re: Need some help with Search
  • From: Alex Fraser
• Re: Shell Script and dd command
  • From: "Nils O. Selåsdal"
• Shell Script and dd command
  • From: pankaj_wolfhunter
• Re: PIC code questions
  • From: Andrei Voropaev
• Re: malloc/free question
  • From: Andrei Voropaev
• Re: Big/little endian conversion
  • From: Pascal Bourguignon
• Re: Asynchronic communication between application in Linux.
  • From: Andrei Voropaev
• Re: "errno" problem
  • From: Roger Leigh
• Re: allocation technique for dynamic strings
  • From: Andrei Voropaev
• Re: Nonblocking socket read gets lots of EAGAIN
  • From: "Nils O. Selåsdal"
• Re: "errno" problem
  • From: =?gb18030?q?=22Nils_O=2E_Sel=810=8A2sdal=22?=
• Re: Big/little endian conversion
  • From: Gianni Mariani
• Re: Big/little endian conversion
  • From: David Schwartz
• Re: rename, why in stdio.h?
  • From: Henry Townsend
• Re: Need some help with Search
  • From: pankaj_wolfhunter
• Re: "errno" problem
  • From: Final
• Re: "errno" problem
  • From: Final
• Re: Big/little endian conversion
  • From: Gianni Mariani
• Re: Big/little endian conversion
  • From: Gianni Mariani
• Bug in proccgi
  • From: Mark Hobley
• Re: Big/little endian conversion
  • From: Jordan Abel
• Re: Big/little endian conversion
  • From: David Schwartz
• Re: rename, why in stdio.h?
  • From: Måns Rullgård
• Re: Big/little endian conversion
  • From: Gianni Mariani
• Re: rename, why in stdio.h?
  • From: Keith Thompson
• Re: rename, why in stdio.h?
  • From: Jordan Abel
• Re: Big/little endian conversion
  • From: David Schwartz
• Re: malloc/free question
  • From: David Schwartz
• Re: malloc/free question
  • From: David Schwartz
• Re: I don't get the significance of the static option on gcc
  • From: Pascal Bourguignon
• Re: Move existing file
  • From: Pascal Bourguignon
• I don't get the significance of the static option on gcc
  • From: Chad
• Re: storing unsigned in void*
  • From: micans
• Re: rename, why in stdio.h?
  • From: Henry Townsend
• Re: Need some help with Search
  • From: Jim Cochrane
• Re: Move existing file
  • From: Jim Cochrane
• Move existing file
  • From: John Smith
• Re: rename, why in stdio.h?
  • From: "Nils O. Selåsdal"
• Re: "errno" problem
  • From: "Nils O. Selåsdal"
• Re: "errno" problem
  • From: Roger Leigh
• Re: rename, why in stdio.h?
  • From: Måns Rullgård
• Re: rename, why in stdio.h?
  • From: Daniel C. Bastos
• Re: rename, why in stdio.h?
  • From: Måns Rullgård
• rename, why in stdio.h?
  • From: Daniel C. Bastos
• Re: Big/little endian conversion
  • From: Bjorn Reese
• Need some help with Search
  • From: pankaj_wolfhunter
• Asynchronic communication between application in Linux.
  • From: borneq
• Re: malloc/free question
  • From: Brian Raiter
• Re: malloc/free question
  • From: Keith Thompson
• Re: malloc/free question
  • From: David Schwartz
• Re: malloc/free question
  • From: David Schwartz
• Re: malloc/free question
  • From: Gordon Burditt
• Re: malloc/free question
  • From: Keith Thompson
• Nonblocking socket read gets lots of EAGAIN
  • From: mblt
• Re: malloc/free question
  • From: David Schwartz
• Re: malloc/free question
  • From: David Schwartz
• Re: malloc/free question
  • From: Gordon Burditt
• Re: Big/little endian conversion
  • From: Gianni Mariani
• Re: dynamically allocated memory
  • From: Henry Townsend
• Re: allocation technique for dynamic strings
  • From: Roger Leigh
• Re: dynamically allocated memory
  • From: Måns Rullgård
• Re: malloc/free question
  • From: Måns Rullgård
• Re: allocation technique for dynamic strings
  • From: Måns Rullgård
• Re: Big/little endian conversion
  • From: Bjorn Reese
• Re: Is there any way / editor to see code after preprocessing
  • From: Bjorn Reese
• Re: allocation technique for dynamic strings
  • From: Roger Leigh
• Re: allocation technique for dynamic strings
  • From: Gianni Mariani
• Re: Big/little endian conversion
  • From: Gianni Mariani
• Re: malloc/free question
  • From: Gordon Burditt
• Re: dynamically allocated memory
  • From: Gordon Burditt
• Re: Big/little endian conversion
  • From: John Brockmeyer
• Re: Big/little endian conversion
  • From: Barry Margolin
• Re: gethostbyaddr doing a A query
  • From: Barry Margolin
• Re: malloc/free question
  • From: Barry Margolin
• Re: malloc/free question
  • From: Russell Shaw
• C99 standard (was Re: storing unsigned in void*)
  • From: Tim Heaney
• Re: malloc/free question
  • From: Pascal Bourguignon
• Re: storing unsigned in void*
  • From: Brian Raiter
• Re: Is there any way / editor to see code after preprocessing
  • From: Brian Raiter
• Re: malloc/free question
  • From: Keith Thompson
• Re: Big/little endian conversion
  • From: toby
• Re: Big/little endian conversion
  • From: David Schwartz
• Re: allocation technique for dynamic strings
  • From: Måns Rullgård
• Re: Big/little endian conversion
  • From: David Schwartz
• Re: allocation technique for dynamic strings
  • From: Måns Rullgård
• Re: allocation technique for dynamic strings
  • From: Roger Leigh
• Re: Big/little endian conversion
  • From: Chris Friesen
• Re: Big/little endian conversion
  • From: JH Trauntvein
• Re: allocation technique for dynamic strings
  • From: Henry Townsend
• Re: allocation technique for dynamic strings
  • From: Daniel C. Bastos
• Re: allocation technique for dynamic strings
  • From: Daniel C. Bastos
• Re: Big/little endian conversion
  • From: mobenoua
• Re: Big/little endian conversion
  • From: David Schwartz
• Re: encryption error - WHY?
  • From: puzzlecracker
• Re: allocation technique for dynamic strings
  • From: Måns Rullgård
• Big/little endian conversion
  • From: mobenoua
• Re: Is there any way / editor to see code after preprocessing
  • From: Fletcher Glenn
• Re: allocation technique for dynamic strings
  • From: Robert Harris
• allocation technique for dynamic strings
  • From: Daniel C. Bastos
• Re: signal, parent & children processes
  • From: Alex Vinokur
• Re: Is there any way / editor to see code after preprocessing
  • From: Bjorn Reese
• Re: execvp() and background process exit
  • From: Maxim Yegorushkin
• Re: signal, parent & children processes
  • From: Alex Vinokur
• Re: malloc/free question
  • From: gremnebulin
• Re: malloc/free question
  • From: gremnebulin
• Re: encryption error - WHY?
  • From: John Gordon
• Re: malloc/free question
  • From: gremnebulin
• Re: malloc/free question
  • From: John Gordon
• Re: malloc/free question
  • From: gremnebulin
• Re: execvp() and background process exit
  • From: quetzalcotl
• Re: Problem with snmp query
  • From: Robert Harris
• Re: gethostbyaddr doing a A query
  • From: pappu72_99
• signal, parent & children processes
  • From: Alex Vinokur
• Re: return value makes me sad.
  • From: Maurizio Loreti
• Re: return value makes me sad.
  • From: Hubble
• Re: PIC code questions
  • From: Hubble
• Re: dynamically allocated memory
  • From: Russell Shaw
• Problem with snmp query
  • From: sanny.h@xxxxxxxxx
• Re: Calling all Programers, Software Engineers, Artists and Sound Bytes, YOU ARE NEEDED
  • From: John C . Randolph
• Re: Calling all Programers, Software Engineers, Artists and Sound Bytes, YOU ARE NEEDED
  • From: John C . Randolph
• Re: Calling all Programers, Software Engineers, Artists and Sound Bytes, YOU ARE NEEDED
  • From: John C . Randolph
• Re: Is there any way / editor to see code after preprocessing
  • From: Markus Elfring
• Re: dynamically allocated memory
  • From: Maxim Yegorushkin
• Re: PIC code questions
  • From: Maxim Yegorushkin
• Re: PIC code questions
  • From: Hubble
• Re: execvp() and background process exit
  • From: Hubble
• Re: execvp() and background process exit
  • From: Alex Vinokur
• execvp() and background process exit
  • From: Alex Vinokur
• Re: malloc/free question
  • From: Keith Thompson
• Re: malloc/free question
  • From: "Nils O. Selåsdal"
• Re: malloc/free question
  • From: toby
• Re: malloc/free question
  • From: Robert M. Gary
• Re: malloc/free question
  • From: Robert M. Gary
• Re: malloc/free question
  • From: Robert M. Gary
• Re: dynamically allocated memory
  • From: Frank Cusack
• encryption error - WHY?
  • From: cpluspluskilla
• Re: problems with sockets -- Help
  • From: clayne
• Re: malloc/free question
  • From: Brian Raiter
• Re: dynamically allocated memory
  • From: David Schwartz
• Re: Is there any way / editor to see code after preprocessing
  • From: Brian Raiter
• Re: malloc/free question
  • From: Russell Shaw
• Re: dynamically allocated memory
  • From: Russell Shaw
• Re: storing unsigned in void*
  • From: Keith Thompson
• Re: storing unsigned in void*
  • From: Keith Thompson
• Re: malloc/free question
  • From: joe
• Re: malloc/free question
  • From: Keith Thompson
• Re: malloc/free question
  • From: Keith Thompson
• Re: dynamically allocated memory
  • From: David Schwartz
• Re: malloc/free question
  • From: David Schwartz
• Re: dynamically allocated memory
  • From: Bjørn Augestad
• Re: dynamically allocated memory
  • From: Simon Elliott
• Re: dynamically allocated memory
  • From: Jordan Abel
• Re: get home directory
  • From: Måns Rullgård
• Re: malloc/free question
  • From: joe
• Re: malloc/free question
  • From: vk02720
• Re: dynamically allocated memory
  • From: David Schwartz
• Re: malloc/free question
  • From: Pascal Bourguignon
• Re: dynamically allocated memory
  • From: Simon Elliott
• Re: malloc/free question
  • From: David Schwartz
• Re: malloc/free question
  • From: David Schwartz
• Re: malloc/free question
  • From: joe
• Re: malloc/free question
  • From: joe
• Re: malloc/free question
  • From: Mikko Rauhala
• Re: malloc/free question
  • From: joe
• Re: malloc/free question
  • From: Mikko Rauhala
• Re: malloc/free question
  • From: joe
• Re: malloc/free question
  • From: gremnebulin
• Re: malloc/free question
  • From: gremnebulin
• Re: malloc/free question
  • From: #2pencil
• malloc/free question
  • From: vk02720
• Re: Is there any way / editor to see code after preprocessing
  • From: Norm Dresner
• snd_async_add_pcm_handler
  • From: Simon Elliott
• Proccedure regarding Upload/Download speed for ADSL connection
  • From: ravicse04
• Proccedure regarding Upload/Download speed for ADSL connection
  • From: ravicse04
• Re: PIC code questions
  • From: krumblebunk
• Re: PIC code questions
  • From: "Nils O. Selåsdal"
• Re: PIC code questions
  • From: Henry Townsend
• Re: return value makes me sad.
  • From: Pascal Bourguignon
• Re: return value makes me sad.
  • From: ambrish . k . baranwal
• Re: get home directory
  • From: Ralf Fassel
• Re: dynamically allocated memory
  • From: Maxim Yegorushkin
• Re: PIC code questions
  • From: Maxim Yegorushkin
• PIC code questions
  • From: krumblebunk
• Re: return value makes me sad.
  • From: Thobias Vakayil
• Re: Is there any way / editor to see code after preprocessing
  • From: Bjorn Reese
• return value makes me sad.
  • From: Mr.Babo
• Re: get home directory
  • From: Gordon Burditt
• Re: dynamically allocated memory
  • From: "Nils O. Selåsdal"
• Re: dynamically allocated memory
  • From: Barry Margolin
• Re: get home directory
  • From: Barry Margolin
• Re: Is there any way / editor to see code after preprocessing
  • From: Barry Margolin
• Re: Writing HTTP header
  • From: Barry Margolin
• Re: get home directory
  • From: Gordon Burditt
• Re: How to pass arguments with '*' to execvp()?
  • From: Mr. Uh Clem
• Re: get home directory
  • From: Henry Townsend
• Re: nonatomic method in signal handler
  • From: Chris Vine
• Re: Writing HTTP header
  • From: joe
• dynamically allocated memory
  • From: vk02720
• Re: Writing HTTP header
  • From: David Schwartz
• Re: Writing HTTP header
  • From: drhowarddrfine
• Re: Writing HTTP header
  • From: joe
• Re: How to pass arguments with '*' to execvp()?
  • From: Chris F.A. Johnson
• Re: Writing HTTP header
  • From: drhowarddrfine
• Re: How to pass arguments with '*' to execvp()?
  • From: Chris F.A. Johnson
• Re: How to pass arguments with '*' to execvp()?
  • From: Pascal Bourguignon
• Re: get home directory
  • From: Måns Rullgård
• Re: Is there any way / editor to see code after preprocessing
  • From: Fletcher Glenn
• Re: How to pass arguments with '*' to execvp()?
  • From: Mr. Uh Clem
• Re: Clocking proccesses' time
  • From: babis85
• Re: get home directory
  • From: Jordan Abel
• Re: get home directory
  • From: Gordon Burditt
• Re: get home directory
  • From: joe
• Re: Writing HTTP header
  • From: John Gordon
• Re: Writing HTTP header
  • From: Måns Rullgård
• get home directory
  • From: thomas jor.
• Re: problems with sockets -- Help
  • From: David Schwartz
• Re: Is there any way / editor to see code after preprocessing
  • From: Bjorn Reese
• Re: Writing HTTP header
  • From: David Schwartz
• Re: Lex & YAcc
  • From: "Nils O. Selåsdal"
• Re: how to dump a core inside gdb
  • From: Jeremy
• problems with sockets -- Help
  • From: sheadley
• Re: real and virtual memory statistics on hp-ux and tru64
  • From: Don Morris
• Is there any way / editor to see code after preprocessing
  • From: bharmaji
• Is there any way / editor to see code after preprocessing
  • From: bharmaji
• Re: Unix Need Help with auto incrementing a field between delimiter. Awk?
  • From: Bill Marcum
• Re: Writing HTTP header
  • From: Brian Utterback
• Re: Writing HTTP header
  • From: Robert Harris
• Re: Writing HTTP header
  • From: Markus Elfring
• Re: how to dump a core inside gdb
  • From: Chris Markle
• Re: real and virtual memory statistics on hp-ux and tru64
  • From: jtucker
• Re: real and virtual memory statistics on hp-ux and tru64
  • From: Maxim Yegorushkin
• real and virtual memory statistics on hp-ux and tru64
  • From: jtucker
• Re: Writing HTTP header
  • From: drhowarddrfine
• Unix Need Help with auto incrementing a field between delimiter. Awk?
  • From: AMBROZE
• Lex & YAcc
  • From: kmlrao
• strcoll and locale
  • From: Vladimir Zolotykh
• Re: Writing HTTP header
  • From: Barry Margolin
• Re: how to dump a core inside gdb
  • From: David Resnick
• Re: Writing HTTP header
  • From: drhowarddrfine
• Re: Writing HTTP header
  • From: Brian Utterback
• Re: how to dump a core inside gdb
  • From: Thobias Vakayil
• Re: nonatomic method in signal handler
  • From: Maxim Yegorushkin
• how to dump a core inside gdb
  • From: Jeremy

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