As the nbcplogs tool exists today, it does address both of your improvements.
1. Allow alternate temporary location
% nbcplogs --tmpdir=/path/to/temp ...your options/arguments here...
OR
% setenv TMPDIR /path/to/temp
% export TMPDIR=/path/to/temp
C:\> set TMPDIR=C:\path\to\temp
% nbcplogs ...your options/arguments here...
The tool looks to the TMPDIR environment variable, but --tmpdir should override all other environment settings. A few people have asked about this and it's probably just not well documented, so spread the word! The --help-long is a really good resource for power users of this tool!
2. FTP operation failure and proxies...
% nbcplogs -f 123-123-123
... failed to upload ...
** upload failed, but bundle remains at /tmp/logs-hostname-.tar.gz
** please ask tech support to create /pub/support/incoming/123-123-123
** then upload it manually
The tool will leave the log bundle on the host in case of failure. On
successful upload, the bundle will be removed.
A current problem with the tool is its lack of good support for proxies. Hopefully in the future, it will support this better. For now, there are options to manipulate the ftp behavior:
--ftp-host=HOSTNAME hostname to upload logs to
--ftp-user=USERNAME username to use for ftp upload
--ftp-pass="PASSWORD" password to use for ftp upload
--ftp-incoming=PATH base directory for incoming uploaded logs
(from --help-long under [common options])
However, if you'd rather just create a log bundle and place it somewhere:
% nbcplogs --bundle --compress /path/to/bundle
The --ftp (or -f) option auto-enables and names the bundle for you. The above is manually doing the work that ftp does automatically and doesnt upload the bundle. This way, you have finer control over how the bundle is created. This can later be uploaded by whatever means you would like.
Hopefully that helps!
Thanks for the feedback!
- Dan