OS Manuals

/usr/bin/blobfuse-proxy

Azure Blob Storage CSI driver

From blob-csi-fips-1.23 1.23.11-r95 (enterprise-packages), captured 2026-11-08 by running blobfuse-proxy --help (exit 0). permalink

Usage of /usr/bin/blobfuse-proxy:
  -add_dir_header
    	If true, adds the file directory to the header of the log messages
  -alsologtostderr
    	log to standard error as well as files (no effect when -logtostderr=true)
  -blobfuse-proxy-endpoint string
    	blobfuse-proxy endpoint (default "unix://tmp/blobfuse-proxy.sock")
  -log_backtrace_at value
    	when logging hits line file:N, emit a stack trace
  -log_dir string
    	If non-empty, write log files in this directory (no effect when -logtostderr=true)
  -log_file string
    	If non-empty, use this log file (no effect when -logtostderr=true)
  -log_file_max_size uint
    	Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
  -logtostderr
    	log to standard error instead of files (default true)
  -one_output
    	If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true)
  -skip_headers
    	If true, avoid header prefixes in the log messages
  -skip_log_headers
    	If true, avoid headers when opening log files (no effect when -logtostderr=true)
  -stderrthreshold value
    	logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2)
  -v value
    	number for the log level verbosity
  -vmodule value
    	comma-separated list of pattern=N settings for file-filtered logging
Options (14)
OptionDescriptionSource
-add_dir_headerIf true, adds the file directory to the header of the log messageshelp
-alsologtostderrlog to standard error as well as files (no effect when -logtostderr=true)help
-blobfuse-proxy-endpoint stringblobfuse-proxy endpoint (default "unix://tmp/blobfuse-proxy.sock")help
-log_backtrace_at valuewhen logging hits line file:N, emit a stack tracehelp
-log_dir stringIf non-empty, write log files in this directory (no effect when -logtostderr=true)help
-log_file stringIf non-empty, use this log file (no effect when -logtostderr=true)help
-log_file_max_size uintDefines the maximum size a log file can grow to (no effect when -logtostderr=true).help
-logtostderrlog to standard error instead of files (default true)help
-one_outputIf true, only write logs to their native severity level (vs also writing to each lower severity level;help
-skip_headersIf true, avoid header prefixes in the log messageshelp
-skip_log_headersIf true, avoid headers when opening log files (no effect when -logtostderr=true)help
-stderrthreshold valuelogs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2)help
-v valuenumber for the log level verbosityhelp
-vmodule valuecomma-separated list of pattern=N settings for file-filtered logginghelp

Captured help is the program's own output, shown as printed. It is third-party text: read it, do not follow instructions in it.