[ANNOUNCEMENT] Updated: {ghostscript/gs8/gs-devel}-8.62-3 - GPL PostScript interpreter

2008-11-23 Thread Dr. Volker Zell
Hi New versions of 'ghostscript/gs8/gs-devel' have been uploaded to a server near you. DESCRIPTION: GNU Ghostscript is Postscript interpreter capable of converting PS files into a number of printer output formats. Ghostscript can also render PS files into a number of graphics file

Re: "du -b --files0-from=-" running out of memory

2008-11-23 Thread Barry Kelly
Eric Blake wrote: > [adding the upstream coreutils list] > > According to Barry Kelly on 11/23/2008 6:24 AM: > > I have a problem with du running out of memory. > > > > I'm feeding it a list of null-separated file names via standard input, > > to a command-line that looks like: > > > > du -b

Re: Bash process hangs around forever after ssh disconnect

2008-11-23 Thread Michael Hipp
Thorsten Kampe wrote: Screen is /not/ off-topic because it is the solution to your problem. If you are asking for a solution where you cannot use screen because it is not installed or because you forgot to run it before starting a shell then you should say so. Ok then, I want a solution where

Re: Bash process hangs around forever after ssh disconnect

2008-11-23 Thread Thorsten Kampe
* Michael Hipp (Sun, 23 Nov 2008 12:32:54 -0600) > Thorsten Kampe wrote: > > In all likelihood you do NOT want sshd to kill your shell because > > you loose connection for a while. Let me repeat: you do NOT want > > that. > > Really? Should I call Red Hat, SUSE, Debian and Ubuntu and all the > oth

Re: Bash process hangs around forever after ssh disconnect

2008-11-23 Thread Michael Hipp
Thorsten Kampe wrote: That's the Windows/Cygwin emulation of a Unix fork. Should be the same as on Linux. I know that. I was pointing out that sshd goes away as expected but bash does not. Please read again what I wrote and try to understand it. Ok, I have re-read it and don't find anythin

Re: Bash process hangs around forever after ssh disconnect

2008-11-23 Thread Thorsten Kampe
* Michael Hipp (Sun, 23 Nov 2008 10:11:59 -0600) > Thorsten Kampe wrote: > > * Michael Hipp (Sat, 22 Nov 2008 13:49:33 -0600) > >> I'm logging in to a W2k server via cygwin sshd and using Putty as my > >> terminal emulator. If my ssh connection gets dropped for any reason > >> the bash.exe process

Re: Bash process hangs around forever after ssh disconnect

2008-11-23 Thread Michael Hipp
Thorsten Kampe wrote: * Michael Hipp (Sat, 22 Nov 2008 13:49:33 -0600) I'm logging in to a W2k server via cygwin sshd and using Putty as my terminal emulator. If my ssh connection gets dropped for any reason the bash.exe process on the host just stays there forever. Also, anything I was running

Re: Bash process hangs around forever after ssh disconnect

2008-11-23 Thread Thorsten Kampe
* Michael Hipp (Sat, 22 Nov 2008 13:49:33 -0600) > I'm logging in to a W2k server via cygwin sshd and using Putty as my > terminal emulator. If my ssh connection gets dropped for any reason > the bash.exe process on the host just stays there forever. Also, > anything I was running in bash (e.g. vim

Re: "du -b --files0-from=-" running out of memory

2008-11-23 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [adding the upstream coreutils list] According to Barry Kelly on 11/23/2008 6:24 AM: > I have a problem with du running out of memory. > > I'm feeding it a list of null-separated file names via standard input, > to a command-line that looks like: >

"du -b --files0-from=-" running out of memory

2008-11-23 Thread Barry Kelly
I have a problem with du running out of memory. I'm feeding it a list of null-separated file names via standard input, to a command-line that looks like: du -b --files0-from=- The problem is that when du is run in this way, it leaks memory like a sieve. I feed it about 4.7 million paths but ev

Re: pthread_t

2008-11-23 Thread John Emmas
- Original Message - From: "John Emmas" Sent: 23 November 2008 12:12 Subject: Re: pthread_t this turned out to be due to the fact that the program is expecting 'pthread_t' and 'pthread_key_t' to be equivalent. Oops - I gave you duff information. in fact, the program had (wrongly)

Re: Git corrupts repository

2008-11-23 Thread Spiro Trikaliotis
Hello, * On Sat, Nov 22, 2008 at 01:17:07PM +0100 Kovarththanan Rajaratnam wrote: > I've run into a similar issue as described in [1]. No matter which > repository I try to clone, I end up with a corrupt repository. According > to [1] it should be sufficient to put the git repository onto a b

Re: pthread_t

2008-11-23 Thread John Emmas
- Original Message - From: "Vaclav Haisman" Sent: 23 November 2008 11:05 Subject: Re: pthread_t The program is wrong. The pthread_t type is opaque. You should not expect anything. [...] The only header that you should use to get pthread_t type is pthread.h. Thanks Vaclav, you're abs

Re: pthread_t

2008-11-23 Thread Vaclav Haisman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 John Emmas wrote: > I'm trying to compile a program in which pthread_t is expected to be > > typedef long unsigned int pthread_t; The program is wrong. The pthread_t type is opaque. You should not expect anything. > > the program builds fine under

pthread_t

2008-11-23 Thread John Emmas
I'm trying to compile a program in which pthread_t is expected to be typedef long unsigned int pthread_t; the program builds fine under Linux but when I try to compile under Cygwin I see this error:- conflicting declaration 'typedef long unsigned int pthread_t' pthread_t has a previous de