Sponsored Content
Top Forums UNIX for Dummies Questions & Answers man synopsis standard compliance Post 302149331 by porter on Wednesday 5th of December 2007 04:20:06 PM
Old 12-05-2007
Interesting, GNU coding standards are very lean on this topic.

I've had a look at a Solaris example...

Code:
     man [-] [-adFlrt] [-M path] [-T macro-package]  [-s section]
     name...

Notice that there is not an option "-adFlrt", they are all different flags, but with no inclusive OR between them. I would tend towards the exclusive OR however I would make the documentation concise and remove ambiguity.
 

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

sudo & Sox compliance

Hello, I am trying to convince my boss to stop allowing our users to login as root (superuser). Currently our users login to our unix server with their own account, then as needed, they will do an su and put in the root password. This scares me, for a bunch of reasons. Mainly, one is that we... (1 Reply)
Discussion started by: rwallaceisg
1 Replies

2. Shell Programming and Scripting

standard error to standard out question

Hi there how can i get the result of a command to not give me its error. For example, on certain systems the 'zfs' command below is not available, but this is fine becaues I am testing against $? so i dont want to see the message " command not found" Ive tried outputting to /dev/null 2>&1 to no... (5 Replies)
Discussion started by: hcclnoodles
5 Replies

3. UNIX for Dummies Questions & Answers

Redirect Standard output and standard error into spreadsheet

Hey, I'm completely new at this and I was wondering if there is a way that I would be able to redirect the log files in a directories standard output and standard error into and excel spreadsheet in anyway? Please remember don't use too advanced of terminology as I just started using shell... (6 Replies)
Discussion started by: killaram
6 Replies

4. HP-UX

Password compliance setting

I need to set password compliance for some servers in my company. However, the requirements are that we need to set different password policies for 3 different user groups within the company. These are : System Users: i.e root, etc Batch/Application Users: oracle, bscs, etc Standard User:... (0 Replies)
Discussion started by: anaigini45
0 Replies

5. OS X (Apple)

POSIX compliance...

Thanks to all you guys about posix compliance I have learnt an enormous amount over the last few days. I have written a program that is an Egg Timer with simple animation. I now realise how sophisticated 'bash' is compared to full posix compliance. The code below has passed all of the tests from... (11 Replies)
Discussion started by: wisecracker
11 Replies
WHEREIS(1)						      General Commands Manual							WHEREIS(1)

NAME
whereis - locate the binary, source, and manual page files for a command SYNOPSIS
whereis [-bmsu] [-BMS directory... -f] filename... DESCRIPTION
whereis locates source/binary and manuals sections for specified files. The supplied names are first stripped of leading pathname compo- nents and any (single) trailing extension of the form .ext, for example, .c. Prefixes of s. resulting from use of source code control are also dealt with. whereis then attempts to locate the desired program in a list of standard Linux places. OPTIONS
-b Search only for binaries. -m Search only for manual sections. -s Search only for sources. -u Search for unusual entries. A file is said to be unusual if it does not have one entry of each requested type. Thus `whereis -m -u *' asks for those files in the current directory which have no documentation. -B Change or otherwise limit the places where whereis searches for binaries. -M Change or otherwise limit the places where whereis searches for manual sections. -S Change or otherwise limit the places where whereis searches for sources. -f Terminate the last directory list and signals the start of file names, and must be used when any of the -B, -M, or -S options are used. EXAMPLE
Find all files in /usr/bin which are not documented in /usr/man/man1 with source in /usr/src: example% cd /usr/bin example% whereis -u -M /usr/man/man1 -S /usr/src -f * FILES
/{bin,sbin,etc} /usr/{lib,bin,old,new,local,games,include,etc,src,man,sbin, X386,TeX,g++-include} /usr/local/{X386,TeX,X11,include,lib,man,etc,bin,games,emacs} SEE ALSO
chdir(2V) BUGS
Since whereis uses chdir(2V) to run faster, pathnames given with the -M, -S, or -B must be full; that is, they must begin with a `/'. whereis has a hard-coded path, so may not always find what you're looking for. AVAILABILITY
The whereis command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/. 8 May 1994 WHEREIS(1)
All times are GMT -4. The time now is 10:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy