comp.unix.programmer

• Date Index

---

• How to make C++ code fork-safe?, Arkadiy
• C/C++ on UNIX Developer required in Woodmead, Johannesburg, arnold
  • Re: C/C++ on UNIX Developer required in Woodmead, Johannesburg, Rainer Weikusat
• pthread_cond_timedwait and signal handler, Jiri Klimes
  • Re: pthread_cond_timedwait and signal handler, chkl
• High-performance server: epoll or a thread pool?, Arkadiy
  • Re: High-performance server: epoll or a thread pool?, Rainer Weikusat
  • Re: High-performance server: epoll or a thread pool?, Chris Friesen
  • Re: High-performance server: epoll or a thread pool?, Rick Jones
• timer sanity check, Arkadiy
  • Re: timer sanity check, fjblurt
• killing a large lists of pids, K-mart Cashier
  • Re: killing a large lists of pids, Joachim Schmitz
    • Re: killing a large lists of pids, J de Boyne Pollard
      • Re: killing a large lists of pids, Kurt M. Weber
      • Re: killing a large lists of pids, Logan Shaw
      • killing a large lists of pids, J de Boyne Pollard
  • Re: killing a large lists of pids, Benoit Lefebvre
    • Re: killing a large lists of pids, K-mart Cashier
    • Re: killing a large lists of pids, shakahshakah@xxxxxxxxx
    • Re: killing a large lists of pids, Barry Margolin
      • Re: killing a large lists of pids, Henry Townsend
  • Re: killing a large lists of pids, fjblurt
    • Re: killing a large lists of pids, William Ahern
• mail / how to send a pre-composed multiple mail file?, rhXX
  • Re: mail / how to send a pre-composed multiple mail file?, Logan Shaw
    • Re: mail / how to send a pre-composed multiple mail file?, rhXX
• c printf/variables content visible in compiled binary. How to hide that ?, Benoit Lefebvre
  • Re: c printf/variables content visible in compiled binary. How to hide that ?, dj3vande
    • Re: c printf/variables content visible in compiled binary. How to hide that ?, Benoit Lefebvre
      • Re: c printf/variables content visible in compiled binary. How to hide that ?, dj3vande
      • Re: c printf/variables content visible in compiled binary. How to hide that ?, David Schwartz
  • Re: c printf/variables content visible in compiled binary. How to hide that ?, Roger Leigh
    • Re: c printf/variables content visible in compiled binary. How to hide that ?, Benoit Lefebvre
      • Re: c printf/variables content visible in compiled binary. How to hide that ?, Paul Pluzhnikov
      • Re: c printf/variables content visible in compiled binary. How to hide that ?, dj3vande
      • Re: c printf/variables content visible in compiled binary. How to hide that ?, Kenny McCormack
      • Re: c printf/variables content visible in compiled binary. How to hide that ?, Logan Shaw
      • Re: c printf/variables content visible in compiled binary. How to hide that ?, Henry Townsend
      • Re: c printf/variables content visible in compiled binary. How to hide that ?, David Schwartz
  • Re: c printf/variables content visible in compiled binary. How to hide that ?, poulacou
• Design of x-window system, Zachary Turner
  • Re: Design of x-window system, Rob Hoelz
    • Re: Design of x-window system, Zachary Turner
    • Re: Design of x-window system, Boltar
      • Re: Design of x-window system, Zachary Turner
• Unicode character decomposition Unix library?, SM Ryan
  • Re: Unicode character decomposition Unix library?, William Ahern
    • Re: Unicode character decomposition Unix library?, SM Ryan
• kernel module unresolved symbol, paoletti . ste
• how to access the keyboard ps/2 port directly?, skam
  • Re: how to access the keyboard ps/2 port directly?, Roger Leigh
• Conceptual question on writeable file descriptors, K-mart Cashier
  • Re: Conceptual question on writeable file descriptors, fjblurt
    • Re: Conceptual question on writeable file descriptors, K-mart Cashier
• booting problem, asit
  • Re: booting problem, Bill Marcum
  • Re: booting problem, fjblurt
