From: Tatsuro MATSUOKA <tmacchant2@yahoo.co.jp>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>,
Tatsuro MATSUOKA <tmacchant2@yahoo.co.jp>
Subject: permission 600
Date: Sun, 9 Jan 2022 14:28:08 +0900 (JST) [thread overview]
Message-ID: <584156248.1199495.1641706088853.JavaMail.yahoo@mail.yahoo.co.jp> (raw)
In-Reply-To: <584156248.1199495.1641706088853.JavaMail.yahoo.ref@mail.yahoo.co.jp>
$ echo aaa > test.txt
$ ls -l test.txt
-rw-r--r-- 1 user user 4 Jan 9 14:07 test.txt
$ chmod 600 test.txt
$ ls -l test.txt
-rw-r--r-- 1 user user 4 Jan 9 14:07 test.txt
I noticed this phenomena in launching the jupyter lab.
File "/usr/lib/python3.8/site-packages/jupyter_core/paths.py", line 909, in secure_write
raise RuntimeError("Permissions assignment failed for secure file: '{file}'."
RuntimeError: Permissions assignment failed for secure file: '/home/user/.local/share/jupyter/runtime/jpserver-27580.json'. Got '0o644' instead of '0o0600'.
Workaround for the jupter lab error is
export JUPYTER_ALLOW_INSECURE_WRITES=true
Tatsuro
next parent reply other threads:[~2022-01-09 5:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <584156248.1199495.1641706088853.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-01-09 5:28 ` Tatsuro MATSUOKA [this message]
2022-01-09 5:38 ` Marco Atzeri
[not found] <517210150.1192809.1641708654835.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-01-09 6:10 ` Tatsuro MATSUOKA
2022-01-09 8:51 ` Thomas Wolff
[not found] <1804805239.1181531.1641726692666.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-01-09 11:11 ` Tatsuro MATSUOKA
2022-01-09 11:25 ` Eliot Moss
[not found] <13484389.1228247.1641769990069.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-01-09 23:13 ` Tatsuro MATSUOKA
2022-01-09 23:26 ` Thomas Wolff
[not found] <996962702.1253083.1641813036736.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-01-10 11:10 ` Tatsuro MATSUOKA
[not found] <1678276178.1336676.1641891339407.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-01-11 8:55 ` Tatsuro MATSUOKA
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=584156248.1199495.1641706088853.JavaMail.yahoo@mail.yahoo.co.jp \
--to=tmacchant2@yahoo.co.jp \
--cc=cygwin@cygwin.com \
--cc=matsuoka@nuce.nagoya-u.ac.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).