diff --git a/CHANGES b/CHANGES index 4ad68be..7edb73b 100644 --- a/CHANGES +++ b/CHANGES @@ -1,6 +1,24 @@ CHANGES ======= +version 7.1.4 (Jan 21, 2002): + - console -[PqQ] didn't work - patch by Han Pilmeyer + + - maxfiles() didn't check FD_SETSIZE - patch by Justin Grudzien + + - New -o and -O server flags for automatically reconnecting + downed consoles - patch by Benn Oshrin + - Automatic reconnection of consoles on read failures, retried + every minute + - Up to nine break sequences can be defined in the + configuration file and assigned to consoles individually, + accessed via new ^ecl[?0-9] escape sequences + - console logs are marked with "up" and "down" timestamps + The following based on code by John R. Jackson + - sequential timestamps merged into one range during playback + - timestamps done on "nice" boundaries (hour, minute, etc.) + - lots of code cleanup, optimizations, etc. + version 7.1.3 (Oct 16, 2001): - NetBSD 1.5 termios bug/compatibility - patch by Andreas Wrede @@ -23,7 +41,7 @@ version 7.1.2 (Oct 15, 2001): - Widened username field of 'console -w' output - Added server hostname to password entry prompt - AC_CHECK_LIB replaced with AC_SEARCH_LIBS in configure.in so - that irrelavent (and sometimes incompatible) libraries aren't + that irrelevant (and sometimes incompatible) libraries aren't linked in version 7.1.1 (Aug 4, 2001): @@ -81,7 +99,7 @@ version 7.1.0 (Jul 26, 2001): - Improved process handling (POSIX waitpid() now necessary) - Significant rework of STREAMS-based pseudo-tty code - TCP connections ('!' config syntax) now have some Telnet protocol - knowledge, removing the "noise" seen when conneting to a terminal + knowledge, removing the "noise" seen when connecting to a terminal server - reported by Todd Stansell - Various code and message "pretty-printing" done - Client and server both run in Windows (tested with Windows @@ -247,5 +265,5 @@ before version 6.05: and enhancements of various types were applied. # -# $Id: CHANGES,v 1.50 2001-10-16 21:32:33-07 bryan Exp $ +# $Id: CHANGES,v 1.52 2002-01-21 02:49:42-08 bryan Exp $ # diff --git a/FAQ b/FAQ index 7aa34df..3c5f3c2 100644 --- a/FAQ +++ b/FAQ @@ -1,4 +1,4 @@ - + Conserver FAQ ============= @@ -14,6 +14,7 @@ directed to faq@conserver.com. The FAQ answers the following questions: 6) What does "console: gethostbyname: console: host lookup error" mean (or something close to that)? 7) How do I set up a serial port for no parity? + 99) Ok, things just don't seem to work. Help?!? 1) What is conserver? @@ -78,6 +79,45 @@ directed to faq@conserver.com. The FAQ answers the following questions: but the answer is to use a 'p' after the baud rate. So, '9600p' is 9600 baud, no parity. +99) Ok, things just don't seem to work. Help?!? + + Yes, this is a pretty vague question, but here are a few tips that + might help. + + - Is your low-level serial connection correct? Incorrect cables, + adapters, wiring, etc. could be the issue. Using a signal tracer + or attaching other equipment that's known to work (like a laptop) + might be enlightening. Check out + http://www.conserver.com/consoles/msock.html for basic serial + information (or http://www.conserver.com/consoles/ for even more + info). + + - Can you talk to the serial port with different software? Try + using tip or minicom or another application to make sure you can + interact with the port. If you're not seeing the right info + here, there may be a baud rate issue, a lack of a getty (or + equivalent) running on the host or...*shrug*. But, if you've + determined that you already have a valid low-level signal + connection, you shouldn't have to worry about that level of + problem. + + - So, you're getting the proper interaction from other + applications, but not conserver? Are the port name and baud rate + correct in the conserver.cf file? When you start conserver + (adding -v doesn't hurt), are there any warnings/errors? Is the + port in the "up" state when you use "console -u"? If not, what + happens when you connect and then do a "^eco" escape sequence to + bring it up? What does the conserver process say when you do + this? These are the types of things I look at first. If that + doesn't help you determine the problem, others will want to see + this info (and possibly the same steps with both the client and + server using the -D option) to be able to help. Posting your + questions to the users mailing list is probably your next step. + + - Have you tried a search on the conserver site (it searches + mailing list traffic as well) to see if someone else has gone + through the same problem? + # -# $Id: FAQ,v 1.3 2001-04-04 16:58:49-07 bryan Exp $ +# $Id: FAQ,v 1.5 2002-01-20 19:06:42-08 bryan Exp $ # diff --git a/TODO b/TODO index 6ecc6e6..bbeea55 100644 --- a/TODO +++ b/TODO @@ -30,6 +30,8 @@ Bryan Stansell - PAM support - syslog? + Daniel E. Singer would like to see it - especially + in regards to --use-libwrap code - alternate (md5) password encryption support in conserver.passwd @@ -113,5 +115,5 @@ Bryan Stansell things) once instead of leaving it down. # -# $Id: TODO,v 1.16 2001-10-16 00:13:27-07 bryan Exp $ +# $Id: TODO,v 1.17 2002-01-18 09:56:57-08 bryan Exp $ # diff --git a/conserver.cf/conserver.cf.man b/conserver.cf/conserver.cf.man index e0765fa..553b429 100644 --- a/conserver.cf/conserver.cf.man +++ b/conserver.cf/conserver.cf.man @@ -1,4 +1,4 @@ -.\" $Id: conserver.cf.man,v 1.17 2001-08-04 20:54:25-07 bryan Exp $ +.\" $Id: conserver.cf.man,v 1.23 2002-01-20 21:14:43-08 bryan Exp $ .\" @(#)constab.5 01/06/91 OSU CIS; Thomas A. Fine .TH CONSERVER.CF 5 "Local" .SH NAME @@ -9,11 +9,13 @@ conserver.cf \- console configuration file for conserver(8) .br .BI \s-1TIMESTAMP\s0= timestamp-spec .br -\fIname\fP:\fIdevice\fP[@\fIconserver\fP]:\fIbaud\fP:\fIlogfile\fP:\fItimestamp-spec\fP +.BI \s-1BREAK\s0\fIn\fP= break-spec .br -\fIname\fP:!\fItermserver\fP[@\fIconserver\fP]:\fIport\fP:\fIlogfile\fP:\fItimestamp-spec\fP +\fIname\fP:\fIdevice\fP[@\fIconserver\fP]:\fIbaud\fP:\fIlogfile\fP:\fItimestamp-spec\fP:\fIbreak\fP .br -\fIname\fP:|\fIcommand\fP[@\fIconserver\fP]::\fIlogfile\fP:\fItimestamp-spec\fP +\fIname\fP:!\fItermserver\fP[@\fIconserver\fP]:\fIport\fP:\fIlogfile\fP:\fItimestamp-spec\fP:\fIbreak\fP +.br +\fIname\fP:|\fIcommand\fP[@\fIconserver\fP]::\fIlogfile\fP:\fItimestamp-spec\fP:\fIbreak\fP .br \fB%%\fP .br @@ -83,7 +85,7 @@ timestamps applied to the console log file and whether to log read/write connection actions. The format of the specification is [\fImark-interval\fP[\fBm\fP|\fBh\fP|\fBd\fP|\fBl\fP]][\fBa\fP]. -The timestamps look like `[-- MARK -- Mon Jan 25 14:46:56 PST 1999]'. +The timestamps look like `[-- MARK -- Mon Jan 25 14:46:56 1999]'. The `\fBm\fP', `\fBh\fP', and `\fBd\fP' tags specify `minutes' (the default), `hours', and `days'. The `\fBl\fP' tag specifies `lines' and will cause timestamps of the form @@ -104,6 +106,54 @@ All consoles below the \fB\s-1TIMESTAMP=\s0\fP line will use that and until superseded by another \fB\s-1TIMESTAMP=\s0\fP line. To turn off marks for a specific console, use a \fImark-interval\fP of zero. +.TP +.I break +specifies which break sequence to use. The default value is `1'. +Values of `0' thru `9' are valid. A value of `0' will unset the +default break sequence, which will cause the \fB^Ecl0\fP sequence to do +nothing. +.PP +The \fIbreak-spec\fP sequences are defined using +the \fB\s-1BREAK\s0\fIn\fB=\fR +syntax where \fIn\fP is a number from 1 to 9. +There are three builtin defaults: ``\s-1BREAK1\s0=\\z'', +``\s-1BREAK2\s0=\\r~^b'', +and ``\s-1BREAK3\s0=#.reset -x\\r''. The values of +the \fB\s-1BREAK\s0\fIn\fR +sequences are simple characters strings with the exception of `\\' and +`^': +.sp +.PD 0 +.IP \\\\a +alert +.IP \\\\b +backspace +.IP \\\\f +form-feed +.IP \\\\n +newline +.IP \\\\r +carriage-return +.IP \\\\t +tab +.IP \\\\v +vertical-tab +.IP \\\\z +serial break +.IP \\\\\\\\ +backslash +.IP \\\\^ +circumflex +.IP \\\\\fIooo\fP +octal representation of a character (where \fIooo\fP is one to three +octal digits) +.IP \\\\\fIc\fP +character \fIc\fP +.IP ^? +delete +.IP ^\fIc\fP +control character (\fIc\fP is `and'ed with 0x1f) +.PD .PP This section is terminated with a `\fB%%\fP' token on a line by itself. .PP @@ -132,12 +182,16 @@ For example, `\fB192.168.1.0\fP' will allow the class C space of 192.168.1.0, but `\fB192.168.1.0/25\fP' will allow only the lower half of that same address space (192.168.1.0 thru 192.168.1.127). .SH EXAMPLE -# name:path:baud:/usr/adm/logfile:mark +# name:path:baud:logfile:mark:break .nf LOGDIR=/tmp +# overriding the builtin BREAK3 sequence +BREAK3=#.reset\\r +# adding another break sequence +BREAK8=+++ # -# This logs to /tmp/treelog... -tree:/dev/ttyj0:9600e:&log: +# This logs to /tmp/treelog...using BREAK8 +tree:/dev/ttyj0:9600e:&log::8 # # This logs to /tmp/fishlog... fish:/dev/ttyj1:4800e:fishlog: @@ -145,19 +199,21 @@ fish:/dev/ttyj1:4800e:fishlog: # Now we're defaulting to /var/tmp for logfiles... LOGDIR=/var/tmp # -# So, this is /var/tmp/birdlog -bird:/dev/ttyj2:4800m:&log: +# So, this is /var/tmp/birdlog with 1-hour timestamps +bird:/dev/ttyj2:4800m:&log:1h # -# And this is /var/tmp/solarlog... -solar:|telnet solar::solarlog: +# And this is /var/tmp/solarlog, using BREAK4, no timestamps +solar:|telnet solar::solarlog::4 # # Now things are all in /var/consoles/ LOGDIR=/var/consoles shell:|::&: # -# These open connections to ports 2003 and 2004 of ts1... -tribe:!ts1:2003:&: -reptile:!ts1:2004:&: +# These open connections to ports 2003 and 2004 of ts1 +# using BREAK2 and BREAK3 +tribe:!ts1:2003:&::2 +# This one also has 10-minute timestamps and activity logging +reptile:!ts1:2004:&:10ma:3 # # This opens /dev/ttyh0 if running on extra.cc.purdue.edu; # otherwise, clients are redirected to that host. diff --git a/conserver.html b/conserver.html index 0cf224c..2237aea 100644 --- a/conserver.html +++ b/conserver.html @@ -8,6 +8,8 @@ + + Conserver