• new filesystem module, ste . paoletti
  • Re: new filesystem module, elsiddik
    • Re: new filesystem module, ste . paoletti
• Is clock_nanosleep() async-signal safe?, Spoon
  • Re: Is clock_nanosleep() async-signal safe?, Geoff Clare
    • Re: Is clock_nanosleep() async-signal safe?, Spoon
      • Re: Is clock_nanosleep() async-signal safe?, Geoff Clare
• Whu I value doesn't change ?, sophia . agnes
  • Re: Whu I value doesn't change ?, Kurt M. Weber
  • Re: Whu I value doesn't change ?, David Schwartz
• welcome to the club - OS X, Henry Townsend
• how to calculate max file / partition size, Jason Maur
  • Re: how to calculate max file / partition size, Måns Rullgård
    • Re: how to calculate max file / partition size, Jason Maur
• Question on a wrapper function., K-mart Cashier
  • Re: Question on a wrapper function., fjblurt
• libstdc++ compatibility frustrations under linux x86, Henrik Goldman
  • Re: libstdc++ compatibility frustrations under linux x86, Spoon
    • Re: libstdc++ compatibility frustrations under linux x86, Henrik Goldman
  • Re: libstdc++ compatibility frustrations under linux x86, Paul Pluzhnikov
    • Re: libstdc++ compatibility frustrations under linux x86, Henrik Goldman
• Socket programming: Command and Data socket, rsergeant
  • Re: Socket programming: Command and Data socket, Rainer Weikusat
    • Re: Socket programming: Command and Data socket, rsergeant
• termios/ioctl: What is the function to force a keystroke into a tty?, Kenny McCormack
  • Re: termios/ioctl: What is the function to force a keystroke into a tty?, Barry Margolin
    • Re: termios/ioctl: What is the function to force a keystroke into a tty?, Kenny McCormack
      • Re: termios/ioctl: What is the function to force a keystroke into a tty?, Spoon
      • Re: termios/ioctl: What is the function to force a keystroke into a tty?, Scott Lurndal
      • Re: termios/ioctl: What is the function to force a keystroke into a tty?, Spoon
• which glibc my "self extractable"/ binary is using?, Neo
  • Re: which glibc my "self extractable"/ binary is using?, fjblurt
    • Re: which glibc my "self extractable"/ binary is using?, Neo
      • Re: which glibc my "self extractable"/ binary is using?, fjblurt
      • Re: which glibc my "self extractable"/ binary is using?, Bill Marcum
• open/fopen read/fread in multithreaded environment., Sheth Raxit
• Best way to check when pty slave has closed?, Boltar
  • Re: Best way to check when pty slave has closed?, Casper H . S . Dik
    • Re: Best way to check when pty slave has closed?, Boltar
      • Re: Best way to check when pty slave has closed?, Rainer Weikusat
      • Re: Best way to check when pty slave has closed?, Casper H . S . Dik
      • Re: Best way to check when pty slave has closed?, Boltar
• How can get process id of a process running on remote machine., sandy
  • Re: How can get process id of a process running on remote machine., shakahshakah@xxxxxxxxx
    • Re: How can get process id of a process running on remote machine., sandy
• www.freebsd.org times out, Spoon
  • Re: www.freebsd.org times out, Giorgos Keramidas
    • Re: www.freebsd.org times out, Spoon
      • Re: www.freebsd.org times out, Giorgos Keramidas
      • Re: www.freebsd.org times out, Spoon
      • Re: www.freebsd.org times out, Giorgos Keramidas
      • Re: www.freebsd.org times out, Spoon
      • Re: www.freebsd.org times out, Giorgos Keramidas
      • Re: www.freebsd.org times out, Spoon
• Re: question to printf(), Johannes Bauer
  • <Possible follow-ups>
  • Re: question to printf(), Eric Sosman
• Please explain me the below code, kiran
  • Re: Please explain me the below code, Lew Pitcher
    • Re: Please explain me the below code, kiran
      • Re: Please explain me the below code, Lew Pitcher
      • Re: Please explain me the below code, Rainer Weikusat
      • Re: Please explain me the below code, kiran
      • Re: Please explain me the below code, James Antill
    • Re: Please explain me the below code, Scott Lurndal
• Detecting network file system, Henrik Goldman
  • Re: Detecting network file system, moi
  • Re: Detecting network file system, Eric Sosman
    • Re: Detecting network file system, Henrik Goldman
      • Re: Detecting network file system, Eric Sosman
      • Re: Detecting network file system, Rainer Weikusat
      • Re: Detecting network file system, Rainer Weikusat
      • Re: Detecting network file system, Juha Laiho
      • Re: Detecting network file system, Rainer Weikusat
      • Re: Detecting network file system, fjblurt
      • Re: Detecting network file system, Rainer Weikusat
      • Re: Detecting network file system, David Schwartz
• how to access the memory information using c++ on unix, pp
  • Re: how to access the memory information using c++ on unix, Rainer Weikusat
  • Re: how to access the memory information using c++ on unix, Alex Fraser
    • Re: how to access the memory information using c++ on unix, Rainer Weikusat
  • Re: how to access the memory information using c++ on unix, toby
    • Re: how to access the memory information using c++ on unix, pp
      • Re: how to access the memory information using c++ on unix, Rainer Weikusat
      • Re: how to access the memory information using c++ on unix, Eric Sosman
      • Re: how to access the memory information using c++ on unix, David Schwartz
      • Re: how to access the memory information using c++ on unix, Gordon Burditt
• Memory Leaks in Readline Library, Josh
• How do I pass signals to a slave pty in linux?, Boltar
  • Re: How do I pass signals to a slave pty in linux?, Boltar
  • Re: How do I pass signals to a slave pty in linux?, Rainer Weikusat
• text file being corrupted, Keith Halligan
  • Re: text file being corrupted, Rainer Weikusat
    • Re: text file being corrupted, Spoon
      • Re: text file being corrupted, Joachim Schmitz
• error while loading shared libraries on amd64, Yaniv
  • Re: error while loading shared libraries on amd64, Paul Pluzhnikov
    • Re: error while loading shared libraries on amd64, Yaniv
      • Re: error while loading shared libraries on amd64, Paul Pluzhnikov
• Parsing svn version, Henrik Goldman
  • Re: Parsing svn version, Ben Bacarisse
    • Re: Parsing svn version, Henrik Goldman
    • Re: Parsing svn version, Henrik Goldman
      • Re: Parsing svn version, Logan Shaw
      • Re: Parsing svn version, Henrik Goldman
  • Re: Parsing svn version, Logan Shaw
• Difference between euid and uid, lak
  • Re: Difference between euid and uid, Rainer Weikusat
• Shared Library descripancy, som
  • <Possible follow-ups>
  • Shared Library descripancy, som
• Long life span LED slim light box-http://www.edlite.hk, jenny
• message queue problem, ganesh bora
• Record level multithread read/write online ref required, Sheth Raxit
• makefile problem: multiple targets in single rule, Morfys
  • Re: makefile problem: multiple targets in single rule, toby
    • Re: makefile problem: multiple targets in single rule, Morfys
• Serialport termios & timeout, simnav
  • Re: Serialport termios & timeout, Robert Harris
• sed ':p /\\$/N; s/\\\n/ /; tp; ', William Pursell
  • Re: sed ':p /\\$/N; s/\\\n/ /; tp; ', Bill Marcum
• freeing memory leads to sig fault, Ryan Knopp
  • Re: freeing memory leads to sig fault, Joachim Schmitz
    • Re: freeing memory leads to sig fault, Joachim Schmitz
      • Re: freeing memory leads to sig fault, Ryan Knopp
      • Re: freeing memory leads to sig fault, Eric Sosman
      • Re: freeing memory leads to sig fault, Wayne C. Morris
      • Re: freeing memory leads to sig fault, Wayne C. Morris
  • Re: freeing memory leads to sig fault, fjblurt
  • Re: freeing memory leads to sig fault, Wayne C. Morris
    • Re: freeing memory leads to sig fault, Ryan Knopp
      • Re: freeing memory leads to sig fault, moi
      • Re: freeing memory leads to sig fault, moi
      • Re: freeing memory leads to sig fault, Ryan Knopp
      • Re: freeing memory leads to sig fault, Ben Bacarisse
      • Re: freeing memory leads to sig fault, Ryan Knopp
      • Re: freeing memory leads to sig fault, Spoon
