In a remo te system, the administrator will also have to verify the usual conditions for working in remote systems: the user will have to have an account in the machine where the server resides, and the name of the client host must appear in the file /etc/hosts.equiv in the same machine.
In both cases the server handles the security using the permissions for users and groups provided by the UNIX OS, and also with the permissions assigned in the definition of each database.
The transaction consistency is more solid, because it assures that all the transactions are completed and stored in disk. This type of checkpoints can only be performed when there are no active transactions.
The server can be configured to perform transaction consistency checkpoints at regular intervals, using some of the parameters of the .sv file. For more information on this topic, see ``Installation'' on page 11.
Manual checkpoints can also be performed with the chkpoint tool. If no parameters are passed to this tool, the cache consistency is assured. If the ``-t''parameter is passed, the consistency is assured at transaction level. If the journal is deactivated, the only type of checkpoint available is the transaction consistency checkpoint.
Finally, it is important to mention that some IDEAFIX tools have parameters to perform a checkpoint when they finish their task. Of those, the most importants are dgen and iql, that have the ``-k''option.
Each time a new schema is created, the new information will not be available to the users until a checkpoint is performed. The ``-k''option assures that the checkpoint is performed immediatly and then that the new schemas are accesible.