How to automatically stop systemd-journald?

[huntrm]

I noticed on my pogoplug V2 that systemd-journald takes up significant amount of memory. In my research, it appears that one can't disable the service but you can either optimize or stop it. Optimizing doesn't do much as it still occupies significant memory.

What is a mechansim that I can put in place that will run:

$this->bbcode_second_pass_code('', 'systemctl stop systemd-journald')

30-seconds after the system rebooted successfully?

I don't need the logging hence the request, and would like the memory footprint back. I need some handholding on this as I'm not familiar with how to stop a service after it has been rebooted via an automatic script.

Thank you.

[winestock]

It appears that systemd-journald can't be stopped as it automatically restarts. That is what I have found on my Pogoplug V4 running 3.10.10-2. How much memory do you see systemd-journald using? On my system, journald is using about 4MB or RAM. If I set "Storage=none" in /etc/systemd/journald.conf and restart journald, the memory usage drops to about 1MB.

[huntrm]

Thought I'd let you know that upon reboot, the pogo would work fine for 2-3 minutes. Then it would lock up under console and apparently would flood my home network with packets. Not sure why this is happening, but I was able to log in after rebooting (before the flood of packets occurred), and changed the setting back to auto.

Any ideas on why this would happen? Fairly certain that this was the cause and not some other runaway process.