• A possible vague question about ttys, K-mart Cashier
  • Re: A possible vague question about ttys, Barry Margolin
• epoll and timeouts, Arkadiy
  • Re: epoll and timeouts, fjblurt
    • Re: epoll and timeouts, Arkadiy
      • Re: epoll and timeouts, fjblurt
      • Re: epoll and timeouts, Arkadiy
      • Re: epoll and timeouts, David Schwartz
      • Re: epoll and timeouts, Arkadiy
      • Re: epoll and timeouts, William Ahern
      • Re: epoll and timeouts, Rainer Weikusat
      • Re: epoll and timeouts, William Ahern
      • Re: epoll and timeouts, David Schwartz
      • Re: epoll and timeouts, Arkadiy
      • Re: epoll and timeouts, David Schwartz
      • Re: epoll and timeouts, Arkadiy
      • Re: epoll and timeouts, David Schwartz
      • Re: epoll and timeouts, Arkadiy
• Fast communication, Tim Frink
  • Re: Fast communication, Benoit Lefebvre
    • Re: Fast communication, Stephan Ceram
  • Re: Fast communication, William Ahern
    • Re: Fast communication, Stephan Ceram
      • Re: Fast communication, Peter J. Holzer
    • Re: Fast communication, Stephan Ceram
      • Re: Fast communication, William Ahern
  • Re: Fast communication, Alex Fraser
• ksh : printing a file to stdout with the variables expanded, sonyantony@xxxxxxxxxxx
  • Re: ksh : printing a file to stdout with the variables expanded, Benoit Lefebvre
  • Re: ksh : printing a file to stdout with the variables expanded, Chris F.A. Johnson
    • Re: ksh : printing a file to stdout with the variables expanded, Logan Shaw
      • Re: ksh : printing a file to stdout with the variables expanded, Kenny McCormack
• initlog is deprecated, wong_powah
  • Re: initlog is deprecated, Barry Margolin
• HP-UX 11.11 invalid loader fixup, Henrik Goldman
• core dump for str, harry
  • Re: core dump for str, Ulrich Eckhardt
    • Re: core dump for str, harry
      • Re: core dump for str, Joachim Schmitz
      • Re: core dump for str, Ulrich Eckhardt
      • Re: core dump for str, Geoff Clare
      • Re: core dump for str, John Gordon
  • Re: core dump for str, Joachim Schmitz
• memory release problem, npcmarques@xxxxxxxxx
  • Re: memory release problem, Alex Fraser
    • Re: memory release problem, npcmarques@xxxxxxxxx
      • Re: memory release problem, Don Morris
  • Re: memory release problem, Eric Sosman
  • Re: memory release problem, David Schwartz
    • Re: memory release problem, npcmarques@xxxxxxxxx
• How to get current US/Eastern date and time, dragoncoder
  • Re: How to get current US/Eastern date and time, Rainer Weikusat
    • Re: How to get current US/Eastern date and time, dragoncoder
      • Re: How to get current US/Eastern date and time, Eric Sosman
  • Re: How to get current US/Eastern date and time, Jim Marshall
