05-14-2009
Indeed, growfs hasn't changed (enough) for its manual page to evolve.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i've never done this before. i created a script that I placed in /usr/bin, but want to create a man page for it. i'm clueless
thanks (3 Replies)
Discussion started by: theDirtiest
3 Replies
2. UNIX for Dummies Questions & Answers
I was wonderiong if ther is a way for a user to add a man page specific to thier account. similar to copying the .1 or .1.gz to /usr/share/man/man1 "cp *.1.gz /usr/share/man/man1". Except for using another folder as I don't have access to /usr/share/man/man1. I would think that this might involve... (1 Reply)
Discussion started by: jacob358
1 Replies
3. Red Hat
Hi Guys,
I'm looking for the man page for scp version 1.2.27
I have an old redhat server that has a few large scripts that use this version and I want to know what the -A flag does and the man page is not on there. (4 Replies)
Discussion started by: Tornado
4 Replies
4. UNIX for Advanced & Expert Users
Man page is not working my system. It is giving the following the following error
> man ls
gdbm fatal: read error
with debug option
> man -d ls
...
....
...
...
using less as pager
checking for locale en_US
add_nls_manpath(): processing /usr/local/man:/usr/share/man:/usr/X11R6/man... (4 Replies)
Discussion started by: praveenkumar_l
4 Replies
5. Solaris
Help,
it seem that i am unable to get man help form solaris 10.
I am running SunOS unknown 5.10 Generic_120012-14 i86pc i386 i86pc
when ever i try to man a command what i get is "No manual entry" like the one below.
# man grep
No manual entry for grep.
# man ls
No manual entry for ls.... (8 Replies)
Discussion started by: ezsurf
8 Replies
6. Solaris
Hi,
I would like to develop a man page as the one we usually get when we execute man <command name>. This man page will be for a samll utility that i have written.
If this is not possible then what are the available possibilites for creating such help.
thanks in advance. (2 Replies)
Discussion started by: raghu.amilineni
2 Replies
7. Shell Programming and Scripting
Hello,
hope this is the correct forum for this question.
I have created a man page, named nfwatchdog.1.gz. This man page was installed under /usr/share/man/man1. When I execute: man nfwatchdog from any location, the man page is incorrectly opened (I see ASCII garbage). But when I directly... (4 Replies)
Discussion started by: nardix
4 Replies
8. UNIX for Advanced & Expert Users
I realise that with GNU 'info' a lot of developers become, dare I say it, quite lazy when it comes to providing a well written man page - and some argue they're not needed at all. But I find, in the products that I develop, that man pages are used more often for quick reference, and therefore the... (1 Reply)
Discussion started by: cambridge
1 Replies
9. UNIX for Dummies Questions & Answers
dear unix experts,
the 'man' command on my system isn't finding a manpage that is
in a MANPATH directory, or even when I specify the path directly:
12:56pm ilya@node1390 /idi/sabetilab/ilya/usr/share/man $ man -M . xemacs
No manual entry for xemacs
12:56pm ilya@node1390... (4 Replies)
Discussion started by: notestaff
4 Replies
LEARN ABOUT FREEBSD
gconcat
GCONCAT(8) BSD System Manager's Manual GCONCAT(8)
NAME
gconcat -- disk concatenation control utility
SYNOPSIS
gconcat create [-v] name prov ...
gconcat destroy [-fv] name ...
gconcat label [-hv] name prov ...
gconcat stop [-fv] name ...
gconcat clear [-v] prov ...
gconcat dump prov ...
gconcat list
gconcat status
gconcat load
gconcat unload
DESCRIPTION
The gconcat utility is used for device concatenation configuration. The concatenation can be configured using two different methods:
``manual'' or ``automatic''. When using the ``manual'' method, no metadata are stored on the devices, so the concatenated device has to be
configured by hand every time it is needed. The ``automatic'' method uses on-disk metadata to detect devices. Once devices are labeled,
they will be automatically detected and configured.
The first argument to gconcat indicates an action to be performed:
create Concatenate the given devices with specified name. This is the ``manual'' method. The kernel module geom_concat.ko will be loaded
if it is not loaded already.
label Concatenate the given devices with the specified name. This is the ``automatic'' method, where metadata are stored in every
device's last sector. The kernel module geom_concat.ko will be loaded if it is not loaded already.
stop Turn off existing concatenate device by its name. This command does not touch on-disk metadata!
destroy Same as stop.
clear Clear metadata on the given devices.
dump Dump metadata stored on the given devices.
list See geom(8).
status See geom(8).
load See geom(8).
unload See geom(8).
Additional options:
-f Force the removal of the specified concatenated device.
-h Hardcode providers' names in metadata.
-v Be more verbose.
SYSCTL VARIABLES
The following sysctl(8) variables can be used to control the behavior of the CONCAT GEOM class. The default value is shown next to each
variable.
kern.geom.concat.debug: 0
Debug level of the CONCAT GEOM class. This can be set to a number between 0 and 3 inclusive. If set to 0 minimal debug information
is printed, and if set to 3 the maximum amount of debug information is printed.
EXIT STATUS
Exit status is 0 on success, and 1 if the command fails.
EXAMPLES
The following example shows how to configure four disks for automatic concatenation, create a file system on it, and mount it:
gconcat label -v data /dev/da0 /dev/da1 /dev/da2 /dev/da3
newfs /dev/concat/data
mount /dev/concat/data /mnt
[...]
umount /mnt
gconcat stop data
gconcat unload
Configure concatenated provider on one disk only. Create file system. Add two more disks and extend existing file system.
gconcat label data /dev/da0
newfs /dev/concat/data
gconcat label data /dev/da0 /dev/da1 /dev/da2
growfs /dev/concat/data
SEE ALSO
geom(4), loader.conf(5), geom(8), growfs(8), gvinum(8), mount(8), newfs(8), sysctl(8), umount(8)
HISTORY
The gconcat utility appeared in FreeBSD 5.3.
AUTHORS
Pawel Jakub Dawidek <pjd@FreeBSD.org>
BSD
May 21, 2004 BSD