
\begin{DoxyItemize}
\item infos = Information about the noresolver plugin is in keys below
\item infos/author = Markus Raab \href{mailto:elektra@libelektra.org}{\texttt{ elektra@libelektra.\+org}}
\item infos/licence = BSD
\item infos/provides = resolver
\item infos/needs =
\item infos/placements = rollback getresolver setresolver commit
\item infos/status = maintained nodep libc configurable discouraged
\item infos/description = resolver dummy that always succeeds
\end{DoxyItemize}\hypertarget{md_src_plugins_noresolver_README_src_plugins_noresolver_README_md}{}\doxysection{Introduction}\label{md_src_plugins_noresolver_README_src_plugins_noresolver_README_md}
{\ttfamily noresolver} is designed for non-\/file-\/based storage plugins like \mbox{\hyperlink{md_src_plugins_uname_README_src_plugins_uname_README_md}{uname}}. It is a trivial resolver that\+:


\begin{DoxyItemize}
\item does not resolve file names but forwards them as given to the storage plugin
\item does not provide any consistency guarantees but storage plugins directly write to the config files
\end{DoxyItemize}\hypertarget{md_src_plugins_noresolver_README_autotoc_md387}{}\doxysection{Explanation}\label{md_src_plugins_noresolver_README_autotoc_md387}
Returns success on every call and can be used as resolver.

It also exports a function checks if a filename is valid. It returns 1 for a relative path and 0 for an absolute path (always successfully).

The path passed to the storage plugin via the parent key is exactly the value that was set during mounting. This plugin {\itshape does not} resolve any paths. If a relative path was set while mounting, storage plugins may treat it as relative to the current working directory. 