<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 9/29/2013 4:17 AM, Leszek Lesner
wrote:<br>
</div>
<blockquote cite="mid:20130929081732.5202064.10793.2759@web.de"
type="cite">
<div style="width: 100%; font-size: initial; font-family: Calibri,
'Slate Pro', sans-serif; color: rgb(31, 73, 125); text-align:
initial; background-color: rgb(255, 255, 255);">It can be
disabled just like any other upstart service. </div>
<div style="width: 100%; font-size: initial; font-family: Calibri,
'Slate Pro', sans-serif; color: rgb(31, 73, 125); text-align:
initial; background-color: rgb(255, 255, 255);">Here is a short
documentation link:
<a class="moz-txt-link-freetext" href="http://upstart.ubuntu.com/cookbook/#disabling-a-job-from-automatically-starting">http://upstart.ubuntu.com/cookbook/#disabling-a-job-from-automatically-starting</a></div>
<div style="width: 100%; font-size: initial; font-family: Calibri,
'Slate Pro', sans-serif; color: rgb(31, 73, 125); text-align:
initial; background-color: rgb(255, 255, 255);"><br>
</div>
<div style="width: 100%; font-size: initial; font-family: Calibri,
'Slate Pro', sans-serif; color: rgb(31, 73, 125); text-align:
initial; background-color: rgb(255, 255, 255);">So renaming
/etc/init/zram-config.conf to /etc/init/zram-config.donotstart
should work here.</div>
</blockquote>
<br>
Thanks, Leszek, this was the cleanest work-around. Disabling the
Upstart job means that the zram configurations never run to begin
with. <br>
<br>
And it doesn't leave anything dubious dangling (like the 'sudo
parted -l' output of 'Error: /dev/zram1: unrecognised disk label').<br>
<br>
<blockquote cite="mid:20130929081732.5202064.10793.2759@web.de"
type="cite">
<div style="width: 100%; font-size: initial; font-family: Calibri,
'Slate Pro', sans-serif; color: rgb(31, 73, 125); text-align:
initial; background-color: rgb(255, 255, 255);"><br
style="display:initial">
</div>
<table style="background-color:white;border-spacing:0px;"
width="100%">
<tbody>
<tr>
<td colspan="2" style="font-size: initial; text-align:
initial; background-color: rgb(255, 255, 255);">
<div id="_persistentHeader" style="border-style: solid
none none; border-top-color: rgb(181, 196, 223);
border-top-width: 1pt; padding: 3pt 0in 0in;
font-family: Tahoma, 'BB Alpha Sans', 'Slate Pro';
font-size: 10pt;">
<div><b>Von: </b>Nio Wiklund</div>
<div><b>Gesendet: </b>Sonntag, 29. September 2013 10:11</div>
<div><b>An: </b>Leszek Lesner; John Hupp;
<a class="moz-txt-link-abbreviated" href="mailto:lubuntu-users@lists.ubuntu.com">lubuntu-users@lists.ubuntu.com</a></div>
<div><b>Betreff: </b>Re: AW: zRAM broken on Raring?</div>
</div>
</td>
</tr>
</tbody>
</table>
<br>
<div id="_originalContent" style="">Hi Leszek,<br>
<br>
John has zRAM in Raring. It was pulled in by a package he
installed, and<br>
I try to help him switch it off.<br>
<br>
Probably it is better to do it in /etc/init.d, but I am not
familiar<br>
with that method, so I didn't suggest that method. Please
describe it,<br>
I'm reading and learning :-)<br>
<br>
Best regards<br>
Nio<br>
<br>
On 2013-09-29 10:03, Leszek Lesner wrote:<br>
> Honestlky I don't get the cronjob. Why is it necessary? On
reboot the<br>
> init system runs the stop command on zram-config in
/etc/init.d which<br>
> dies exactly the same as the cronjob here.<br>
> <br>
> *Von: *Nio Wiklund<br>
> *Gesendet: *Sonntag, 29. September 2013 08:29<br>
> *An: *John Hupp; <a class="moz-txt-link-abbreviated" href="mailto:lubuntu-users@lists.ubuntu.com">lubuntu-users@lists.ubuntu.com</a><br>
> *Betreff: *Re: zRAM broken on Raring?<br>
> <br>
> <br>
> On 2013-09-29 02:23, John Hupp wrote:<br>
>> On 9/28/2013 12:23 PM, sudodus wrote:<br>
>>> Hi John,<br>
>>><br>
>>> Yes, let us hope the bug will be fixed soon, and it
will be<br>
>>> back-ported :-)<br>
>>><br>
>>> Can you run your application without zRAM? You can
switch it off in a<br>
>>> simple way (and have it ready for reactivation)
like this with crontab.<br>
>>> Edit the crontab with<br>
>>><br>
>>> sudo crontab -e<br>
>>><br>
>>> $ sudo crontab -l |tail -n3<br>
>>> # m h dom mon dow command<br>
>>> @reboot /sbin/swapoff /dev/zram*<br>
>>> @reboot /sbin/rmmod zram<br>
>>><br>
>>> Best regards<br>
>>> Nio<br>
>><br>
>> I set up a root crontab as you suggested, Nio, and
syslog confirms that<br>
>> the two crontab commands are run after the zram setup
commands.<br>
>><br>
>> But sudo parted -l still reports:<br>
>> Error: /dev/zram1: unrecognised disk label<br>
>><br>
>> Does anyone know if the zram1 device would be using
memory (the setup<br>
>> command designated 512MB for zram on this 1GB setup) or
otherwise doing<br>
>> any harm?<br>
> <br>
> Hi John,<br>
> <br>
> The zRAM is not removed, only de-activated. Only if zRAM is
used already<br>
> '@reboot', when cron runs the command, and there is no
place to put the<br>
> content, then swapoff would fail (I think).<br>
> <br>
> 1. Did you check with<br>
> <br>
> swapon -s<br>
> <br>
> This command should return no zram block device.<br>
> <br>
> 2. Check the memory with<br>
> <br>
> free -m<br>
> <br>
> and install and run<br>
> <br>
> htop<br>
> <br>
> to check if something related to zram is running or using
memory.<br>
> <br>
> Best regards<br>
> Nio<br>
> <br>
> -- <br>
> Lubuntu-users mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Lubuntu-users@lists.ubuntu.com">Lubuntu-users@lists.ubuntu.com</a><br>
> Modify settings or unsubscribe at:<br>
> <a class="moz-txt-link-freetext" href="https://lists.ubuntu.com/mailman/listinfo/lubuntu-users">https://lists.ubuntu.com/mailman/listinfo/lubuntu-users</a><br>
<br>
</div>
</blockquote>
<br>
</body>
</html>