On 16/08/2009 Jan Engelhardt wrote: > "Users of libpam-mount regularly get confused when PAM is set > to no-debug-output (which is the default), but cryptsetup > spews this line. Commands that ran successful should not > print to stderr, because that would indicate a warning, and > "command successful" definitely is not a warning." > > The patch is against tr...@83.
hello, unfortunately this is not an option at all. scripts might rely on the current output behaviour and simply removing the output to STDERR would break scripts and backwards compability in general. only option i see so far is to add a commandline option that causes cryptsetup to suppress the success message to stderr. greetings, jonas
signature.asc
Description: Digital signature
