MAN Solaris - evolution (1)



evolution - A personal and workgroup information management solution. An integration of mailer, calendar and addressbook clients. Sun Microsystems Edition, Version 2.8



evolution [--debug=filename] [--force-shutdown] [--help] [--offline] [--online] [--usage] [--disable-eplugin] [--component=name] [--display-preview]




Evolution integrates email, calendar, contacts, and task list management in one application. Evolution provides full support for several data exchange and communication standards, such as IMAP, POP, SMTP, LDAP, iCalendar, and vCard. Evolution enables tight integration with Sun ONE Messaging and Calendar Servers and other messaging systems.


The following options are supported:

--debug=filename Send the debugging output of all components to a file specified by filename. filename is a path to a file. For example, /tmp/Evolution is a valid value for filename.

--force-shutdown Forcibly shut down all Evolution components.

-?, --help Display help text.

--offline Start in offline mode.

--online Start in online mode.

--usage Display brief usage text.

--disable-eplugin Disable loading of any plugins.

-c, --component=name Start Evolution activating the specified component.

--disable-preview Disable preview pane of Mail, Contacts and Tasks.


Example 1: To start Evolution activating the Calendar component

example% evolution -c calendar


The following exit values are returned:

0 Application exited successfully

1 Application exited with failure


The following files are used by this application:

/usr/bin/evolution Executable script for Evolution application

$HOME/.evolution Directory with per-user configuration files and local storage for Evolution


See attributes(5) for descriptions of the following attributes:

Interface stabilityVolatile


evolution-exchange-setup(1), libebook-1.2(3), libecal-1.2(3)


Ever since the upgrade Evolution from 1.4 to 2.x, this product includes source code for the Berkeley Database a product of Oracle Corporation. Your use of the Berkeley Database software separately from Evolution or authorized derivatives thereof is subject to additional licensing conditions.

Per-user configuration files and local storage in Evolution 2.x are stored in $HOME/.evolution directory as opposed to $HOME/evolution directory in Evolution 1.4. If the user had Evolution 1.4 installed on the system before, they are able to upgrade to Evolution 2.8 without losing configuration and local data. When run for the first time, Evolution 2.x will automatically check for and import all the old configuration and local data owned by Evolution 1.4, and convert them to the format readable by Evolution 2.x. Users are also allowed to choose between preserving the $HOME/evolution directory or not. If users choose to preserve configuration and local data for Evolution 1.4, they will have to manage Evolution 1.4 and Evolution 2.8 configuration and data separately, after the one-time migration. No automatic syncing is available for ensuring that changes made to Evolution 2.x are ported to Evolution 1.4, or vice versa.

The addressbook database formats of Evolution 2.x and Evolution 1.4 are different due to the use of different versions of Berkeley DB in the backend. User cannot simply copy the database file from Evolution 1.4 to Evolution 2.8 in order to do the porting of addressbook.

Written by Irene Huang, Sun Microsystems Inc., 2006.

Jump to page    or go to Top of page |  Section 1 |  Main Solaris Index.

SunOS 5.11 evolution (1) 7 Jun 2006
Generated by Open Solaris Forum from /usr/share/man/man1/evolution.1 using man macros with tbl support.