<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Linux - Tag - 栗悟饭のspace</title>
        <link>https://blog.zayx.me/tags/linux/</link>
        <description>Linux - Tag - 栗悟饭のspace</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 01 Nov 2024 00:40:03 &#43;0800</lastBuildDate><atom:link href="https://blog.zayx.me/tags/linux/" rel="self" type="application/rss+xml" /><item>
    <title>Solution to cuda driver failure after kernel update</title>
    <link>https://blog.zayx.me/2024/11/01/solution-to-cuda-driver-failure-after-kernel-update/</link>
    <pubDate>Fri, 01 Nov 2024 00:40:03 &#43;0800</pubDate>
    <author>xxxx</author>
    <guid>https://blog.zayx.me/2024/11/01/solution-to-cuda-driver-failure-after-kernel-update/</guid>
    <description><![CDATA[<p>after a recent kernel update (presumably automatic via unattended-upgrades), cuda functionality on my server ceased functioning.  the primary symptom was the following error when running <code>nvidia-smi</code>:</p>
<div class="code-block code-line-numbers open" style="counter-reset: code-block 0">
    <div class="code-header language-bash">
        <span class="code-title"><i class="arrow fas fa-chevron-right fa-fw" aria-hidden="true"></i></span>
        <span class="ellipses"><i class="fas fa-ellipsis-h fa-fw" aria-hidden="true"></i></span>
        <span class="copy" title="Copy to clipboard"><i class="far fa-copy fa-fw" aria-hidden="true"></i></span>
    </div><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">NVIDIA-SMI has failed because it couldn‘t communicate with the NVIDIA driver ...</span></span></code></pre></div></div><p>this indicates a mismatch between the installed nvidia driver and the current kernel version.  the solution involves using <code>dkms</code> (Dynamic Kernel Module Support) to rebuild the nvidia driver against the new kernel.</p>]]></description>
</item>
<item>
    <title>managing frp with systemd: a best-practice approach</title>
    <link>https://blog.zayx.me/2024/10/31/managing-frp-with-systemd-a-best-practice-approach/</link>
    <pubDate>Thu, 31 Oct 2024 22:15:39 &#43;0800</pubDate>
    <author>xxxx</author>
    <guid>https://blog.zayx.me/2024/10/31/managing-frp-with-systemd-a-best-practice-approach/</guid>
    <description><![CDATA[<p>frp is a fantastic tool for intranet penetration, but managing it effectively can be a challenge.  systemd provides a robust and elegant solution for automating frp&rsquo;s startup and ensuring its resilience.  this post will guide you through creating a best-practice systemd unit file for frp, focusing on clarity, efficiency, and robustness.</p>
<p>here&rsquo;s the optimized unit file:</p>
<div class="code-block code-line-numbers open" style="counter-reset: code-block 0">
    <div class="code-header language-bash">
        <span class="code-title"><i class="arrow fas fa-chevron-right fa-fw" aria-hidden="true"></i></span>
        <span class="ellipses"><i class="fas fa-ellipsis-h fa-fw" aria-hidden="true"></i></span>
        <span class="copy" title="Copy to clipboard"><i class="far fa-copy fa-fw" aria-hidden="true"></i></span>
    </div><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-service" data-lang="service"><span class="line"><span class="cl"><span class="k">[Unit]</span>
</span></span><span class="line"><span class="cl"><span class="na">Description</span><span class="o">=</span><span class="s">frp server</span>
</span></span><span class="line"><span class="cl"><span class="na">Requires</span><span class="o">=</span><span class="s">network-online.target</span>
</span></span><span class="line"><span class="cl"><span class="na">After</span><span class="o">=</span><span class="s">network-online.target</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="k">[Service]</span>
</span></span><span class="line"><span class="cl"><span class="na">ExecStart</span><span class="o">=</span><span class="s">/usr/bin/frpc -c /path/to/your/frpc.ini</span>
</span></span><span class="line"><span class="cl"><span class="na">Restart</span><span class="o">=</span><span class="s">on-failure</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="k">[Install]</span>
</span></span><span class="line"><span class="cl"><span class="na">WantedBy</span><span class="o">=</span><span class="s">multi-user.target</span></span></span></code></pre></div></div><p>let&rsquo;s break down the key components:</p>]]></description>
</item>
</channel>
</rss>
