rootdir
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
rootdir [2022/02/11 16:06] yves [Integrity check] |
rootdir [2022/08/10 15:07] (current) yves |
||
|---|---|---|---|
| Line 34: | Line 34: | ||
| ==== Configuration ==== | ==== Configuration ==== | ||
| + | |||
| + | **Root directories management** | ||
| + | |||
| + | Root directories can be managed by selecting the "Root directories" option under the "Settings" section in the left menu. | ||
| + | |||
| + | {{ :roots.png?nolink&400 |}} | ||
| + | |||
| + | The list displays all the configured root directories and provides options to add new, edit and delete entries. | ||
| + | |||
| + | * The "Offline" column indicates whether or not a root directory is enabled. An offline root directory is not advertised by the system and its contents are not available to the end-users. | ||
| + | * The "Path exists" column indicates whether or not the system is able to mount a root directory's path and access it's contents. For example a root directory that points to a local file system folder, that has been deleted, will not have the "Path exists" column checked. | ||
| We have a [[rootdir_config|separate section]] in this wiki that takes you through the different steps that you can take to [[rootdir_config|configure root directories and mounting points]]. | We have a [[rootdir_config|separate section]] in this wiki that takes you through the different steps that you can take to [[rootdir_config|configure root directories and mounting points]]. | ||
| - | We also talk about the security precautions that you can take when configuring these. | + | Root-directories can be labeled public or private, which allow you to [[rootdir_security#public_vs_private|take security precautions when configuring these]]. |
| ==== Security ==== | ==== Security ==== | ||
| Line 69: | Line 80: | ||
| {{ :rootdir_activity.png?direct&400 |}} | {{ :rootdir_activity.png?direct&400 |}} | ||
| - | === Elmah log === | ||
| - | |||
| - | [[https://elmah.github.io/|Elmah error logs]] are a standard way of capturing runtime errors in software. While these logs are not specific to root directories, they can help troubleshoot intermittent problems. Examples include: | ||
| - | * connection information is (temporarily) no longer correct | ||
| - | * a file format may have been modified by its vendor and now no longer renders correctly | ||
| - | |||
| - | {{ ::rootdir_elmah.png?direct&400 |}} | ||
| ==== Integrity check ==== | ==== Integrity check ==== | ||
| - | Elmah logs work great for ad-hoc troubleshooting, but when problems persist over time, a more structured and proactive approach is warranted. | + | When problems persist over time, a structured and proactive approach is warranted. |
| When you suspect certain slides in a particular root directory are corrupt, you can run an integrity check on a particular folder: | When you suspect certain slides in a particular root directory are corrupt, you can run an integrity check on a particular folder: | ||
| + | {{ :rootdir_integrity.png?direct&400 |}} | ||
| This attempts to read all slides in a folder and reports on the ones that fail. You should then [[format_troubleshoot|try to find out why such slides cannot be read]]. | This attempts to read all slides in a folder and reports on the ones that fail. You should then [[format_troubleshoot|try to find out why such slides cannot be read]]. | ||
| + | |||
| + | For problems that only occur occasionally and don't appear to be persistent, [[diag_elmah|Elmah logs]] are available to assist in for ad-hoc troubleshooting. | ||
rootdir.1644584782.txt.gz · Last modified: 2022/02/11 16:06 by yves
