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

 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

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

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

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




       scpm  [-q] [-v] [-f] [-s] command [command_options] [argu­


       scpm enables your system to hold multiple  configurations,
       e.g. different network settings. This is especially useful
       for notebook computers which may be periodically connected
       to  different  networks.   For a more detailed description
       and a usage howto please have a look at the info  documen­


       SCPM 0.9 is the latest release of SCPM, and so it has some
       new features and surely a lot of new bugs.  At  least  the
       features are nameable:

   new concept: Resoure Groups
       Resource  Groups  are the successors of Resource Sets. The
       intention is to logically group resources together so  the
       user does not have to care about which services need which
       configuration files.  See info documentation for  details.

   support for non root users
       Normal users can now perform switching. This is especially
       useful for users who do not  administrate  their  machines
       themselves. See info documentation.

   extended switch script support
       The  prior  SCPM  version  had already support for running
       user scripts at certain points of the script process,  but
       those  scripts had no access to SCPM data and no possibil­
       ity to influence the further switch process. Now there  is
       a script environment wich provides some data.  Please have
       a look in the info documentation for further  information.

       This  is  something  SCPM should have had earlier. Locking
       prevents you from running multiple SCPM processes  concur­
       rently.  This should help to hold your data consistent. In
       fact, the main intention for this is to have  a  mechanism
       to  prevent  SCPM  from  corrupt  your system in case SCPM
       crashed or aborted unexpectetly. In case this happens  and
       SCPM  moans  about  a lock already exists but no SCPM pro­
       cesses are  running  anymore,  just  remove  the  lockfile
       /var/lib/scpm/#LOCK  and  run `scpm -s reload' afterwards.
       Then you should have a sane system again.

       -v Verbose mode. This option does nothing at the moment.

       -f Force action. Actually only useful with the switch  and
       enable  commands.   Prevents  SCPM  from asking questions,
       saves all pending changes.

       -s Skip mode. Actually only useful  with  the  switch  and
       enable  commands.   Prevents  SCPM  from asking questions,
       drops all pending changes.

       -d Log debug messages.

       -b Boot mode. This modifies the way a  profile  switch  is
       performed  by  skipping  the  start/stop resource actions.
       This is usually run from /etc/init.d/boot.scpm  on  system
       start up.

       -w  Exit on warning. This lets SCPM terminate on warnings,
       not only on errors.

       -x Force loading of database even if  version  numbers  do
       not match. You should not need that.


       Prints the active profile to stdout.

   add {profile}
       Creates  a new profile named profile.  The actual configu­
       ration of your system is taken for the new profile.

   copy {source_profile} {destination_profile}
       Creates a copy of the profile source_profile with the name

   delete {profile}
       Delete  the  profile named profile.  This is not undoable.
       You cannot delete the active and the default profiles.

       This completely disables the  SCPM  on  your  system.  The
       existing profiles are not going to be deleted.

       In case you are running SCPM for the first time, this will
       set up SCPM on your system and the default profile will be

       Not yet implemented.

       This reloads the current profile. Useful if you did  local
       modification you want to drop or apply to the current pro­
       file. You can also use the

       Similar to `reload', but only performs saving of  modified
       resources.  Nothing  gets  restored  and  no  services get
       started or stopped.

   rename {profile} {new_profile}
       Renames profile to newprofile.

       The set command lets  you  add  or  remove  a  description
       to/from the active profile and gives you the possiblity to
       add scripts to a profile  that  are  executed  at  certain
       times  while a profile switch is performed.  Please have a
       look at the info page for more details.

       The get command is the counterpart of the set comand, that
       means you can query the stuff you have set with it.

   switch [-r|-g] {profile}
       This performs a switch form the actual profile to profile.
       If working in default mode, this may ask you if  you  want
       to  save possible changes. You will get prompted for every
       modified resource that is under SCPM control. You can  use
       the  '-s'  and  '-f'  options  to prevent SCPM from asking
       questions and drop/save all changes.  After that the  data
       of  the  destination  profile is restored and services are
       stopped/started accoring to the  new  profile's  settings.
       The  command  options  '-r' and '-g' stand for show single
       resources and  show  resource  groups.   Default  is  '-g'
       unless no resource groups are being used.

   db {command}
       With   no  command  given,  this  enters  the  interactive
       database manipulation utility.  This utility has an online

   deactivate_group {group}
       Deactivates  the  resource  group  group  and  removes all
       resources of this group from the  database  and  all  pro­


       In  this  file all data regarding your profiles, resources
       etc is located. It should not be modified manually!

       This directory is used to save the resource data  for  the
       different profiles.

       The  SCPM  configuration  file.  You  can customize SCPM's
       behaviour here. The file is a  standard  KEY=VALUE  config
       file, which may contain the following keys:

       Specifies where the database should be read from and writ­
       ten to.  Defaults to /var/lib/scpm/scdb/scdb.db.

       Specifies where the SCPM subsystem has been installed  to.
       This defaults to /lib/scpm.

       Defines  where  SCPM  should  log to. This may be a normal
       file specification or syslog for logging  via  syslogd  or
       empty for logging to stderr.

       Using  this  variable  you can define a resource set which
       SCPM should use. Up to  SCPM  0.6  the  whole  system  was
       searched  for resources and from this information the SCDB
       was generated.  A  resource  set  defines  what  resources
       'exist'  and  so  you  can  reduce  the  database  to that
       resources you really want to have  under  profile  manage­
       ment.  There is a predefined resource set called `typical'
       which defines only a  small  set  of  resources.  You  can
       adjust  that by copying /lib/scpm/resource_sets/typical to
       /var/lib/scpm/resource_sets/ and modify that  file  after­
       wards.  The resource set `typical' is also the default now

       When  determining  the resource list for the resource type
       file, files that match one of the pattern  specified  here
       will    be   excluded   from   the   list.   Defaults   to
       /lib/scpm/resource_types/file/exclude.  The  patterns  are
       normal shell patterns.

       When  determining  the resource list for the resource type
       file, files that match one of the pattern  specified  here
       will    be    added    to    the    list.    Defaults   to
       /lib/scpm/resource_types/file/extra.   The  patterns   are
       normal  shell  patterns.  The extra patterns are processed
       after the exclude patterns, so you  can  add  files  here,
       which are normally excluded by the built in list.

       The  same  as  FILE_EXCLUDE_PATTERN  but  for  the service
       resource type.

       The  same  as  FILE_EXTRA_PATTERN  but  for  the   service
       resource type.

       With  this  variable you can set the default behaviour for
       the switch command. Normally, SCPM asks  you  whether  you
       want  to save or drop modified resources. Using the -f and
       -s (force an skip) switches, you  can  prevent  SCPM  from
       asking  questions.  Setting  the  SWITCH_MODE  variable to
       force and skip does basically the same (you  can  override
       with  the  command  line  options, of course). Leaving the
       variable empty or setting it to normal lets  SCPM  operate
       as usual.

       Specified  the  SCPM  behaviour  on boot time. In case you
       gave a parameter PROFILE=profile_to_boot_into on the  LILO
       command  line,  SCPM  will restore the profile data of the
       given profile before the services are started.  If you set
       BOOT_MODE  to force your actual configuration (that means,
       the  configuration  before  you  rebooted/shut  down  your
       machine)  will  get  saved  before the wanted profile gets
       restored. If you set it to skip changes get dropped.   You
       can  also set it to backup which will create a backup pro­

       For people who want to have more control over what's  hap­
       pening, here comes a description for manually updating:

       After  updating, the database may be in an old format ver­
       sion. So first of all call

       `scpm db convert'

       This will rewrite the database in  the  new  format.  Then

       `scpm db maximize'

       This  will add some resources which SCPM 0.6 did not found
       (mainly files living in /etc/sysconfig). Finally call

       `scpm db rebuild_deps'

       This re-determines the dependencies for all resources.

       In case you have decided to use a resource set  (see  sec­
       tion  about  FILES,  subsection /etc/scpm.conf) you surely
       want  to  run  `scpm  db  clean'  now.  This  removes  all
       `deleted'  resources,  which includes all resources, which
       are not in the resource set.


       In case you did an  operation  system  update,  SCPM  will
       detect  this  (at least, it should so) and refuse to work.
       Background: the configuration data saved in your  profiles
       are not updated by the system update routines. That means,
       switching to the profiles may have unwanted results. Until
       now  we  did  not  reveal  an resonable and generic way to
       achive updating of the profile configuration data. So  the
       safe  way is to set up SCPM on your system again, at least
       for now.


       This manpage is  far  from  being  complete.  For  further
       information  about  command  options please have a look at
       the texinfo documentation.


       © 2002,2003 SuSE Linux AG Nuernberg

       SCPM is released under the terms of the GNU General Public
       License.  That  means  you  are  allowed  to modify and/or
       redistribute it under certain conditions.  Refer  to  your
       most favourite copy of the GPL on your system.



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 help in many different ways.


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.16 Seconds