Re: Testing the exit status

2009-10-13 Thread Werner Koch
On Mon, 12 Oct 2009 17:46, david.g...@turpin-distribution.com said: Thanks for the info. I'm still not clear on how to use the argument status-fd 2 Writing to a file descriptor is basic technique on almost all systems. You may want to consult the APUE [1] to see how it works. I originally

Re: Testing the exit status

2009-10-12 Thread Werner Koch
On Mon, 12 Oct 2009 11:29, david.g...@turpin-distribution.com said: Can you tell me what the numeric arguments are for status-fd? That is the file descriptor obn which output should happen. Usualy you woul use --status-fd 2 to output to stderr; however how can use arbitrary file

RE: Testing the exit status

2009-10-12 Thread David Gray
v2. Contacted the auther who is looking at an upgrade. Regards David -Original Message- From: Werner Koch [mailto:w...@gnupg.org] Sent: 12 October 2009 11:00 To: David Gray Cc: gnupg-users@gnupg.org Subject: Re: Testing the exit status On Mon, 12 Oct 2009 11:29, david.g...@turpin

Re: Testing the exit status

2009-10-10 Thread Werner Koch
On Fri, 9 Oct 2009 13:47, david.g...@turpin-distribution.com said: Does GPG return different status codes when it exits? I'm specifically looking for different types of error, such as file not found, key not found, invalid passphrase etc. This would not be reliable. There are just too

Testing the exit status

2009-10-09 Thread David Gray
Hi, Does GPG return different status codes when it exits? I'm specifically looking for different types of error, such as file not found, key not found, invalid passphrase etc. I'm using the Windows version if that makes any difference. Rgds Dave Registered Office: Turpin Distribution