<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Hi John,<br>
<br>
<div class="moz-cite-prefix">On Wed 02/12/20 23:33, John Thurston
via ZendTo wrote:<br>
</div>
<blockquote type="cite"
cite="mid:WM!a3784f0a996fe1e59a55f8fbbd7e2ede230925f9d1367c060f2a873e374deaabbf97f713f8d85582b646c183bf9f37da!@mx.jul.es">a'yep,
that job is there, and running the 'find' command interactively
returns appropriate files.
<br>
<br>
I don't recall how old the files were the last time my disk-full
alarm went off and I shoveled it out. It is possible that job was
just about to trigger and I was premature. It is likely that our
increased use of this tool is simply over-running my small disks.
<br>
</blockquote>
That's quite possible. Just about every ZendTo installation I have
seen has an ever-increasing disk space requirement. On my own
installation here at Southampton, I have recently had to up the max
drop-off size to 100GB (we have a non-clinical team who do MRI scans
of tiny objects, and create data like it's going out of fashion).
And after adding the 4th TB of disk space, we've had to reduce the
default lifetime from 32 days to 22 days, just to try to limit its
hunger for space!<br>
<br>
<blockquote type="cite"
cite="mid:WM!a3784f0a996fe1e59a55f8fbbd7e2ede230925f9d1367c060f2a873e374deaabbf97f713f8d85582b646c183bf9f37da!@mx.jul.es"><br>
I have two more questions:
<br>
<br>
1) I see a reference in the preferences:
<br>
<br>
// This is where your drop-offs are stored.
<br>
// It must be on the same filesystem as /var/zendto/incoming,
and
<br>
// on preferably on the same filesystem as /var/zendto.
<br>
'dropboxDirectory' => NSSDROPBOX_DATA_DIR."dropoffs",
<br>
<br>
Why the "same filesystem" requirement for 'incoming' and
'dropoffs'?
<br>
</blockquote>
Because it basically does a "mv" from the incoming directory to the
dropoffs directory.<br>
If they are on the same filesystem, that is an instant atomic
operation.<br>
If they aren't, that could take minutes, where the user will just be
left waiting and wondering why his upload got to 100% and then just
sat there!<br>
<br>
<br>
<blockquote type="cite"
cite="mid:WM!a3784f0a996fe1e59a55f8fbbd7e2ede230925f9d1367c060f2a873e374deaabbf97f713f8d85582b646c183bf9f37da!@mx.jul.es"><br>
2) The lines above define 'dropoffs'. Where is 'incoming' defined?
<br>
</blockquote>
php.ini. It's the temporary upload location that PHP uses.<br>
<br>
Cheers,<br>
Jules.<br>
<br>
<blockquote type="cite"
cite="mid:WM!a3784f0a996fe1e59a55f8fbbd7e2ede230925f9d1367c060f2a873e374deaabbf97f713f8d85582b646c183bf9f37da!@mx.jul.es"><br>
On 12/2/2020 1:57 AM, Jules wrote:
<br>
<blockquote type="cite">There should be a cron job that cleans
these up for you.
<br>
It should be in /etc/cron.d/zendto.
<br>
The relevant line in that file is this one:
<br>
<br>
5 */4 * * * root find -H /var/zendto/incoming -type f -mmin
+1440 -delete >/dev/null 2>&1
<br>
<br>
This will fire every 4 hours, deleting any files in
/var/zendto/incoming that are more than 24 hours old.
<br>
</blockquote>
<br>
_______________________________________________
<br>
ZendTo mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:ZendTo@zend.to">ZendTo@zend.to</a>
<br>
<a class="moz-txt-link-freetext" href="http://jul.es/mailman/listinfo/zendto">http://jul.es/mailman/listinfo/zendto</a>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">Jules
--
Julian Field MEng CEng CITP MBCS MIEEE MACM
'Solutions nearly always come from the direction you least expect, which
means there's no point trying to look in that direction because it won't
be coming from there.' - Douglas Adams
<a class="moz-txt-link-abbreviated" href="http://www.Zend.To">www.Zend.To</a>
Twitter: @JulesFM
</pre>
</body>
</html>