Timeline for How to detect if mount point exists from init.d script?
Current License: CC BY-SA 3.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
S Nov 7, 2016 at 5:39 | history | edited | Alexis Wilke | CC BY-SA 3.0 |
Fixed timeout code to work.
|
S Nov 7, 2016 at 5:39 | history | suggested | Efren | CC BY-SA 3.0 |
Fixed timeout code to work.
|
Nov 7, 2016 at 4:03 | review | Suggested edits | |||
S Nov 7, 2016 at 5:39 | |||||
Nov 4, 2016 at 17:00 | history | edited | Alexis Wilke | CC BY-SA 3.0 |
Fixed the mountpoint path. Added a paragraph about systemd.
|
Oct 21, 2016 at 19:30 | history | edited | Alexis Wilke | CC BY-SA 3.0 |
Fixed the last paragraph, added example with mountpoint.
|
Nov 4, 2013 at 5:54 | comment | added | fukawi2 |
Also, instead of using test -f you could use mountpoint -q to ensure the mountpoint is actually mounted, and that file hasn't somehow appears on the local filesystem.
|
|
Nov 4, 2013 at 4:39 | history | edited | Alexis Wilke | CC BY-SA 3.0 |
Added another example with a count to timeout
|
Nov 3, 2013 at 19:38 | comment | added | Marki | @fredrik: Count to thirty and stop when 30 has been reached. | |
Nov 3, 2013 at 18:55 | vote | accept | fredrik | ||
Nov 3, 2013 at 18:49 | comment | added | fredrik | @Alexis-Wilke This is almost perfect. How can I throw an error/timeout after say 30 retries? | |
Nov 3, 2013 at 14:29 | comment | added | Marki | Absolutely right. Although I would add a timeout at some point that throws an error. | |
Nov 3, 2013 at 10:18 | history | answered | Alexis Wilke | CC BY-SA 3.0 |