• Re: 11 datagrams in a PF_UNIX datagram system buffer, Spoon
• call to calloc() segfaulting, Kurt M. Weber
  • Re: call to calloc() segfaulting, John Gordon
    • Re: call to calloc() segfaulting, Kurt M. Weber
  • Re: call to calloc() segfaulting, moi
    • Re: call to calloc() segfaulting, Kurt M. Weber
      • Re: call to calloc() segfaulting, Ben Bacarisse
      • Re: call to calloc() segfaulting, Kurt M. Weber
      • Re: call to calloc() segfaulting, Eric Sosman
      • Re: call to calloc() segfaulting, Giorgos Keramidas
      • Re: call to calloc() segfaulting, Joachim Schmitz
      • Re: call to calloc() segfaulting, Rainer Weikusat
      • Re: call to calloc() segfaulting, Eric Sosman
      • Re: call to calloc() segfaulting, Scott Lurndal
      • Re: call to calloc() segfaulting, Casper H . S . Dik
      • Re: call to calloc() segfaulting, John Tsiombikas
      • Re: call to calloc() segfaulting, John Tsiombikas
      • Re: call to calloc() segfaulting, Henry Townsend
      • Re: call to calloc() segfaulting, John Tsiombikas
      • Re: call to calloc() segfaulting, Giorgos Keramidas
      • Re: call to calloc() segfaulting, Rainer Weikusat
      • Re: call to calloc() segfaulting, Casper H . S . Dik
      • Re: call to calloc() segfaulting, moi
  • Re: call to calloc() segfaulting, Ben Bacarisse
• writing in a file, eliminating output, simon_k50
  • Re: writing in a file, eliminating output, Ben Bacarisse
    • Re: writing in a file, eliminating output, simon_k50
      • Re: writing in a file, eliminating output, Ralf Fassel
      • Re: writing in a file, eliminating output, Ben Bacarisse
• checking OS type in Makefile?, William Xu
  • Re: checking OS type in Makefile?, KC
    • Re: checking OS type in Makefile?, William Xu
  • Re: checking OS type in Makefile?, Giorgos Keramidas
    • Re: checking OS type in Makefile?, William Xu
• How can I know a socket was actually created before using it, Andrew Falanga
  • Re: How can I know a socket was actually created before using it, David Schwartz
• syslog(3) blocks when local socket is full, Spoon
  • Re: syslog(3) blocks when local socket is full, Rainer Weikusat
    • Re: syslog(3) blocks when local socket is full, Spoon
      • Re: syslog(3) blocks when local socket is full, Rainer Weikusat
      • Re: syslog(3) blocks when local socket is full, Keith Willis
      • Re: syslog(3) blocks when local socket is full, Rainer Weikusat
• Finding libraries to link to..., Jamie Ostrowski
  • Re: Finding libraries to link to..., Paul Pluzhnikov
    • Re: Finding libraries to link to..., Geoff Clare
• Getting ip address from udp packet., Ryan Knopp
  • Re: Getting ip address from udp packet., Chris Friesen
    • Re: Getting ip address from udp packet., Ryan Knopp
      • Re: Getting ip address from udp packet., Chris Friesen
• fork/exec/waitpid/SIGCHLD/zombie - design && implementation question, asclearuc
  • Re: fork/exec/waitpid/SIGCHLD/zombie - design && implementation question, Loic Domaigne
    • Re: fork/exec/waitpid/SIGCHLD/zombie - design && implementation question, asclearuc
      • Re: fork/exec/waitpid/SIGCHLD/zombie - design && implementation question, Barry Margolin
• how to automatically print a backtrace of an application on segfault, Helfer Thomas
  • Re: how to automatically print a backtrace of an application on segfault, fjblurt
    • Re: how to automatically print a backtrace of an application on segfault, Helfer Thomas
      • Re: how to automatically print a backtrace of an application on segfault, dexkid
• Port code from Solaris to Linux, Leo Calado
  • Re: Port code from Solaris to Linux, fjblurt
    • Re: Port code from Solaris to Linux, William Xu
  • Re: Port code from Solaris to Linux, William Ahern
    • Re: Port code from Solaris to Linux, Leo Calado
      • Re: Port code from Solaris to Linux, William Ahern
      • Re: Port code from Solaris to Linux, Giorgos Keramidas
