similar to: Minor nitpick on openssh: man pages

Hi, I am sorry about this stupid question but after compilation of openssh-2.3.0p1 the manpages were installed but a man ssh gives only unstructured response without underlined lines etc. A nroff -man sshd.8 gives the same output but the contents of the file shows a nroff-format. Any ideas? My system is a HP-UX 11.000 with the pam-patch. regards Stephan -- LDS Brandenburg Dr. Stephan Hendl

Hi all. I can't read the openssh man pages on Solaris. I tried all the nroff macro packages I could find, with more or less garbled success. Could someone point me to versions suitable for Solaris, or a man2sgml converter? Or to a good online tutorial covering this issue (SysV vs. BSD?) that would allow me to translate the nroff dialects involved? In the latter case, I would of course

AIX v4.3 returns the correct error $ /usr/bin/nroff -mdoc a /usr/bin/nroff: 1004-010 Cannot find or open /usr/lib/tmac/tmac.doc $ echo $? 130 $ EdGy

On Thu, 3 May 2001, Gus Mancuso wrote: I haven't seen the answer to this question (included way below) yet. I'm installing it on Solaris 8 and have the same problem - I can't read the man pages in any format other than 80 column wrapped text. The Solaris 8 is pretty generic, with all the current patches. OpenSSH version is 2.9p1. The man pages stored in /usr/local/man/manx are

I've noticed that the man pages provided in the tarball do not work on Solaris - the output is not formatted as expected. On a linux box it is possible to view the man pages using nroff -mdoc ./sshd.8, where prepended file is /usr/lib/groff/tmac/tmac.doc. There does not appear to be an equivelent macro file on Solaris 2.6. Does anybody know how I can get the man pages to display properly on

Hi Team, I'm looking to "upgrade" my sites ssh installation from the original. I have built openssh-2.3.0p1 and it looks good. I am puzzled as to why there are so many source distributions? However, that is not why am writing - the man pages provided do not format with either Solaris 'nroff -man' or 'groff -man'. What am I missing here? Thanks for your help. Scott

On Thu, 3 May 2001, Gus Mancuso wrote: > Hello OpenSSH developers > > First, many thanks for producing this app! > > I've noticed that the man pages for openssh don't look > at all like man pages. My somewhat limited > troubleshooting skills point towards a problem with > nroff not expanding the macros embedded in the man > files. > When I `man sshd`, I get

Hi The man pages don't format properly on Tru64 unix for portable openssh. They come out as a solid lump of text. I managed to fix the problem by including the line .so /usr/local/share/groff/tmac/tmac.andoc (I have GNU groff installed) In the man pages. It appears the OSF -man option on nroff doesn't format the pages correctly. Thanks Jeremy -- Jeremy Sanders <jss at

I'm seeing some extremely odd behavior with solaris. I have a suspicion it's me, but here's the story and maybe someone can suggest an avenue of investigation. This seems to be happening with any release of openssh since at least 2.5.2p1. 1) Problem #1: If SSH protocol 1 is enabled then sshd segfaults right off. This turns out to be because the call to arc4random_stir is

Right out of the box (after I made Damien's LDFLAGS fix in configure) using gcc-2.95.2. The only problem I have now is the man pages. I still can't read them using Solaris nroff, and when I tried to build with --with-catman=cat, I got the following during a make install: /rtr/bin/install -c -m 644 ssh.[01].out /usr/local/man/cat1/ssh.1 Try `/rtr/bin/install --help' for more

Thanks to Brian Ripley I have been using R utilities for some time for converting S-Plus UNIX nroff help files to .Rd to .html files. .Rd files seem to be the most natural format for help files and this format is probably easier to maintain than nroff, so I would like to start using .Rd files as my master documentation format if anyone has a utility for going from .Rd to nroff. I guess I could

Greetings, I'm playing aroung with the library and try to encode some PCM samples out of a WAVE file. I recognized that my own encoding is bigger than the encoding with the command line tool and I can't figure out why it is so. I tried some API functions to get a better result but I missed. minimal test code: http://stinfwww.informatik.uni-leipzig.de/~mai02cal/test.c example wav:

http://bugzilla.mindrot.org/show_bug.cgi?id=883 Summary: mdoc2man.awk causes flaw in ssh(1) man page Product: Portable OpenSSH Version: 3.8.1p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: Build system AssignedTo: openssh-bugs at mindrot.org ReportedBy:

This is propagated to R-devel in case anyone else has a comment on this : >>>>> "MM" == Martin Maechler <maechler@stat.math.ethz.ch> writes: MM> On Aug. 14, MM> "Ross" == Ross Ihaka <ihaka@stat.auckland.ac.nz> writes: Ross> Re the emacs stuff: MM> ... Ross> 2. Peter Dalgaard made the suggestion that we made R source

Hi, Just tested the latest snapshot on RHL72 via building RPM's of it. Nroff detection was wrong, and if no --with-mantype was specified, the type would always revert to cat. This one-byter fixes it. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert

Hello everyone, In the process of packaging Icecast and Ices2 for Debian, it was necessary for me to write a set of minimal manual pages to satisfy policy requirements. Since I would be adding them to CVS as part of the debian/ directories anyway, I thought I would present them here, so they could perhaps be integrated with the other forms of packaging. They are very simple but perhaps someone

Roland Mainz wrote: > April Chin wrote: > > I''m in the process of filing manpage bugs for ksh93 to include > > changes to existing pages and new manpages for ksh93(1) and its > > builtins (builtin(1), disown(1)). > > > > CR 6457823 New manpages needed for ksh93 > > > > However, I do not see any manpages for vmap(1), alarm(1), or vpath(1). >

I am using R 1.2.3 on Linux Mandrake 7.2. I have a ton of S Nroff help files that end with source code typified by the following: Last S statement in an example, e.g. X <- y ..KW models ..KW regression ..WR When using R RMD Sd2Rd to create the .Rd file I get X <- y \keyword{models} \keyword{regression} } The } matches a { in \examples{ at the beginning of the example code (started in

Hello, the man pages for openssh-2.3.0p1 look bad on our Tru64 Unix V4.0E systems. (Secure Shell) is a program for logging into a remote machine and for executing commands on a remote machine. It is intended to replace rlogin and rsh, and provide secure encrypted communica- tions between two untrusted hosts over an insecure network. X11 connections and arbitrary TCP/IP ports can also be

Hi, On systems that have mandoc installed but are missing an nroff binary, the configure script will fall back to pre-formatted manual pages despite the fact that mandoc could be used. The proposed patch adds mandoc as a valid formatter to configure.ac. As mandoc supports the -mdoc flag, it can simply be added to the list of nroff-like binaries. Wolfgang -------------- next part --------------