Timeline for viewing printf after pipe (or subshell?)
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 3, 2015 at 8:01 | history | edited | basin | CC BY-SA 3.0 | added 51 characters in body |
| Jul 3, 2015 at 7:54 | comment | added | basin | read prompt failed and the loop was never entered | |
| Jul 3, 2015 at 7:53 | comment | added | basin | @RobF Your debug printf didn't work, because mount prints its prompt to the terminal, not stdout | |
| Jul 3, 2015 at 7:22 | comment | added | Rob F | The original question was mainly about why the debug printf's that were commented out weren't showing in the console. As to the password file; it seems a password supplied through PASSWD_FILE (with the proper formatting, I didn't make that mistake), PASSWD, the password= parameter in the options; all get ignored and I get prompted for the password anyway!? I can also enter any garbage as the credentials file and it won't show an error.I might want to look into this as a separate problem if you don't know the answer... | |
| Jul 3, 2015 at 6:20 | comment | added | basin | @RobF You can try to supply a fake password file | |
| Jul 2, 2015 at 22:46 | comment | added | Rob F | As far as I can see a password file is itself a security liability. I want it so that an actual human has to type in the password (and only once, despite there being three prompts) | |
| Jul 2, 2015 at 18:59 | history | edited | basin | CC BY-SA 3.0 | added 97 characters in body |
| Jul 2, 2015 at 18:53 | history | answered | basin | CC BY-SA 3.0 |