Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

llines(1) [debian man page]

llines(1)						      General Commands Manual							 llines(1)

NAME
llines - LifeLines genealogy program SYNOPSIS
llines [OPTION]... llines [OPTION]...Database DESCRIPTION
llines invokes the LifeLines genealogy program. For up to date documentation please refer to the Documentation section of this man page. LifeLines is a program to manipulate genealogical information in lineage-linked GEDCOM format. It has a curses interface, and a built-in interpreter for its own genealogical report language. OPTIONS
The following options are some of the options available for llines. -C Specify configuration file location. -F Finnish option (only available if compiled with Finnish flag) -I Specify a user property (e.g. -ILLEDITOR=gvim) -a Log dynamic memory operation (for debugging) -c Supply cache values (eg, -ci400,4000f400,4000 sets direct indi & fam caches to 400, and indirect indi & fam caches to 4000) -d Developmental/debug mode (signals are not caught) -f Force open a database (only for use if reader/writer count is wrong) -i Open database with immutable access (no protection against other access -- for use on read-only media) -k Always show key values (normally key is not shown if a REFN is shown) -l Lock (-ly) or unlock (-ln) a database for use with read only media (access to a locked database is treated as immutable) -n Do not use traditional family rules -o Specify program output filename (eg, -o/tmp/mytests) -r Open database with read-only access (protect against other writer access) -uCOLS,ROWS Specify window size (eg, -u120,34 specifies 120 columns by 34 rows) -w Open database with writeable access (protecte against other reader or writer access) -x Execute a single lifelines report program directly -z Use normal ASCII characters for drawing lines in user interface rather than the vt100 special characters -? Display options summary, (on UNIX or Linux use the -h option) llexec is a version of llines without the user interface for non-interactive processing of report programs. (Typically used with the -x option.) dbverify is a utility program to verify Lifelines databases. For information about options, run dbverify with the -h option. FILES
/etc/lifelines.conf ~/.linesrc ~/lines.cfg ./linesrc ./lines.cfg Possible locations for Lifelines configuration file Lifelines looks for a configuration file for various settings. See section Sys- tem And User Properties in the userguide for details. DOCUMENTATION
The LifeLines documentation should be installed as part of the installation, and may also be viewed at the project site: http://life- lines.sourceforge.net. Look for ll-userguide and ll-reportmanual (with appropriate extensions for text, html and pdf formats). The normal installation process includes a large number of sample report programs that you can customize to suit your needs. In the directory con- taining these reports you should find a file named index.html which gives a very brief summary of each report. SEE ALSO
llexec(1), dbverify(1), btedit(1) Lifelines 3.0.61 2007 Aug llines(1)

Check Out this Related Man Page

userdbck(1M)															      userdbck(1M)

NAME
userdbck - verify or fix information in the user database, /var/adm/userdb SYNOPSIS
[file] DESCRIPTION
verifies the information in the user database reports inconsistencies, and fixes problems. If no options and no arguments are specified, reports all data corruption problems in all files in If the option is also specified, each reported problem is repaired. If a file argument (hex 00-ff) is specified, only that file in the directory is verified. Options The following options are recognized: Verify attributes. Information in is used to report any attribute that is not valid, not allowed in the user database, has an invalid value, or is allowed only for a local user and the user is not in Normally when the user database is disabled (see userdb(4)), immediately exits without verifying or repairing the database. The option overrides this and forces to verify or repair the database. Verify user names. User names found in the database are reported if they do not exist in any of the repositories defined in This option could take a long time on a system with many users. Repair all data corruption problems that are found. If this option is not specified, problems are reported but not repaired. Notes Only users who have read and write access to can run RETURN VALUE
exits with one of the following values: success: no inconsistencies were found inconsistencies were found and fixed invalid usage database is disabled; see userdb(4) inconsistencies were found but not fixed, because the option was not specified a problem was found that could not be fixed EXAMPLES
In the following example, all problems in the user database are reported but not repaired. In the following example, all problems in file are reported and repaired. FILES
user database security defaults configuration file security attributes description file SEE ALSO
userdbget(1M), userdbset(1M), userdb_read(3), security(4), userdb(4). userdbck(1M)
Man Page