<div dir="ltr">I thought that was a good idea!<div><br></div><div><div>bmike1@c521 ~ $ sudo crontab -u bmike1 -l</div><div>no crontab for bmike1</div><div>bmike1@c521 ~ $ sudo crontab -u root -l</div><div>no crontab for root</div><div>bmike1@c521 ~ $ </div></div><div><br></div><div>But not in my case. Unless of course there is another user it is run under.</div><div>So the mouse wheel in my mind started to creak..... So I inspected the man for crontab.... which inspired me to cat /etc/cron*.... </div><div>which lead me down the path to ls /etc/cron.daily/ </div><div>and in that directory is a file! /etc/cron.daily/apt/</div><div><br></div><div>So How to edit the file? Ask PLUG or ask the web? I opted to ask the web. It told me: <span style="color:rgb(0,0,0);font-family:verdana,geneva,lucida,'lucida grande',arial,helvetica,sans-serif;font-size:13.3333px;background-color:rgb(253,253,253)">edit crontab with crontab -e</span></div><div class="gmail_extra">So I tried:</div><div class="gmail_extra">bmike1@c521 /etc/cron.daily $ crontab -e /etc/cron.daily/apt<br></div><div class="gmail_extra"><div class="gmail_extra">bmike1@c521 /etc/cron.daily $ crontab /etc/cron.daily/apt -e<br></div><div class="gmail_extra">bmike1@c521 /etc/cron.daily $ sudo crontab /etc/cron.daily/apt -e<br></div><div class="gmail_extra">and<br></div><div class="gmail_extra">bmike1@c521 /etc/cron.daily $ sudo crontab -u bmike1 /etc/cron.daily/apt/ -e<br></div><div class="gmail_extra">all of which responded with:</div><div class="gmail_extra">crontab: usage error: no arguments permitted after this option</div><div class="gmail_extra">usage:<span class="" style="white-space:pre"> </span>crontab [-u user] file</div><div class="gmail_extra"><span class="" style="white-space:pre"> </span>crontab [ -u user ] [ -i ] { -e | -l | -r }</div><div class="gmail_extra"><span class="" style="white-space:pre"> </span>(default operation is replace, per 1003.2)</div><div class="gmail_extra"><span class="" style="white-space:pre"> </span>-e<span class="" style="white-space:pre"> </span>(edit user's crontab)</div><div class="gmail_extra"><span class="" style="white-space:pre"> </span>-l<span class="" style="white-space:pre"> </span>(list user's crontab)</div><div class="gmail_extra"><span class="" style="white-space:pre"> </span>-r<span class="" style="white-space:pre"> </span>(delete user's crontab)</div><div class="gmail_extra"><span class="" style="white-space:pre"> </span>-i<span class="" style="white-space:pre"> </span>(prompt before deleting user's crontab)</div><div class="gmail_extra">bmike1@c521 /etc/cron.daily $ </div><div>so I looked a little more in the web and so tried:</div><div>sudo <b style="color:rgb(0,0,0);font-family:Monaco,Courier,'Courier New',monospace;font-size:12px">crontab -e</b><span style="color:rgb(0,0,0);font-family:Monaco,Courier,'Courier New',monospace;font-size:12px;background-color:rgb(239,239,239)"> bmike1</span></div><div class="gmail_quote">which gave the same error.</div><div class="gmail_quote">So now I need to ask what I'm doing wrong.</div><div class="gmail_quote"><br></div><div class="gmail_quote"><br></div><div class="gmail_quote">On Mon, Sep 21, 2015 at 9:19 PM, Michael Butash <span dir="ltr"><<a href="mailto:michael@butash.net" target="_blank">michael@butash.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I've noticed on lower-end systems, that daily cron will peg a system for a bit while that occurs. I had an ancient imac with ubuntu installed that the apt update would hang the system for like a half-hour with an old 400mhz ppc proc, consuming all cpu and memory, then swap and thus disks too. I finally just disabled it, and shortly thereafter retired the outdated system itself that it obviously had outlived its usefulness vs. power drawn.<br>
<br>
You likely have the same issue, just when using it, the update will slam the system. Might be better off doing it manually, or setting the update time for the cronjob to overnight when not using it.<span><font color="#888888"><br>
<br>
-mb</font></span><span><br>
<br>
<br>
On 09/19/2015 09:25 AM, Michael Havens wrote:<br>
</span><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
the problem seems to have been checkapt.py . I tried to figure out what it does and it seems that it locks a database (apt's?). But it couldn't of been apt's as I wasn't running apt. Then I ran top again and it seemed to have corrected itself after 10 or fifteen minutes. Am I correct in what I think it does? Is it safe to kill if this happens again?<br>
</blockquote>
<br></span><div><div>
---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" rel="noreferrer" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><div><div dir="ltr"><div><span style="font-size:12.8px">:-)~MIKE~(-:</span><br></div></div></div></div></div>
</div></div>