<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Reboot on sigtar.com</title>
		<link>https://sigtar.com/tags/reboot/</link>
		<description>Recent content in Reboot on sigtar.com</description>
		<generator>Hugo</generator>
		<language>en-nz</language>
		
		
		
		
			<lastBuildDate>Thu, 10 Sep 2020 00:00:00 +1200</lastBuildDate>
		
			<atom:link href="https://sigtar.com/tags/reboot/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>emergency reboot a hung Linux host</title>
				<link>https://sigtar.com/2020/09/10/emergency-reboot-a-hung-linux-host/</link>
				<pubDate>Thu, 10 Sep 2020 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2020/09/10/emergency-reboot-a-hung-linux-host/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;https://sigtar.com/wp-content/uploads/Screenshot-Terminal.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Sometimes you need something that can kick a host a bit harder than the standard &lt;strong&gt;reboot&lt;/strong&gt; command. Even if you include the &lt;strong&gt;-f&lt;/strong&gt; switch to force, a hung task can prevent your host from rebooting.&lt;/p&gt;&#xA;&lt;p&gt;Try this - first enable the sysrq setting, then trigger. Your host should reboot immediately.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;sudo echo 1 &amp;gt; /proc/sys/kernel/sysrq&lt;/strong&gt;&lt;br&gt;&#xA;&lt;strong&gt;sudo echo b &amp;gt; /proc/sysrq-trigger&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Note : This is effectively a hard reset which does not cleanly shut services or tasks down. You may need to check your disk on some operating systems.&lt;/p&gt;</description>
			</item>
			<item>
				<title>opensolaris - smbd issues?</title>
				<link>https://sigtar.com/2009/07/27/opensolaris-smbd-issues/</link>
				<pubDate>Mon, 27 Jul 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/07/27/opensolaris-smbd-issues/</guid>
				<description>&lt;p&gt;Hmm&amp;hellip; i&amp;rsquo;ve been having problems since the 2009.06 (snv_111b) update with cifs.&lt;/p&gt;&#xA;&lt;p&gt;Cant pin it exactly as it could be &amp;ldquo;load&amp;rdquo; related&amp;hellip; hmmm.&lt;/p&gt;&#xA;&lt;p&gt;found this ? &lt;a href=&#34;http://opensolaris.org/jive/thread.jspa?threadID=107681&#34;&gt;http://opensolaris.org/jive/thread.jspa?threadID=107681&lt;/a&gt; this also may be a clue.. &lt;a href=&#34;http://opensolaris.org/jive/thread.jspa?threadID=92472&amp;amp;tstart=75&#34;&gt;http://opensolaris.org/jive/thread.jspa?threadID=92472&amp;amp;tstart=75&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;imapd ?  might have to go back to 2008.11&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;You might get better performance if you enable oplocks but there are known issues with it but you can do it just to see if you see any difference:&lt;/p&gt;&#xA;&lt;p&gt;svccfg -s smb/server setprop smbd/oplock_enable=boolean: true&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
			</item>
			<item>
				<title>Linux - crontab</title>
				<link>https://sigtar.com/2009/02/03/linux-crontab/</link>
				<pubDate>Tue, 03 Feb 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/02/03/linux-crontab/</guid>
				<description>&lt;p&gt;Time to schedule some tasks!&lt;/p&gt;&#xA;&lt;p&gt;First you need to make sure your in the &lt;strong&gt;/etc/cron.d/cron.allow&lt;/strong&gt; file. If you are not &lt;strong&gt;SU&lt;/strong&gt; to root and add yourself into it.&lt;/p&gt;&#xA;&lt;p&gt;Now to create your new crontab file;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;crontab -e&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;You are in &lt;strong&gt;vi&lt;/strong&gt; in your newly created crontab file (note if you do not have access to do this it will say so)&lt;/p&gt;&#xA;&lt;p&gt;Now, i&amp;rsquo;m no expert at using &lt;strong&gt;vi&lt;/strong&gt;, but if you press &lt;strong&gt;i&lt;/strong&gt; you will go into insert mode. Do this, then type the cron job details. A typical cron job will look like this&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
