9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steve_Kilbane Steve_Kilbane@cegelecproj.co.uk
Subject: Fun with cs.
Date: Thu, 14 Dec 1995 09:04:05 -0500	[thread overview]
Message-ID: <19951214140405.UQAEP9agvtkgjN_0TjvhB2LOAswuADrgTpmdUaBcqVg@z> (raw)

Waaaay back in August, Vadim mentioned a workaround in /rc/bin/cpurc
for ndb/cs not handling net!$auth!ticket lookups. Is this workaround still
valid, and if so, can someone give me a more complete description? I'm
encountering this problem now.

It sounds to me like cpurc (and, I guess, termrc) should have

ndb/cs -n
sysname=`{cat /dev/sysname}
switch ($sysname) {
case myhost
	...
}
date >>/$cputype/log/$sysname
ndb/cs -n

Does this sound reasonable?

steve






             reply	other threads:[~1995-12-14 14:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-12-14 14:04 Steve_Kilbane [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-12-14 16:10 Dave
1995-12-14  6:25 Vadim
1995-08-17  7:23 Vadim

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=19951214140405.UQAEP9agvtkgjN_0TjvhB2LOAswuADrgTpmdUaBcqVg@z \
    --to=9fans@9fans.net \
    /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).