<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class=""><br class="">
</div>
<div class="">In the future, software and data will be in different partitions and this may also solve the problem, right?</div>
<div class="">Software is anyway nothing we would like to sync between the systems if I remember correctly.</div>
<div class="">Otherwise, I could add a cleanup target to remove those files or change permissions. Maybe I should do that anyway to cleanup that garbage ...</div>
<div class=""><br class="">
</div>
<br class="">
<div apple-content-edited="true" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<span class="" style="orphans: 2; widows: 2;">All the best,</span></div>
<div class="" style="orphans: 2; widows: 2; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
Jörg</div>
<div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<span class="" style="orphans: 2; widows: 2;"><br class="">
</span></div>
<div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<span class="" style="orphans: 2; widows: 2;">********************************************************************************************</span><br class="" style="orphans: 2; widows: 2;">
<span class="" style="orphans: 2; widows: 2;">Jörg Tiedemann</span></div>
<div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<span class="" style="orphans: 2; widows: 2;">Language Technology<span class="Apple-tab-span" style="white-space: pre;">
</span></span><a href="https://blogs.helsinki.fi/language-technology/" class="">https://blogs.helsinki.fi/language-technology/</a></div>
<div class=""><span style="orphans: 2; widows: 2;" class="">University of Helsinki</span></div>
</div>
</div>
</div>
</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 18 Sep 2019, at 15:44, Stephan Oepen <<a href="mailto:oe@ifi.uio.no" class="">oe@ifi.uio.no</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">at the core of those scripts is just an rsync(1) invocation; i am not<br class="">
sure that an except pattern would actually appease it; and i would be<br class="">
a tad nervous about accidentally dropping sub-directories elsewhere in<br class="">
the tree that should actually be replicated.<br class="">
<br class="">
how about a clean-up script as part of the installation instead,<br class="">
removing directories (at the top level, maybe) that start with a dot?<br class="">
<br class="">
oe<br class="">
<br class="">
<br class="">
oe<br class="">
<br class="">
On Wed, Sep 18, 2019 at 2:34 PM Tiedemann, Jörg<br class="">
<<a href="mailto:jorg.tiedemann@helsinki.fi" class="">jorg.tiedemann@helsinki.fi</a>> wrote:<br class="">
<blockquote type="cite" class=""><br class="">
<br class="">
Could we skip directories that start with ‘.’<br class="">
That would solve all (most?) of the issues below.<br class="">
<br class="">
Jörg<br class="">
<br class="">
********************************************************************************************<br class="">
Jörg Tiedemann<br class="">
Language Technology <a href="https://blogs.helsinki.fi/language-technology/" class="">
https://blogs.helsinki.fi/language-technology/</a><br class="">
University of Helsinki<br class="">
<br class="">
On 18 Sep 2019, at 14:58, Stephan Oepen <<a href="mailto:oe@ifi.uio.no" class="">oe@ifi.uio.no</a>> wrote:<br class="">
<br class="">
dear all,<br class="">
<br class="">
truth be told, i have barely looked at the emails that are<br class="">
auto-generated to the infrastructure task force each night over the<br class="">
past several months, but as we are setting up new instances of the<br class="">
laboratory on Puhti and Saga i would like to go back to actually<br class="">
paying attention to what happens.  among other things, the replication<br class="">
and back-up notifications are good indicators of someone making<br class="">
changes to the shared data and software directories ... and in<br class="">
principle, i think, we should keep abreast with these developments<br class="">
:-).<br class="">
<br class="">
the scripts are written to only send email when something actually<br class="">
happened, or when there is an indication of problems.  for the past<br class="">
several months, we have had some directories and files on both Abel<br class="">
Taito that were not readable by the back-up scripts (which run in user<br class="">
land, as 'oe'), which led to nightly 'problem' emails.<br class="">
<br class="">
joerg and yves, could i ask that you both try fixing file permissions<br class="">
on both systems.  current trouble makers appear to be:<br class="">
<br class="">
[oe@login-nird-0 nlpl]$ grep -i 'permission denied'<br class="">
mirror/*/current/operation/log/*/nird.19-09-17-*<br class="">
mirror/abel/current/operation/log/abel/nird.19-09-17-02:00:rsync:<br class="">
opendir "/projects/nlpl/software/nlpl-common/.cache" failed:<br class="">
Permission denied (13)<br class="">
mirror/abel/current/operation/log/abel/nird.19-09-17-02:00:rsync:<br class="">
opendir "/projects/nlpl/software/nlpl-common/.emacs.d/auto-save-list"<br class="">
failed: Permission denied (13)<br class="">
mirror/abel/current/operation/log/abel/nird.19-09-17-02:00:rsync:<br class="">
send_files failed to open<br class="">
"/projects/nlpl/software/nlpl-common/.lesshst": Permission denied (13)<br class="">
mirror/taito/current/operation/log/taito/nird.19-09-17-02:00:rsync:<br class="">
opendir "/proj/nlpl/software/nlpl-common/.cache/pip/http/8" failed:<br class="">
Permission denied (13)<br class="">
mirror/taito/current/operation/log/taito/nird.19-09-17-02:00:rsync:<br class="">
opendir "/proj/nlpl/software/nlpl-common/.cache/pip/http/9/c" failed:<br class="">
Permission denied (13)<br class="">
mirror/taito/current/operation/log/taito/nird.19-09-17-02:00:rsync:<br class="">
opendir "/proj/nlpl/software/nlpl-common/.cache/pip/http/b/6" failed:<br class="">
Permission denied (13)<br class="">
mirror/taito/current/operation/log/taito/nird.19-09-17-02:00:rsync:<br class="">
send_files failed to open<br class="">
"/proj/nlpl/software/nlpl-common/.cache/pip/http/6/3/c/9/7/63c973d02997ec099a5c771c5ca2ac4b2e125e001a171c85b274b610":<br class="">
Permission denied (13)<br class="">
mirror/taito/current/operation/log/taito/nird.19-09-17-02:00:rsync:<br class="">
send_files failed to open<br class="">
"/proj/nlpl/software/nlpl-common/.cache/pip/http/b/b/8/7/6/bb876b2e6a22c2739002e9ef3388ae978b7a6192a19fe67d8b0030f2":<br class="">
Permission denied (13)<br class="">
<br class="">
from the above, i am guessing that the installation of the 'common'<br class="">
module temporarily treats the module directory as a home directory,<br class="">
leading to stray configuration and cache files there.  minimally, i<br class="">
would recommend you set a more generous umask(1) for these steps, so<br class="">
that the files do not end up with restrictive permissions?<br class="">
<br class="">
cheers, oe<br class="">
<br class="">
<br class="">
</blockquote>
</div>
</blockquote>
</div>
<br class="">
</body>
</html>