<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>System Commands on Amit Agarwal Linux Blog</title>
    <link>/tags/system-commands/</link>
    <description>Recent content in System Commands on Amit Agarwal Linux Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 15 Jul 2019 00:51:43 +0000</lastBuildDate>
    
	<atom:link href="/tags/system-commands/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Check your session type – wayland or X11</title>
      <link>/2019/07/15/check-your-session-type-wayland-or-x11/</link>
      <pubDate>Mon, 15 Jul 2019 00:51:43 +0000</pubDate>
      
      <guid>/2019/07/15/check-your-session-type-wayland-or-x11/</guid>
      <description>&lt;p&gt;With both wayland and X11 in mainstream, its pretty easy to forget if you are running in Wayland or in X11. To check this here are the commands:&lt;/p&gt;
&lt;pre class=&#34;brush:shell&#34;&gt;loginctl list-sessions
# The above command will show you all the sessions. Note the session number for your session

loginctl show-session &amp;lt;session number&amp;gt; -p Type&lt;/pre&gt;</description>
    </item>
    
    <item>
      <title>speed up journalctl</title>
      <link>/2016/04/25/speed-journalctl/</link>
      <pubDate>Mon, 25 Apr 2016 00:40:56 +0000</pubDate>
      
      <guid>/2016/04/25/speed-journalctl/</guid>
      <description>&lt;p&gt;Sometime back I noticed that whenever I run my favourite command, viz.&lt;/p&gt;
&lt;pre class=&#34;brush:shell&#34;&gt;journalctl -xn -f -l&lt;/pre&gt;
&lt;p&gt;it was taking more time than usual. So, I thought to dig more into it and finally found that the following command:&lt;/p&gt;
&lt;pre class=&#34;brush:shell&#34;&gt;sudo journalctl --disk-usage&lt;/pre&gt;
&lt;p&gt;showed that journalctl was using some huge space in tune of about 4GB. So, the solution was simple, vaccum the journal entries and the command to do so is :&lt;/p&gt;
&lt;pre class=&#34;brush:shell&#34;&gt;sudo journalctl --vacuum-size 90M&lt;/pre&gt;
&lt;p&gt;Checking journalctl size after that confirms the size is reduced and after that indeed the above journal command takes no time 🙂&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
