similar to: openssh-2.5.1p1 etc

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

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

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

Why would this be happening, and how can I fix this - the man subsystem hasn't been working because of this for a while. This is FreeBSD-4.9-Prerelease: # gdb man man GNU gdb 4.18 (FreeBSD) This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... /usr/share/tmac/man: No such file or directory. And when I go to run a manpage, I sometimes get this

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

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 --------------

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! I'm trying to cross-compile 4.8-STABLE world to install it over NFS later. I have ./make.conf: # start of file CPUTYPE=i486 KERNCONF?=CONS MODULES_WITH_WORLD=true DESTDIR=/mnt/cons # end of file I run: dir=`pwd` make __MAKE_CONF=$dir/make.conf buildworld 2>&1 | tee $dir/bw.log It fails: ===> gnu/usr.bin/groff/contrib ===> gnu/usr.bin/groff/contrib/mm sh

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

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

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

I'm trying to replace ssh 1.2.27 with openssh 1.2.1-pre* It seems that a openssh client accessing any openssh/ssh server I've setup always results in a password prompt. It also seems that a openssh server requires ssh clients to provide a password regardless of the entries in the /etc/ssh/shosts.equiv file. If I shut off the openssh server and run a ssh server then normal ssh client

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 xtrans is a library of code that is shared (but is *not* a shared library) among various X packages to handle network protocol transport in a modular fashion, allowing a single place to add new transport types. It is used by the X server, libX11, libICE, the X font server, and related components. This minor release converts the libxtrans API

These are all in the port of 1.2.3pre2: - configure accepts --includedir, but doesn't seem to pass it on to the Makefile. You have to edit the Makefile manually if you have include files anywhere but /usr/include. Which is a problem because... - The Makefile doesn't include /usr/local/include by default, which is where zlib installs itself by default. Probably oughta be in there.

I am installing asterisk on a second box with OpenSuSE 10.2. I have installed libpri, run menuselect/configure and then make. The make stops at the last line shown below. Looking at the processes, the current process is running sed. Not sure from where. Any ideas? ... checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln checking for mkdir... /bin/mkdir

I have help files in several formats. Up until now I have converted nroff files to S-Plus 6 sgml and html files using Splus doc_to_S ... (creates .sgml file) Splus HINSTALL ... (creates .sgm and .html files) I maintain master help files in R .Rd files, and for some of my functions converting from .Rd to .sgm using R CMD Rdconv --type=Ssgm ... produces better .sgm files than beginning with

I have a beefy machine (Intel dual-quad core, 16GB memory 2 x GigE) I have loaded RHEL5.1-xen on the hardware and have created two logical systems: 4 cpus, 7.5 GB memory 1 x Gige Following RHEL guidelines, I have it set up so that eth0->xenbr0 and eth1->xenbr1 Each of the two RHEL5.1 guests uses one of the interfaces and this is verified at the switch by seeing the unique MAC addresses.

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

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

Pascal Volk writes: >> Cut&pasted off the terminal man page output. Looking into >> man1/doveadm-move.1, I see >> >> .B doveadm move \-u jane Archive/2011/09 mailbox INBOX BEFORE \(rs >> .B 2011-10-01 SINCE 01-Sep-2011 >> >> so it's a problem with my nroff, not dovecot's man pages. (Hmm, it >> happens with groff too -- it appears