• Fork Exec Pipe: HOW???, Phoenix87
  • Re: Fork Exec Pipe: HOW???, fjblurt
    • Re: Fork Exec Pipe: HOW???, Phoenix87
      • Re: Fork Exec Pipe: HOW???, SM Ryan
      • Re: Fork Exec Pipe: HOW???, Johannes Bauer
      • Re: Fork Exec Pipe: HOW???, Barry Margolin
      • Re: Fork Exec Pipe: HOW???, Johannes Bauer
      • Re: Fork Exec Pipe: HOW???, Johannes Bauer
      • Re: Fork Exec Pipe: HOW???, Logan Shaw
      • Re: Fork Exec Pipe: HOW???, Barry Margolin
      • Re: Fork Exec Pipe: HOW???, Geoff Clare
      • Re: Fork Exec Pipe: HOW???, Phoenix87
      • Re: Fork Exec Pipe: HOW???, fjblurt
      • Re: Fork Exec Pipe: HOW???, Rainer Weikusat
      • Re: Fork Exec Pipe: HOW???, Phoenix87
      • Re: Fork Exec Pipe: HOW???, Rainer Weikusat
      • Re: Fork Exec Pipe: HOW???, Phoenix87
      • Re: Fork Exec Pipe: HOW???, Rainer Weikusat
      • Re: Fork Exec Pipe: HOW???, Phoenix87
• select() and fd_set *exceptfds, Daniel C. Bastos
  • Re: select() and fd_set *exceptfds, David Schwartz
• Determining which thread terminated first, Bill
  • Re: Determining which thread terminated first, David Schwartz
  • Re: Determining which thread terminated first, Eric Sosman
    • Re: Determining which thread terminated first, CJ
      • Re: Determining which thread terminated first, toby
      • Re: Determining which thread terminated first, Bill
      • Re: Determining which thread terminated first, David Schwartz
      • Re: Determining which thread terminated first, Bill
      • Re: Determining which thread terminated first, Bill
      • Re: Determining which thread terminated first, Bill
      • Re: Determining which thread terminated first, Golden California Girls
      • Re: Determining which thread terminated first, Bill
      • Re: Determining which thread terminated first, Eric Sosman
      • Re: Determining which thread terminated first, Bill
      • Re: Determining which thread terminated first, Eric Sosman
      • Re: Determining which thread terminated first, David Schwartz
      • Re: Determining which thread terminated first, Bill
      • Re: Determining which thread terminated first, Eric Sosman
      • Re: Determining which thread terminated first, Bill
      • Re: Determining which thread terminated first, David Schwartz
      • Re: Determining which thread terminated first, David Schwartz
      • Re: Determining which thread terminated first, Bill
      • Re: Determining which thread terminated first, Golden California Girls
      • Re: Determining which thread terminated first, David Schwartz
      • Re: Determining which thread terminated first, Bill
      • Re: Determining which thread terminated first, Golden California Girls
      • Re: Determining which thread terminated first, David Schwartz
      • Re: Determining which thread terminated first, Eric Sosman
      • Re: Determining which thread terminated first, CJ
  • Re: Determining which thread terminated first, Sheth Raxit
    • Re: Determining which thread terminated first, Bill
      • Re: Determining which thread terminated first, David Schwartz
      • Re: Determining which thread terminated first, Golden California Girls
      • Re: Determining which thread terminated first, Sheth Raxit
• compiling 'make' w/o 'make' (?), jamiil
  • Re: compiling 'make' w/o 'make' (?), Chris Friesen
  • Re: compiling 'make' w/o 'make' (?), fjblurt
    • Re: compiling 'make' w/o 'make' (?), jellybean stonerfish
      • Re: compiling 'make' w/o 'make' (?), fjblurt
      • Re: compiling 'make' w/o 'make' (?), jellybean stonerfish
      • Re: compiling 'make' w/o 'make' (?), jamiil
• setitimer and nanosleep issue., Ryan Knopp
  • Re: setitimer and nanosleep issue., fjblurt
  • Re: setitimer and nanosleep issue., Andrei Voropaev
• Extracting symbol table from libc to make coredumps useful, Johannes Bauer
  • Re: Extracting symbol table from libc to make coredumps useful, fjblurt
    • Re: Extracting symbol table from libc to make coredumps useful, Johannes Bauer
      • Re: Extracting symbol table from libc to make coredumps useful, Paul Pluzhnikov
  • <Possible follow-ups>
  • Extracting symbol table from libc to make coredumps useful, Johannes Bauer
