Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
International Medical Corps

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 117 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

fillup



SYNOPSIS

       fillup [options] basefile addfile outputfile

       fillup [options] basefile addfile

       fillup -V|--version ...

       fillup -h|--help ...


DESCRIPTION

       fillup  -  merges  input  files  into one resulting output
       file. Usually, each file is a configuration file.

       fillup merges files which are holding variables  (ie  con­
       figuration  or  environment  variables).   A  variable  is
       defined by an entity composed of a  preceding  comment,  a
       variable  name,  an  assignment  delimiter,  and a related
       variable value.  A variable is determined by its  variable
       name.

       A  preceding comment is optional.  An assignment delimiter
       may be optional, but if there is an assignment  delimiter,
       a  variable  name must precede it.  The last entity may be
       composed only of a comment.

       Only if variables are included in both input files  (base­
       file  and  addfile)  fillup has to select one of the vari­
       ables.  Otherwise, if variables are included only  in  one
       of  the input files they are added to the resulting output
       file  (with  the  exception  of  the  -i|--ignoreDefinites
       option).

       The  functionality  is now controlled by a parameter which
       determines whether a variable included both in  the  base­
       file  and  in the addfile is taken from the former or from
       the latter.  Furthermore, a parameter controls whether the
       variable is removed from a copy of the basefile.

       To  keep  the  fillup  v1.04 functionality, the outputfile
       parameter can be omitted -- this means the resulting  out­
       put  file  is named exactly like the first input file name
       (basefile = outputfile).

       If variables should be  removed  from  the  basefile,  the
       basefile  is  not  touched,  but  the result is written to
       basefile.new.

       If basefile includes a header as part of the  first  vari­
       able  this  header is preserved only for the outputfile if
       after the header an empty line follows.

       Starting  with  version  1.20  handling  of  metadata  for

       fillup -exchange "/etc/rc.config" "my.config"

       Only variables  of  "/etc/rc.config"  that  are  not  also
       defined  within  "my.config"  are  passed to the resulting
       output file "/etc/rc.config".  All variables  of  "my.con­
       fig" are appended.

       fillup -m -r "/etc/rc.config" "my.config" "/etc/rc.config"

       All  variables  of  "/etc/rc.config"  are  passed  to  the
       resulting output file "/etc/rc.config".  Variables defined
       only within  "my.config"  are  appended.   The  additional
       parameter  '-r'  removes  variables defined more than once
       from a copy of "/etc/rc.config".   "/etc/rc.config"  isn't
       touched  and  the  result  of  the  removal  is written to
       "/etc/rc.config.new".

       fillup -i "/etc/rc.config" "my.config"

       This is a filter functionality. Variables of "/etc/rc.con­
       fig"   are  only  passed  to  the  resulting  output  file
       "/etc/rc.config" if they are defined in both input  files.
       Because  "my.config"  is  normally only a list of variable
       names from "/etc/rc.config", this is  named  filter  func­
       tionality.   Additionally  variables  of  "my.config"  are
       appended if they are defined only in "my.config".


OPTIONS

       There are many options, which are displayed if  fillup  is
       called without or with the -h or --help option.

       Most  of  the parameters are based on v1.04. In the sequel
       only useful parameters are listed:

         -i, --ignoreDefinites    filter functionality
         -t, --trailing           save trailing comment
         -v, --verbose            maximum output to screen
         -V, --version            print fillup version and exit
         -c | --char <char>       use <char> as comment marker
         -d | --delim <char>      use <char> as delimiter

         -m, --maintain           maintaining the basefile
         -x, --exchange           exchanging the basefile
         -r, --remove             removing within a copy


EXIT CODE

       fillup  returns  EXIT_SUCCESS  on  successful  completion.
       Otherwise,  an  exception  handler  is  called,  which may
       return EXIT_FAILURE;


COPYRIGHT

       fillup is copyright 1996,1997,1998,1999,2000,2001 by  SuSE
       GmbH,  Germany.   fillup  is  copyright  2002,2003 by SuSE
       Linux AG, Germany.

       There is NO warranty; not even for MERCHANTABILITY or FIT­
       NESS FOR A PARTICULAR PURPOSE.


AUTHOR

         Martin Scherbaum, maddin@suse.de (v1.04, 1996)
         Joerg Dippel,     jd@suse.de     (v1.05, 1998)
         Joerg Dippel,     jd@suse.de     (v1.06, 2000)
         Joerg Dippel,     jd@suse.de     (v1.10, 2002)
         Joerg Dippel,     jd@suse.de     (v1.21, 2003)

fillup                       Jan 2002                   FILLUP(8)
  
Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.


Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
You can choose larger fonts by selecting a different themes.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds