comp.unix.programmer

• Date Index

---

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

• Security
• UNIX
• Linux
• Coding
• Usenet

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

unix.derkeiler.com  > Newsgroups  > comp.unix.programmer  > 2008-07