Hello,
On Fri, Jul 13, 2018 at 12:29:56PM +0200, Nicolas George wrote:
> Adam Weremczuk (2018-07-13):
> > What's the safest and quickest way to temporarily triple the size of /run ?
>
> Do not.
>
> Instead, change your program to put its tons of data somewhere else,
> preferably in a directory t
Curt (2018-07-13):
> Why not (not a rhetorical question)?
Because requiring unusual system configuration for user programs is not
convenient in the long run.
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
On 2018-07-13, Nicolas George wrote:
>
> Adam Weremczuk (2018-07-13):
>> What's the safest and quickest way to temporarily triple the size of /run=
> ?
>
> Do not.
Why not (not a rhetorical question)?
man logind.conf
RuntimeDirectorySize=
Sets the size limit on the $XDG_RUNTIME_DIR runti
Thank you both for useful advice.
For me the AIDE script is a bit too complex (700+ lines) to quickly
analyse and experiment with.
I've decided to take a lazy path which is simply increasing the size of
/run and retrying AIDE job.
No problem if it buzzes in the background for a couple of day
Adam Weremczuk (2018-07-13):
> What's the safest and quickest way to temporarily triple the size of /run ?
Do not.
Instead, change your program to put its tons of data somewhere else,
preferably in a directory that can easily be configured.
Also, change it to set up checkpoints so that you can r
On 13.07.2018 11:56, Adam Weremczuk wrote:
> I have no entry for /run in /etc/fstab so decided to look into
> /usr/share/initramfs-tools/init
> To my surprise the line was showing 20%, not 10%:
>
> mount -t tmpfs -o "nosuid,size=20%,mode=0755" tmpfs /run
> I've changed it to 60% (hoping to tripl
Hi all,
I have a one off big job (full AIDE report on millions of files) which
I'm trying to run on old Debian 7.1.
The system uses 2 physical disks and physical volumes, no LVM.
It has 8GB or RAM and 32GB of swap which appears to be just enough.
After running for a couple of days the job faile
7 matches
Mail list logo
