No man pages in solaris 9

have installed solaris 9 by live upgrade from solaris 8 to solaris 9 . After installation i cannot find man pages . i installed the package SUNWdoc but still its not working . Any suggestion is greatly appreciated
And also smc not working , any ideas .

Man pages are in SUNWman package. During Live Upgrade did you use Sol 9 CD 2 of 2 or did you quit after just using CD 1 of 2? Additionally, if your original Sol 8 install was "Core" or "End User" the man pages would not have been installed, by default, unless you added them later, so the LU may have seen that original was "Core" for example, and didn't load man pages.

Similar Messages

Can't view man pages on solaris 8 x86

Hi,
I installed solaris 8 on a intel x86 machine not using the webwizard because I wanted a minimal installation.
When I try to view man pages I get the following error:
man manReformatting page. Please Wait...Invalid SGML. File cannot be formatted
sys(cd /usr/share/man; /usr/lib/sgml/sgml2roff /usr/share/man/sman1/man.1 > /tmp/sman_3827) fail!
aborted (sorry)
when I list /usr/lib/sgml then I got the following files:
ls -ltotal 2830
-rwxr-xr-x 1 root bin 68016 Jan 9 2000 instant
-rwxr-xr-x 1 root bin 1366552 Jan 9 2000 nsgmls
-rwxr-xr-x 1 root bin 3183 Jan 6 2000 sgml2roff
Don't know what is wrong but I think I'm missing a package, anybody clues...
with regards,
Martijn de Munnik
[email protected]

Depending on how minimal your install was, you may not have installed the man pages.
Take a look in /usr/share/man and see if you have the man pages installed, and if not, install them.

Man pages in solaris 9

I have installed solaris 9 by live upgrade from solaris 8 to solaris 9 . After installation i cannot find man pages . i installed the package SUNWdoc but still its not working . Any suggestion is greatly appreciated
And also smc not working , any ideas .

SUNWman seems to be the package containing the man pages:
% pkgchk -l -p /usr/share/man/sman1/sh.1
Pathname: /usr/share/man/sman1/sh.1
Type: regular file
Expected mode: 0444
Expected owner: root
Expected group: bin
Expected file size (bytes): 86295
Expected sum(1) of contents: 52036
Expected last modification: Okt 19 00:48:12 2002
Referenced by the following packages:
SUNWman
Current status: installed

Man pages for "expr" command incorrect

There appears to be a loss of functionality from the HP-UX environment to the SOLARIS OS that is not noted in the man pages. The man pages for Solaris 5.8 insist that the command expr allows for the argument "substr" as well as "length". However this functionality is not available though the expr command.
Many of our in-house scripts use logic such as
expr substr $VAR 3 2
or
expr length $VAR
Which was valid in the HPUX 10.20 environment. However this command in the Solaris environment results in "expr: syntax error" errors. According to the MAN pages the errors we are having are not happening.

