Description of problem: the -p option is not properly defined in the opts section fo the handle_command_mode definition. Needs to include p to be successful Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
p is actually in the list, my mistake, however the behavior does still exist. If I find a solution I'll post
Was able to get around the issue by having -s first in the args list and then using -p
Created attachment 313204 [details] patch to change how keys are set in command mode Thanks for the report, I think I need to use putenv instead of environ there. Can you try this patch and see how it works? Thanks!
hrmm, didn't seem to fix it. Still get weird -p error [csellers@dspacetrial1 dspace-trial]$ sudo -u dspace /usr/bin/s3fs dspace-trial /usr/local/dpsace-trial -p 0WPRTZ6ENM9S7FGP5AR2 -s W/xUbTcUUtbp4APCwwMaeQK3TZ/UD4PgalaTeFWM audit_log_user_command(): Connection refused Usage: s3fs [mountpoint] [options] s3fs: error: no such option: -p Also -p is missing from the usage line too (./s3fs [<-C> [-hcdrfk]] [<bucket> <mountpoint>]) It's very strange behavior. Linux dspacetrial1.nitle.org 2.6.16-xenU #1 SMP Mon May 28 03:41:49 SAST 2007 i686 athlon i386 GNU/Linux
Ah, I see your problem, you're trying to use s3fs in mount mode, rather than in command mode (in command mode you need to specify -C as the first option). When in mount mode you specify options like you do when you use the mount utility (-o option=value,option=value). Try running like this: sudo -u dspace /usr/bin/s3fs -o AWS_ACCESS_KEY_ID=<pubkey>,AWS_SECRET_ACCESS_KEY=<seckey> dspace-trial /usr/local/dpsace-trial I've updated the binary in my git tree upstream to reflect the addional parameters that are missing from the usage/help output. Thanks!
I was successful before using the ENV vars, so I'm glad things worked out. Thanks and good work. Bug resolved.
cool. Thanks!