9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: [9fans] remote access to fossil console
Date: Tue,  2 Dec 2003 14:18:33 -0500	[thread overview]
Message-ID: <bb16dbac0a15d4a4bbdfa0b9cb3c9f14@plan9.bell-labs.com> (raw)

Here's something I did last week to get remote access to the fossil
console using consolefs to our server called 'ehime':

1) you need a consoledb file, say /lib/ndb/consoledb-ehime:
	% cat consoledb-ehime
	group=sys
		uid=jmk
		uid=...
	console=ehime-fs dev=/srv/fscons
		gid=sys
	%

2) add a case to /bin/C to select the correct server:

	...
	switch($1){
	case ehime-fs
		server=ehime
	case *
		# look for server in /lib/ndb
		server=`{ndb/query sys $1 console}
		switch($server){
		case ''
			echo C: unknown console server for $1
			exit 1
		}
	}
	...

3) add startup code for consolefs in /bin/cpurc.ehime:

	...
	# start the remote fs console server
	if(test -e /srv/fscons)
		aux/consolefs -c /lib/ndb/consoledb.ehime
	...

Now we can 'C ehime-fs' just like we can for the serial consoles
of the servers in the machine room.

I changed consolefs last week not to present the status and ctl files
for remote consoles if the underlying device doesn't support them, but
this will work without that update to consolefs.


             reply	other threads:[~2003-12-02 19:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-02 19:18 jmk [this message]
2003-12-02 20:51 ` Axel Belinfante
2003-12-02 21:06   ` mirtchov
2003-12-02 21:22     ` Axel Belinfante
2003-12-02 20:55       ` Russ Cox
2003-12-03  1:47       ` Dan Cross
2003-12-02 23:27 ` Geoff Collyer
2003-12-03  2:32 ` boyd, rounin
2003-12-02 21:30 David Presotto
2003-12-03  2:37 ` boyd, rounin

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=bb16dbac0a15d4a4bbdfa0b9cb3c9f14@plan9.bell-labs.com \
    --to=jmk@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).