• how to recreate the current process?, Pietro Cerutti
  • Re: how to recreate the current process?, fjblurt
    • Re: how to recreate the current process?, Pietro Cerutti
      • Re: how to recreate the current process?, Lew Pitcher
      • Re: how to recreate the current process?, Henry Townsend
      • Re: how to recreate the current process?, fjblurt
      • Re: how to recreate the current process?, Pietro Cerutti
    • Re: how to recreate the current process?, Rainer Weikusat
    • Re: how to recreate the current process?, Keith Willis
    • Re: how to recreate the current process?, Geoff Clare
• Re: getopt under windows, Henry Townsend
  • Re: getopt under windows, santosh
    • Re: getopt under windows, FrenKy
      • Re: getopt under windows, Scott Lurndal
      • Re: getopt under windows, Giorgos Keramidas
      • Re: getopt under windows, Henry Townsend
      • Re: getopt under windows, Giorgos Keramidas
      • Re: getopt under windows, Henry Townsend
  • Re: getopt under windows, Markus Mayer
• What should happen when a remote session is unceremoniously killed, Adrian
  • Re: What should happen when a remote session is unceremoniously killed, Golden California Girls
    • Re: What should happen when a remote session is unceremoniously killed, Adrian
      • Re: What should happen when a remote session is unceremoniously killed, Golden California Girls
      • Re: What should happen when a remote session is unceremoniously killed, Adrian
      • Re: What should happen when a remote session is unceremoniously killed, Barry Margolin
      • Re: What should happen when a remote session is unceremoniously killed, Logan Shaw
      • Re: What should happen when a remote session is unceremoniously killed, Golden California Girls
      • Re: What should happen when a remote session is unceremoniously killed, Barry Margolin
      • Re: What should happen when a remote session is unceremoniously killed, Golden California Girls
      • Re: What should happen when a remote session is unceremoniously killed, fjblurt
• Using _fini() with dlclose(), Boltar
  • Re: Using _fini() with dlclose(), Casper H . S . Dik
    • Re: Using _fini() with dlclose(), Boltar
      • Re: Using _fini() with dlclose(), Jim Marshall
      • Re: Using _fini() with dlclose(), Boltar
      • Re: Using _fini() with dlclose(), Jim Marshall
      • Re: Using _fini() with dlclose(), fjblurt
• Delete empty lines from a file, shulamitm
  • Re: Delete empty lines from a file, Giorgos Keramidas
  • Re: Delete empty lines from a file, John Gordon
  • Re: Delete empty lines from a file, fjblurt
• Book- Linux System Programming, kmeson
  • Re: Book- Linux System Programming, Darko
• Richard Stevens photo, Darko
  • Re: Richard Stevens photo, santosh
    • Re: Richard Stevens photo, Darko
      • Re: Richard Stevens photo, Logan Shaw
      • Re: Richard Stevens photo, Darko
      • Re: Richard Stevens photo, Gary R. Schmidt
      • Re: Richard Stevens photo, Darko
      • Re: Richard Stevens photo, Barry Margolin
      • Re: Richard Stevens photo, Al Balmer
    • Re: Richard Stevens photo, Golden California Girls
• Hanging popen/fgets/pclose, Henrik Goldman
  • Re: Hanging popen/fgets/pclose, Barry Margolin
    • Re: Hanging popen/fgets/pclose, santosh
      • Re: Hanging popen/fgets/pclose, hg
    • Re: Hanging popen/fgets/pclose, hg
  • Re: Hanging popen/fgets/pclose, Alex Fraser
• st_nlink with shared memory, jombocito
  • Re: st_nlink with shared memory, David Schwartz
    • Re: st_nlink with shared memory, Geoff Clare
      • Re: st_nlink with shared memory, jombocito
      • Re: st_nlink with shared memory, Barry Margolin
• nat-traverse, Larry
• linking against shared libraries (2), noident
  • Re: linking against shared libraries (2), Logan Shaw
    • Re: linking against shared libraries (2), noident