Actually, the man page says that "length" and "substr" are supported only on Solaris x86 and only for compatibility with INTERACTIVE UNIX.
You could use a little script like this one to replace "expr substr" and "expr length" (perl considers the substr's "offset" to be zero-based -- subtract one from $ARGV[2] if HPUX does not).
#!/usr/bin/perl
if ($ARGV[0] eq "substr") {
$out = substr($ARGV[1], $ARGV[2], $ARGV[3]);
elsif ($ARGV[0] eq "length") {
$out = length($ARGV[1]);
else {
print "usage: perl-expr substr string offset length\n";
print " or perl-expr length string\n";
exit 1;
print "$out\n";
exit 0;

Bug with Solaris man page on dlsym

I hope someone at Sun working on Solaris is reading this. There are bugs in the Solaris 10 man page on dlsym - there are a couple of places that says "see the .". Apparently soemthing is missing. My version of man pages is "Last change: 26 Sep 2005".

The prototype of pthread_create() is correct on Solaris 10 man page (SunOS 5.10 Last change: 23 Mar 2005):
int pthread_create(pthread_t *restrict thread, const
pthread_attr_t *restrict attr, void
*(*start_routine)(void*), void *restrict arg);
But the prototype of pthread_cleanup_push() is correct on Solaris 10 man page (SunOS 5.10 Last change: 4 Oct 2005) is incorrect:
void pthread_cleanup_push(void (*handler, void *),void *arg);
I guess Sun simply has to check all the man pages of the pthread functions carefully one by one to make sure this error is fixed.

Core install - no man pages & can not eject cdrom solaris 10

I did a custom core install for solaris 10. I thought I installed all the packages needed, as well as all the dependacies.
I have no man pages!
I can not eject cdrom, I get an error:
"No such file or directory"
When I type vold I also get an error:
"fatal: vol-init failed (cant communicate with kernel)
I can not start in services by:
svcadm enable vold
How do I fix?

I have fixed the vol_init error
touch /reconfigure;init 6
What cd is the man pages on for solaris 10
would it just be pkgadd -d /yada/yada...

What does "restrict" mean in Solaris 10 man pages ?

Hi everyone,
On Solaris 10 programming man pages I see the
"restrict" word used quite often. What is its meaning ?
It wasn't there in previous releases. Is it documented anywhere ?
Excerpt from select(3c) man page:
    int select(int nfds, fd_set *restrict readfds, fd_set *res-
     trict writefds, fd_set *restrict errorfds, struct timeval
     *restrict timeout);Thanks.,
Vlad.

It's for C99. It has to do with pointer aliasing. See section D.1.2.1 of
http://docs.sun.com/source/817-6697/c99.app.html
and section 3.8.2 of
http://docs.sun.com/source/817-6697/parallel.html#70231
- Stephen

Thr_create() returns -1 which isn't specified in the man page. What is -1?

Hello,
I'm for the first time experimenting with Solaris threads as I'm porting an AIX app. over to Solaris.
Anyhow, I have a sample program that creates a simple thread. For some reason, the return value of of the initial thr_create is -1, which isn't specified in the man page for thr_create. The man page lists the following return values, non of which are -1:
RETURN VALUES
Zero indicates a successful return and a non-zero value
indicates an error.
ERRORS
If any of the following conditions occur, these functions
fail and return the corresponding value:
EAGAIN The system-imposed limit on the total number
of threads in a process has been exceeded or
some system resource has been exceeded (for
example, too many LWPs were created).
EINVAL The value specified by attr is invalid.
If any of the following conditions are detected,
pthread_create() fails and returns the corresponding value:
ENOMEM Not enough memory was available to create the
new thread.
If any of the following conditions are detected,
thr_create() fails and returns the corresponding value:
EINVAL o stack_base is not NULL and stack_size is
less than the value returned by
thr_min_stack(3T).
o stack_base is NULL and stack_size is not
zero and is less than the value returned by
thr_min_stack(3T).
However, I don't see a -1 there and therefore, don't know what this means.
Here is the simple code that I wrote for this experiment as well as the output. It doesn't get too far into the program before exiting - I've bolded where it exits:
#define _REENTRANT
#include <stdio.h>
#include <thread.h>
#include <errno.h>
/* Function prototypes for thread routines */
void sub_a(void );
void sub_b(void );
void sub_c(void );
void sub_d(void );
void sub_e(void );
void sub_f(void );
thread_t thr_a, thr_b, thr_c;
void main()
thread_t main_thr;
int rc = 0;
main_thr = thr_self();
printf("Main thread = %d\n", main_thr);
if (rc = thr_create(NULL, 0, sub_b, NULL, THR_NEW_LWP, &thr_b))
printf("\n rc = %d",rc);
switch(rc)
case EAGAIN: printf("This one1");
break;
case EINVAL: printf("This one2");
break;
case ENOMEM: printf("This one3");
break;
default: printf("rc = %d");
break;
fprintf(stderr,"Can't create thr_b\n"),
* exit(1); *
/* if (thr_create(NULL, 0, sub_a, (void *)thr_b, THR_NEW_LWP, &thr_a))
fprintf(stderr,"Can't create thr_a\n"), exit(1); */
if (thr_create(NULL, 0, sub_c, (void *)main_thr, THR_NEW_LWP, &thr_c))
fprintf(stderr,"Can't create thr_c\n"), exit(1);
printf("Main Created threads A:%d B:%d C:%d\n", thr_a, thr_b, thr_c);
printf("Main Thread exiting...\n");
thr_exit((void *)main_thr);
void sub_a(void arg)
thread_t thr_b = (thread_t) arg;
thread_t thr_d;
int i;
printf("A: In thread A...\n");
if (thr_create(NULL, 0, sub_d, (void *)thr_b, THR_NEW_LWP, &thr_d))
fprintf(stderr, "Can't create thr_d\n"), exit(1);
printf("A: Created thread D:%d\n", thr_d);
/* process
for (i=0;i<1000000*(int)thr_self();i++);
printf("A: Thread exiting...\n");
thr_exit((void *)77);
void * sub_b(void *arg)
int i;
printf("B: In thread B...\n");
/* process
for (i=0;i<1000000*(int)thr_self();i++);
printf("B: Thread exiting...\n");
thr_exit((void *)66);
void * sub_c(void *arg)
void *status;
int i;
thread_t main_thr, ret_thr;
main_thr = (thread_t)arg;
printf("C: In thread C...\n");
if (thr_create(NULL, 0, sub_f, (void *)0, THR_BOUND|THR_DAEMON, NULL))
fprintf(stderr, "Can't create thr_f\n"), exit(1);
printf("C: Join main thread\n");
if (thr_join(main_thr,(thread_t *)&ret_thr, &status))
fprintf(stderr, "thr_join Error\n"), exit(1);
printf("C: Main thread (%d) returned thread (%d) w/status %d\n", main_thr, ret_thr, (int) status);
/* process
for (i=0;i<1000000*(int)thr_self();i++);
printf("C: Thread exiting...\n");
thr_exit((void *)88);
void * sub_d(void *arg)
thread_t thr_b = (thread_t) arg;
int i;
thread_t thr_e, ret_thr;
void *status;
printf("D: In thread D...\n");
if (thr_create(NULL, 0, sub_e, NULL, THR_NEW_LWP, &thr_e))
fprintf(stderr,"Can't create thr_e\n"), exit(1);
printf("D: Created thread E:%d\n", thr_e);
printf("D: Continue B thread = %d\n", thr_b);
thr_continue(thr_b);
printf("D: Join E thread\n");
if(thr_join(thr_e,(thread_t *)&ret_thr, &status))
fprintf(stderr,"thr_join Error\n"), exit(1);
printf("D: E thread (%d) returned thread (%d) w/status %d\n", thr_e,
ret_thr, (int) status);
/* process
for (i=0;i<1000000*(int)thr_self();i++);
printf("D: Thread exiting...\n");
thr_exit((void *)55);
void * sub_e(void *arg)
int i;
thread_t ret_thr;
void *status;
printf("E: In thread E...\n");
printf("E: Join A thread\n");
if(thr_join(thr_a,(thread_t *)&ret_thr, &status))
fprintf(stderr,"thr_join Error\n"), exit(1);
printf("E: A thread (%d) returned thread (%d) w/status %d\n", ret_thr, ret_thr, (int) status);
printf("E: Join B thread\n");
if(thr_join(thr_b,(thread_t *)&ret_thr, &status))
fprintf(stderr,"thr_join Error\n"), exit(1);
printf("E: B thread (%d) returned thread (%d) w/status %d\n", thr_b, ret_thr, (int) status);
printf("E: Join C thread\n");
if(thr_join(thr_c,(thread_t *)&ret_thr, &status))
fprintf(stderr,"thr_join Error\n"), exit(1);
printf("E: C thread (%d) returned thread (%d) w/status %d\n", thr_c, ret_thr, (int) status);
for (i=0;i<1000000*(int)thr_self();i++);
printf("E: Thread exiting...\n");
thr_exit((void *)44);
void sub_f(void arg)
int i;
printf("F: In thread F...\n");
while (1) {
for (i=0;i<10000000;i++);
printf("F: Thread F is still running...\n");
OUTPUT:
# /emc/smithr15/solthread
Main thread = 1
rc = -1Can't create thr_b
rc = -1#
Any ideas as to what -1 indicates and how to solve this?
Thanks for your response,
dedham_ma_man

ok, my bad. I wasn't linking in the -lthread library.
Thanks anyway.

No scrolling when viewing man pages with Gnome terminal?

Hi all,
I have just installed Oracle Solaris 11 on x86. For a long time I've used Solaris 9 on SPARC. I like the new OS, but I'm having a problem viewing man pages with Gnome terminal. When I view a long man page, e.g., "man newfs", I don't get a functional scroll bar on the right hand side of the window. And although the space bar works to advance the page, when I reach the end, it doesn't return to the command prompt. It just beeps, prints "END", and I can only exit by closing the window. Can anyone tell me how to fix this? Suggestions would be much appreciated.
Many thanks,
Chris Tidy

It does sound like you're using "less" instead of more. When you see the "(END)" prompt you can simply type "q" and it will exit back to the command line prompt making it unnecessary to close the window. See the "less" manual page for more detail on the less command. Under Solaris 9 the paging was done with the "more" command. If you set the PAGER environment variiable to "more" the man page will use more and revert to the behavior you'd be used to with Solaris 9. Less erases the text you've already read when you type that final "q" which is a behavior I don't like. I didn't bother to determine if there is a way to fix that with less, I just went back to more. The choice between "more" and "less" is a personal preference.

Unable to view (most) man pages

... really aggravating:
I've recently completed a Solaris 8 install (Sparc). I've also installed some software from the "companion" cd (in /opt/sfw). I have gobs of man page files in several locations, but I am unable to view most of them. I've tried entering various "man" incantations on a command line, and double-clicking on man page files in the file manager window. Nothing works - from the cmd line for example:
# man -s 1 zip
"Reformatting page. Please wait... done"
or, in File Manager:
Double-click a man file (e.g. zip.1) in File Manager gets this message: "Man page could not be formatted. THe requested Man Page is either not present, or corrupt."
However, there are a few files (in /opt/sfw/man) that, when double-clicked in FIle Manager (or man'd fm the command line) will display.
I've searched the FAQs 'til my eyes are bleeding, but have found no answers. Can someone tell me WTFIGO?
Thanks!

You may want to pkginfo -l SUNWman to see if your main man pages were installed successfully.
Also check:
http://docs.sun.com:80/ab2/coll.40.6/REFMAN1/@Ab2PageView/201680?Ab2Lang=C&Ab2Enc=iso-8859-1
For info on MANPATH and locale variables that may affect viewing.

A non-trivial typo in the man page for pthread_cleanup_push()?

On my Solaris 9 and 10 systems, the prototype of the pthread_cleanup_push() function is, according to the man page:
void pthread_cleanup_push(void (*handler, void *), void *arg);
Should it be
void pthread_cleanup_push(void (*routine) (void *), void *arg); ?
Alternatively, if both are correct, what are the differences between the two? I tried to use the first format to write some test code and got a bunch of syntax errors.

Ditto for pthread_create():
int pthread_create(pthread_t thread, const pthread_attr_t attr,
void *(*start_routine, void*),void *arg);

How to install man pages

I recently installed Solaris 8 but did not install the man pages. Is it possible to install them now. If yes, then can I get from the install CD or can I download from sun's website.
thanks for your help
SG

yes, you can install manpages after the installation is done.
in the admintool you can choose software, then add.
now you must specify your media (cd) and choose the software to install.

Install man pages

Hi
I installed Solaris 10 x86 with a complete install, but I not have the man page installed.
How I can install it ?
roberto

That is hardly possible, how did you come to this conclusion?

Nsswitch behavior -vs- man page?

I have a question about Solaris 10's /etc/nsswitch.conf
functionality. It seems like it does not work as it use to, say in
Solaris 8 or 9, yet the man page for nsswitch.conf indicates that for
DNS, NIS, and "all other sources" that the DEFAULT criteria should be
"NOTFOUND=continue".
Yet for the past few years it seems I must manually put something like
the lines below in the nsswitch file for "continue" to work
correctly? Is this a bug, or am I completely misunderstanding the man
page and/or how nsswitch REALLY works? Very possible!
hosts: files [NOTFOUND=continue] dns [NOTFOUND=continue] nis
ipnodes: files [NOTFOUND=continue] dns [NOTFOUND=continue] nis
If I use the "default sample file for NIS (/etc/nsswitch.nis) which
may contain something like "hosts: nis [NOTFOUND=return] files" and
yet I want to add DNS, what might the line look like?
I know I have to copy the sample file to the .conf file extension.
Thanks,

Your question is a little fuzzy, but I'll try to answer anyway...
nsswitch.conf file is responsible for specifying the name services that are to be used when trying to find a particular piece of information.
In Solaris, there are 5 possible sources (name services): files, nis, nisplus, dns and ldap.
You may specify multiple (even all) sources to be used. All sources are checked in the order they are written on a line.
Every source may return 4 status values: SUCCESS, NOTFOUND, UNAVAIL or TRYAGAIN.
For every return status, there are 2 possible actions: continue and return. continue means "try the next source", return means "don't look any further". The default action for every status is continue, except for the SUCCESS status, when action is *return", obviously...
One can overwrite the default action for each status, by specifying what action should be taken for any return status.
Let's take for instance this line:
hosts: files dns [NOTFOUND=continue] nis [NOTFOUND=return] ldapThis is interpreted as follows:
- first check "files" (i.e. check /etc/inet/inpnodes, /etc/inet/hosts); no action is specified for any return status, so default actions are in place: if the entry is found on files (SUCCESS), then action is return" , if status is anything else, then action is continue* and next source is checked
- next source is "dns"; if SUCCESS, program will return; if NOTFOUND , then continue to the next source (this is also the default action, but it doesn't matter - this line is just for teaching purposes...); if UNAVAIL (service dns is not configured) or TRYAGAIN (server was too busy to respond to request), then apply default action: *continue"
- next source is nis; if SUCCESS ,then default action (*return*); if NOTFOUND then overwrite default action and return ; so, if the entry is found or not found in nis, the next source (ldap) will not be checked.
and so on....
>
If I use the "default sample file for NIS (/etc/nsswitch.nis) which
may contain something like "hosts: nis [NOTFOUND=return] files" and
yet I want to add DNS, what might the line look like?
{quote}
Well, it depends; suppose you want to check dns after nis and before files. The line may look like this:
{code}
hosts: nis dns files
{code}
The above entry will check dns even if nis returns NOTFOUND.
Hope you got the idea...
kido

Man page or example for ddi_walk_devs

Hallo,
I'm developing a pseudo driver for Solaris 8 on UltraSparc 540 architecture.
I would like walk trough the dev_info tree and store some infos about my machine. I know it is possible to do this at user level with the functions of libdevinfo library but unfortunately it can't work in a driver I've found the prototypes and short comments for a set of functions like ddi_walk_devs, ddi_get_child ... in the file
/usr/include/sys/sunddi.h
There are no documents or man pages about.
Is there anyone who has already used this functions or could help me.
Thank you very much for your help.
al_vise

Hi Al,
ddi_walk_devs(device, function, argument);
The first argument is a device node to start from.If you want to start from the top there is a ddi_root_node function.
ddi_walk_devs then walks the device tree a level at a time, calling a function specified by you as the second arg. This function is passed a pointer to the device node, and your final pointer argument.
However, before calling this, the device tree has to be locked. This used to be done with a reader_writer lock, now there is a new undocumented function to do it (i_ndi_block_device_tree_changes).
The ddi_walk_devs function is deliberately not documented because it is not intended for use in leaf drivers, and its is subject to change (as per the tree locking).
Hope that helps.
Regards,
Ralph
SUN DTS

No man pages in solaris 9

Similar Messages

Maybe you are looking for