From: 岡本健二 <kokamoto@hera.eonet.ne.jp>
To: "9front@9front.org" <9front@9front.org>
Subject: RE: [9front] The last CD distribution
Date: Sun, 5 Jun 2016 09:26:07 +0900 [thread overview]
Message-ID: <201606050026.u550QI3a027713@mailmsa11.mozu.eo.k-opti.ad.jp> (raw)
In-Reply-To: <201606050021.u550Kxbk026214@mailmsa11.mozu.eo.k-opti.ad.jp>
[-- Attachment #1: Type: text/plain, Size: 144 bytes --]
If the process was expected one.
We have to reboot the auth/file/cpu server whenever we add
a user onto this system.
Am I wrong?
Kenji
[-- Attachment #2: Type: text/html, Size: 6062 bytes --]
next prev parent reply other threads:[~2016-06-05 0:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 8:14 岡本健二
2016-06-03 11:02 ` [9front] " cinap_lenrek
2016-06-03 12:16 ` cinap_lenrek
2016-06-03 14:49 ` stanley lieber
2016-06-04 5:59 ` 岡本健二
2016-06-04 6:16 ` 岡本健二
2016-06-04 14:13 ` cinap_lenrek
2016-06-05 0:20 ` 岡本健二
2016-06-05 0:26 ` 岡本健二 [this message]
2016-06-05 0:37 ` kokamoto
2016-06-05 1:43 ` cinap_lenrek
2016-06-05 7:49 ` kokamoto
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=201606050026.u550QI3a027713@mailmsa11.mozu.eo.k-opti.ad.jp \
--to=kokamoto@hera.eonet.ne.jp \
--cc=9front@9front.org \
/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 NNTP newsgroup(s).