• Debugging core file?, Zach
  • Re: Debugging core file?, Darko
  • Re: Debugging core file?, Sheth Raxit
• How can i list my arguments while pressing tab?, lak
  • Re: How can i list my arguments while pressing tab?, Brian Szmyd
    • Re: How can i list my arguments while pressing tab?, Darko
      • Re: How can i list my arguments while pressing tab?, Brian Szmyd
  • Re: How can i list my arguments while pressing tab?, Chris F.A. Johnson
    • Re: How can i list my arguments while pressing tab?, Darko
  • Re: How can i list my arguments while pressing tab?, William Pursell
• Unix Network Programming Volume 1, Peter
  • Re: Unix Network Programming Volume 1, Nabeel
    • Re: Unix Network Programming Volume 1, Peter
• simple question about using diff, Lawson English
  • Re: simple question about using diff, Eric Sosman
    • Re: simple question about using diff, Lawson English
  • Re: simple question about using diff, Stephane CHAZELAS
    • Re: simple question about using diff, Lawson English
• Re: Signal dispositions, Rainer Weikusat
  • Re: Signal dispositions, Scott Lurndal
    • Re: Signal dispositions, Rainer Weikusat
    • Re: Signal dispositions, David Schwartz
  • <Possible follow-ups>
  • Re: Signal dispositions, Martin Vuille
  • Re: Signal dispositions, Rainer Weikusat
  • Re: Signal dispositions, Rainer Weikusat
  • Re: Signal dispositions, Eric Sosman
  • Re: Signal dispositions, Rainer Weikusat
• Re: Need to know if my application is leaking or not, William Xu
  • Re: Need to know if my application is leaking or not, Spoon
    • Re: Need to know if my application is leaking or not, abd_web
      • Re: Need to know if my application is leaking or not, Jim Marshall
      • Re: Need to know if my application is leaking or not, Andrei Voropaev
      • Re: Need to know if my application is leaking or not, Rainer Weikusat
• Re: errno=0 How to debug/avoid problem.--, Sheth Raxit
• Re: Reclaiming locks, Boudewijn Dijkstra
  • <Possible follow-ups>
  • Re: Reclaiming locks, Boudewijn Dijkstra
• Re: Read Fail -104 -Connection reset by peer., Sheth Raxit
  • Re: Read Fail -104 -Connection reset by peer., David Schwartz
    • Re: Read Fail -104 -Connection reset by peer., Sheth Raxit
      • Re: Read Fail -104 -Connection reset by peer., David Schwartz
  • Re: Read Fail -104 -Connection reset by peer., Andrei Voropaev
• Re: To Change PS1 automatically, meenakshi
  • Re: To Change PS1 automatically, Logan Shaw
    • Re: To Change PS1 automatically, Doug McIntyre
      • Re: To Change PS1 automatically, Logan Shaw
      • Re: To Change PS1 automatically, Stephane CHAZELAS
      • Re: To Change PS1 automatically, Keith Willis
      • Re: To Change PS1 automatically, Stephane CHAZELAS
      • Re: To Change PS1 automatically, Logan Shaw
      • Re: To Change PS1 automatically, lak
      • Re: To Change PS1 automatically, Stephane CHAZELAS
      • Re: To Change PS1 automatically, Darko
  • <Possible follow-ups>
  • Re: To Change PS1 automatically, hsing
  • Re: To Change PS1 automatically, Stephane CHAZELAS
    • Re: To Change PS1 automatically, Stephane CHAZELAS
• how to overcome this difficutly, hai . xu1
  • Re: how to overcome this difficutly, David Schwartz
• Re: weird fork problem, Logan Shaw
  • <Possible follow-ups>
  • Re: weird fork problem, Almond
  • Re: weird fork problem, Andrei Voropaev
• Re: Why localize structures in this case., Logan Shaw
  • Re: Why localize structures in this case., James Antill
  • <Possible follow-ups>
  • Re: Why localize structures in this case., Logan Shaw
    • Re: Why localize structures in this case., Rainer Weikusat

• Security
• UNIX
• Linux
• Coding
• Usenet

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

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