I see your point, however the error code was produced by the program, not PHP.
The error is the program's, not PHP's.
Therefore, the explanation of the error involves the command, not PHP.
Second, you shouldn't assume anything.
The errors that mySQL returns involve mySQL, not PHP. Yes, you can view them in PHP, but they come from mySQL. The same is true with this system command.
The only errors having to do with PHP are the errors that PHP itself generates... the Warning: errors and the Fatal Errors.
sorry to say it, but your assumption is wrong, and your question is in regard to the system command. You want to know what the return code of the system command is.
I found this:
3.6 Key signing
As mentioned before in the introduction there is one major Achilles' heel in the system. This is the authenticity of public keys. If you have a wrong public key you can say bye bye to the value of your encryption. To overcome such risks there is a possibility of signing keys. In that case you place your signature over the key, so that you are absolutely positive that this key is valid. This leads to the situation where the signature acknowledges that the user ID mentioned in the key is actually the owner of that key. With that reassurance you can start encrypting.
Using the gpg --edit-key UID command for the key that needs to be signed you can sign it with the sign command.
You should only sign a key as being authentic when you are ABSOLUTELY SURE that the key is really authentic!!!. So if you are positive you got the key yourself (like on a key signing party) or you got the key through other means and checked it (for instance by phone) using the fingerprint-mechanism. You should never sign a key based on any assumption.
Based on the available signatures and "ownertrusts" GnuPG determines the validity of keys. Ownertrust is a value that the owner of a key uses to determine the level of trust for a certain key. The values are
1 = Don't know
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
If the user does not trust a signature it can say so and thus disregard the signature. Trust information is not stored in the same file as the keys, but in a separate file.
at:
http://webber.dewinter.com/gnupg_howto/english/GPGMiniHowto-3.html
http://linux.ctyme.com/userdoc/gnupg-1.0.6/faq.html#q4.1
I suggest running your command in the command line, and seeing what it says, as the errors are outlined in the second link I posted.
I also found some stuff referring to using this command in a web environment, like you want. You might find something useful.
I'm not sure why you want to use this, but you might take a look at the encryption functions built into PHP.