Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #737
Difficulty: Medium
In 1979, the TRS-80 had the largest selection of software in the microcomputer market.
True or False?
Linux & Unix Commands - Search Man Pages

msynctool(1) [suse man page]

msynctool(1)							       Sync							      msynctool(1)

msynctool - Command line interface for OpenSync SYNTAX
msynctool option [arguments] [option] msynctool --sync SYNC_GROUP DESCRIPTION
Command line interface for OpenSync You can use this tool to synchronize your devices and applications using the OpenSync framework from the command line. - First you have to create a SYNC_GROUP: msynctool --addgroup evo2-sync - Now you have to add the members to this group. (2 at least) Note: The first argument to the --addmember command is the group to which you want to add a member, the second argument is the name of the plugin to add. msynctool --addmember evo2-sync evo2-sync msynctool --addmember evo2-sync file-sync - The next thing you have to do is to configure the plugins. msynctool --configure evo2-sync 1 (configures the first group member) msynctool --configure evo2-sync 2 (configures the second group member) - Now your group is ready for usage! msynctool --sync evo2-sync OPTIONS
--listgroups Lists all groups --listplugins Lists all plugins --listobjects Lists all objtypes that the engine understands objtypes: contact, data, event, note, todo --showformats objtype Lists all formats that a objtype can have --showgroup groupname Lists all members of the group --sync groupname Sync all members in a group --filter-objtype objtype Filter out objtype For example, the following syncs only contacts: msynctool --sync evo2-sync --filter-objtype event --filter-objtype note --filter-objtype todo Note: if you use "--filter-objtype data" it syncs nothing !? --slow-sync objtype Perform a slow-sync of all members in the group [--wait] Don't immediately start to sync, but wait for a client to initialize the sync [--multi] Repeat to wait for sync alerts --addgroup groupname Add a new group --delgroup groupname Delete the given group --addmember groupname plugintype Add a member to the group --configure groupname memberid Configure a member. memberid as returned by --showgroup [--manual] Make manual engine iterations. Only for debugging [--configdir] Set a different configdir than ~/.opensync [--conflict 1-9/d/i/n] Resolve all conflicts as side 1-9 wins, duplicate, ignore, or keep newer ENVIRONMENT VARIABLES
OSYNC_TRACE When you want to provide trace files please turn on tracing like this: export OSYNC_TRACE=/path/to/log/dir When you run some opensync commands now, opensync will generate a couple of Thread*.log files in this directory. You can exclude sensitive data in the trace files with: export OSYNC_PRIVACY=1 SEE ALSO
convcard(1),file-sync.conf(5) AUTHORS
This manual page was written for the Debian GNU/Linux project by Matthias Jahn <>. But it may be used by other distributions. msynctool was written by Armin Bauer and the OpenSync project Armin Bauer 0.19 msynctool(1)

Check Out this Related Man Page


glClientWaitSync - block and wait for a sync object to become signaled C SPECIFICATION
GLenum glClientWaitSync(GLsync sync, GLbitfield flags, GLuint64 timeout); PARAMETERS
sync The sync object whose status to wait on. flags A bitfield controlling the command flushing behavior. flags may be GL_SYNC_FLUSH_COMMANDS_BIT. timeout The timeout, specified in nanoseconds, for which the implementation should wait for sync to become signaled. DESCRIPTION
glClientWaitSync causes the client to block and wait for the sync object specified by sync to become signaled. If sync is signaled when glClientWaitSync is called, glClientWaitSync returns immediately, otherwise it will block and wait for up to timeout nanoseconds for sync to become signaled. The return value is one of four status values: o GL_ALREADY_SIGNALED indicates that sync was signaled at the time that glClientWaitSync was called. o GL_TIMEOUT_EXPIRED indicates that at least timeout nanoseconds passed and sync did not become signaled. o GL_CONDITION_SATISFIED indicates that sync was signaled before the timeout expired. o GL_WAIT_FAILED indicates that an error occurred. Additionally, an OpenGL error will be generated. NOTES
glClientWaitSync is available only if the GL version is 3.2 or greater. ERRORS
GL_INVALID_VALUE is generated if sync is not the name of an existing sync object. GL_INVALID_VALUE is generated if flags contains any unsupported flag. SEE ALSO
glFenceSync(), glIsSync() glWaitSync() COPYRIGHT
Copyright (C) 2010 Khronos Group. This material may be distributed subject to the terms and conditions set forth in the Open Publication License, v 1.0, 8 June 1999. [FIXME: source] 05/30/2012 GLCLIENTWAITSYNC(3G)

Featured Tech Videos