archive-com.com » COM » O » ORCAWARE.COM

Total: 284

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Orca-dev Info Page
    list or change your existing subscription in the sections below Subscribing to Orca dev Subscribe to Orca dev by filling out the following form You will be sent email requesting confirmation to prevent others from gratuitously subscribing you This is a private list which means that the list of members is not available to non members Your email address Your name optional You may enter a privacy password below This provides only mild security but should prevent others from messing with your subscription Do not use a valuable password as it will occasionally be emailed back to you in cleartext If you choose not to enter a password one will be automatically generated for you and it will be sent to you once you ve confirmed your subscription You can always request a mail back of your password when you edit your personal options Once a month your password will be emailed to you as a reminder Pick a password Reenter password to confirm Which language do you prefer to display your messages English USA Would you like to receive list mail batched in a daily digest No Yes Orca dev Subscribers The subscribers list is only available to the

    Original URL path: https://www.orcaware.com/mailman/listinfo/orca-dev (2016-04-24)
    Open archived version from archive


  • Orca-users Info Page
    can subscribe to the list or change your existing subscription in the sections below Subscribing to Orca users Subscribe to Orca users by filling out the following form You will be sent email requesting confirmation to prevent others from gratuitously subscribing you This is a private list which means that the list of members is not available to non members Your email address Your name optional You may enter a privacy password below This provides only mild security but should prevent others from messing with your subscription Do not use a valuable password as it will occasionally be emailed back to you in cleartext If you choose not to enter a password one will be automatically generated for you and it will be sent to you once you ve confirmed your subscription You can always request a mail back of your password when you edit your personal options Once a month your password will be emailed to you as a reminder Pick a password Reenter password to confirm Which language do you prefer to display your messages English USA Would you like to receive list mail batched in a daily digest No Yes Orca users Subscribers The subscribers list is

    Original URL path: https://www.orcaware.com/mailman/listinfo/orca-users (2016-04-24)
    Open archived version from archive

  • Svnmerge Info Page
    or change your existing subscription in the sections below Subscribing to Svnmerge Subscribe to Svnmerge by filling out the following form You will be sent email requesting confirmation to prevent others from gratuitously subscribing you This is a private list which means that the list of members is not available to non members Your email address Your name optional You may enter a privacy password below This provides only mild security but should prevent others from messing with your subscription Do not use a valuable password as it will occasionally be emailed back to you in cleartext If you choose not to enter a password one will be automatically generated for you and it will be sent to you once you ve confirmed your subscription You can always request a mail back of your password when you edit your personal options Once a month your password will be emailed to you as a reminder Pick a password Reenter password to confirm Which language do you prefer to display your messages English USA Would you like to receive list mail batched in a daily digest No Yes Svnmerge Subscribers The subscribers list is only available to the list members Enter your

    Original URL path: https://www.orcaware.com/mailman/listinfo/svnmerge (2016-04-24)
    Open archived version from archive

  • System Configurations - SubversionWiki
    for a single machine in the above repository Note that we create dir directly in the repository not in any checked out working copy svn mkdir file svn configs macchina If you start off like this you can simply check out the empty directory to the root directory of your machine instead of checking out the repository root as described above In case you started like described above and only later thought about adding other machines you ll need to move your existing contents to the new location svn move file svn configs etc file svn configs macchina etc svn switch file svn configs macchina Make sure to first move the contents in the repository and only then switch your working copy because otherwise you might switch to an empty tree and all your versioned files would be deleted You can then create additinal directories for other machines and check them out to their root directory Let s suppose you are working on a machine called maschine You could do the following svn mkdir ssh svn root macchina svn configs maschine svn checkout ssh svn root macchina svn configs maschine Advanced tricks for multiple administrators and machines Note that the trick for logging the user by passing username to each command only works reasonably well with the file scheme It won t work with ssh access to another machine And it is easy enough to forget to provide your name We can solve all this and more by ab using the svn facility for defining tunnel applications On every machine where you want to manage the configuration using svn first create the following file named usr local bin svn sysadmin bin bash Taken from http www orcaware com svn wiki System Configurations if z SYSADMIN then SYSADMIN read p Your non root login name NAME dev tty dev tty echo NAME fi if z SYSADMIN then echo You need to give your name dev tty exit 1 fi exec usr bin ssh l sysadmin svn tunnel user SYSADMIN Make it executable chmod a x usr local bin svn sysadmin Register it in the tunnels section of your subversion config tunnels sysadmin usr local bin svn sysadmin On the machine where the reporitory is create a new user named sysadmin svn and make it owner of the repository chown R sysadmin svn svn configs To allow access to the repository it is probably most convenient to create a ssh public key for root on each machine using ssh keygen I would consider it safe enough to not use a passphrase as this key only protects access to the repository and if someone unauthorized managed to become root you are in trouble anyway You can then register all those keys in sysadmin svn ssh authorized keys on the machine with the repository to allow them all access to that account Now you can move your machine config to this new scheme svn switch relocate ssh svn root macchina svn configs maschine ssh

    Original URL path: https://www.orcaware.com/svn/wiki/System_Configurations (2016-04-24)
    Open archived version from archive

  • Subversion configured for Windows Active Directory HTTPS - SubversionWiki
    section or to anyone using the wildcard Each definition can grant read r access read write rw access or no access groups group1 harry sally group2 romeo julia group3 sally julia r group1 rw 6 Create a SSL certificate Openssl exe included with this version of Apache 2 2 does not seem to be configured well on windows In order to create a certificate you need a well configured version of openssl For this example configuration of subversion with https file Openssl 0 9 7e Win32 zip 1 combined with file openssl conf 2 were downloaded from support etouch net 3 run the following commands openssl req config openssl cnf new out svn example com csr openssl rsa in privkey pem out svn example com key openssl x509 in svn example com csr out svn example com cert req signkey svn example com key days 1000 copy the resulting cert and key files to the apache2 2 conf directory 7 Edit apache conf httpd conf LoadModule dav module modules mod dav so LoadModule dav svn module modules mod dav svn so LoadModule authz svn module modules mod authz svn so LoadModule ldap module modules mod ldap so LoadModule ssl module modules mod ssl so VirtualHost default 443 SSLEngine on SSLCipherSuite ALL ADH EXPORT56 RC4 RSA HIGH MEDIUM LOW SSLv2 EXP eNULL SSLCertificateFile conf svn example com cert SSLCertificateKeyFile conf svn example com key FilesMatch cgi shtml phtml php3 SSLOptions StdEnvVars FilesMatch Directory C Program Files Apache Group Apache2 cgi SSLOptions StdEnvVars Directory SetEnvIf User Agent MSIE nokeepalive ssl unclean shutdown downgrade 1 0 force response 1 0 redirect repos to repos RedirectMatch repos 1 Location repos DAV svn SVNPath c subversion repositories repo1 SVNParentPath c subversion repositories SVNListparentPath on Order allow deny Allow from all AuthType Basic AuthBasicProvider ldap AuthzLDAPAuthoritative off AuthName svn example com AuthzSVNAccessFile c subversion repositories svn authz at least one of your domain servers listens on port 3268 besides default ldap port 389 use the server that listens on port 3268 if you have more than one AD server The service on port 389 uses referrals to the other AD servers Referrals are used anonymously Anonymoys binding will not work on most AD servers AuthLDAPURL ldap dc example com 3268 DC example DC com sAMAccountName sub objectClass this assumes you have created a dedicated bind user apache bind on your active directory AuthLDAPBindDN CN apache bind CN users DC example DC com warning this password for AD apache bind user is in plain text AuthLDAPBindPassword password for ad user apache bind AuthLDAPFollowReferrals off AuthLDAPGroupAttributeIsDN on AuthLDAPGroupAttribute member SSLRequireSSL require ldap group CN svnusers CN Users DC example DC com require valid user Location VirtualHost 8 Apply ldap patch for MS AD When a Microsoft Active Directory times out it sends a TCP RST instad of a TCP FIN to the client There is a workaround for this MS AD bug in Apache mod ldap see http www apachelounge com forum viewtopic php t 1995 or download

    Original URL path: https://www.orcaware.com/svn/wiki/Subversion_configured_for_Windows_Active_Directory_HTTPS (2016-04-24)
    Open archived version from archive

  • Automatic lock-modify-unlock - SubversionWiki
    Visual 1 bin svnlook exe set TEMP c Progra 1 Visual 1 if exist TEMP tempfile 2 del TEMP tempfile 2 REM Identify all property updates and added files in current transaction and print them to tempfile for f tokens 1 usebackq i in SVNLOOK changed t 2 1 do if i A echo j TEMP tempfile 2 for f tokens 1 usebackq i in SVNLOOK changed t 2 1 do if i U echo j TEMP tempfile 2 REM If no property updates or file additions occurred go to the end of the script if not exist TEMP tempfile 2 goto NOFILESADDED REM For each file with these extensions listed in the tempfile check that it has the needs lock property set for f tokens usebackq i in findstr E I R bmp gif ico jpeg jpg png tif tiff doc jar odt pdf ppt swf vsd xls zip TEMP tempfile 2 do REM echo SVNLOOK propget t 2 1 svn needs lock i 1 nul 2 nul 1 2 SVNLOOK propget t 2 1 svn needs lock i 1 2 REM If the property wasn t set if ERRORLEVEL 1 REM Display a helpful error message to the user echo commit denied binary files must have property svn needs lock 2 type TEMP tempfile 2 2 del TEMP tempfile 2 EXIT B 1 del TEMP tempfile 2 NOFILESADDED EXIT B 0 2 Recursively set svn needs lock property on binaries If you need to apply svn needs lock on already existing binaries in a repository do the following on a client not on the svn server checkout a repository add to following line to a cmd script Windows only FOR R c full path to repository v in bmp gif ico jpeg jpg png tif tiff doc jar odc odf odg odi odp ods odt pdf ppt ser swf vsd xls zip do svn propset svn needs lock yes fv run the script 3 Configure users to automatically use svn needs lock property on new binary files New binary files should have the svn needs lock property set this is verified by the script of step 1 This can be achieved automatically if users configure their svn client config file under windows the SVN config file is C Documents and Settings USER NAME Application Data Subversion config Replace or merge the miscellany and auto props sections in the svn config file with the following miscellany enable auto props yes auto props The format of the entries is file name pattern propname value propname value The file name pattern can contain wildcards such as and All entries which match will be applied to the file Note that auto props functionality must be enabled which is typically done by setting the enable auto props option bmp svn mime type image bmp svn needs lock gif svn mime type image gif svn needs lock ico svn mime type image x icon svn needs lock jpeg svn mime type image jpeg svn

    Original URL path: https://www.orcaware.com/svn/wiki/Automatic_lock-modify-unlock (2016-04-24)
    Open archived version from archive

  • Server performance tuning for Linux and Unix - SubversionWiki
    subdirectories that don t grow past a specified size This allows repositories to store many more revisions than can efficiently be stored in one directory Modern filesystems can handle hundreds of thousands of files in a single directory However performance can suffer as the directory index starts to use multiple levels of indirection Some administration tools may also have trouble with very large directories Splitting the revision store into sub directories avoids all these problems The shard size can by adjusted by editing the layout sharded line in db format after svnadmin create but before populating the repository The default is 1000 revisions per subdirectory Non sharded repositories can be loaded into a new sharded repository using svnadmin load or svnsync Optimize write once files on NFS If the repository is on a NFS filesystem then a cache consistency check is made every time a file is opened Since the revision files in a FSFS repository never change it is worthwhile to skip the cache checks on these files The subversion 1 5 repository format store immutable files in specific subdirectories so that this can be done The NFS cache check can be disabled on Linux by passing the nocto option to the mount command note the man page claims this is ignored but it isn t on linux 2 6 You need coherency for some files so the NFS volume is also mounted without the option on a different mount point Symbolic links are made from the cache coherent mount point to the nocto mount for these directories revs and txn protorevs Implementation example not complete just an outline of the key steps stop all servers that can write to the repository sudo mount t nfs nfs server mount point mnt svn o rw nosuid tcp rsize 32768 wsize 32768 sudo mount t nfs nfs server mount point mnt svn nocto o rw nosuid tcp rsize 32768 wsize 32768 nocto actimeo 3600 cd mnt svn repo path mv revs revs nocto mv txn protorevs txn protorevs nocto ln s mnt svn nocto repo path db revs nocto revs ln s mnt svn nocto repo path db txn protorevs nocto txn protorevs start the servers Increase NFS caching timeout On Linux metadata on files from NFS is only kept for a finite period of time This can be changed by passing the actimeo option to the mount command The man page claims the default is 60 seconds but some experimentation suggests it may be higher than that For a nocto mount point this value can be raised to something much larger e g 3600 See the above example Distributing CPU load The subversion communicates with the clients by transmitting differences in state so the CPU load to calculate the difference can be significant By storing the repository on NFS you can have multiple front end FE systems that share the computational load and provide redundancy A network load balancer makes all front ends FEs appear as one server to users

    Original URL path: https://www.orcaware.com/svn/wiki/Server_performance_tuning_for_Linux_and_Unix (2016-04-24)
    Open archived version from archive

  • Svnmerge.py - SubversionWiki
    way it is when Subversion itself is shipped Thus the trunk version is recommended we believe it to be mostly stable there is a quite extensive testsuite Mailing List A svnmerge mailing list has been established The mailing list is the place to go for information about active development and new features List archives are available at OrcaWare GMANE marc info Nabble Development Patches bugfixes and development of svnmerge are all discussed on the mailing list Patches to svnmerge are also tracked using the svnmerge subcomponent on the Subversion bug tracker To submit a patch or bug report please follow the buddy system as described here but use the svnmerge mailing list Quick Usage Overview Use svnmerge init to initialize merge tracking on a branch directory Use svnmerge avail to review the revisions available for merging Use svnmerge merge to merge in some or all available revisions from other branches Commit the merge changes using svn commit Return to step 2 and repeat Quick tutorials What follows are two quick tutorials for two common usage cases Development branches This tutorial assumes that you are working on a recently created development branch made off the trunk It also assumes that the development branch has never merged changes from the trunk The svnmerge py command works as a pull operation so all commands are run from the development branch working copy This example pulls changes made on the trunk to your development branch Go to the top level directory of a pristine working copy of the branch if you re currently in a working copy directory containing trunk you can switch to the branch using svn switch url path to branch This is your development branch svnmerge py is meant to always operate in this condition so let me repeat top level directory no local modifications Initialize merge tracking support svnmerge py init This command will scan the branch history to find out when the branch was created so to initialize merge tracking support This needs to be done only once for each branch you want to use svnmerge py on You should run this command with in the top level directory of the branch otherwise it won t work as expected The svnmerge py init command added a property to the top level directory Since svnmerge py never does a commit it s your turn to commit that change to the repository You can use the handy automatically generated file svn ci F svnmerge commit message txt rm svnmerge commit message txt Or use your favourite commit message It s time to do a merge To merge everything from the trunk into the branch chdir to the top level of the branch and it s sufficient to do foo branch1 svnmerge py merge or without chdir foo svnmerge py merge branch1 and that s it You will always get the svnmerge commit message txt in the current directory Then review the merge fix any eventual conflict and commit There is a handy commit message listing the logs of all the merged revisions can be quite long which many people find useful According to the svn repository it may be necessary to nav into the directory above the working copy of the branch then name the branch in the svnmerge merge command so the sequence of init tracking merge would be for instance path to dir myworkingcopy svnmerge py init path to dir myworkingcopy svn ci F svnmerge commit message txt path to dir myworkingcopy cd path to dir svnmerge py merge myworkingcopy Repeat the last step whenever you want to merge new changes from the trunk If you want to have a look at what new changes are available to be merged from the trunk do this svnmerge py avail show only the revision numbers svnmerge py avail log show logs of the revisions on the trunk available for merging svnmerge py avail diff show diffs of the revisions on the trunk available for merging Release branches This tutorial assumes that you are working on a recently created release branch made off the trunk in which no changes were previously merged With release branch we mean a branch commonly used to stabilize a release only a few selected changes must be merged from the trunk the others must be ignored The svnmerge py command works as a pull operation so all commands are run from the release branch working copy This example pulls selected changes made on the trunk to your release branch Go to the top level directory of a pristine working copy of the branch svn copy trunk release cd release svnmerge py is meant to always operate in this condition so let me repeat top level directory no local modifications Initialize merge tracking support svnmerge py init This command will scan the branch history to find out when the branch was created so to initialize merge tracking support This needs to be done only once for each branch you want to use svnmerge py on svnmerge py never does a commit so it s your turn You can use the handy automatically generated file svn ci F svnmerge commit message txt rm svnmerge commit message txt Or use your favourite commit message Note however that svnmerge py generates the commit message directly from svn client s output so on Windows it ll have an OEM encoding You need to tell that to svn if your log messages contains non ASCII characters otherwise it ll assume an ANSI encoding and the message may be written incorrectly to the repository Then instead of the command above you should use svn ci encoding IBM850 F svnmerge commit message txt rm svnmerge commit message txt To know the current encoding used in the console one can use the chcp command Review changes available on the trunk to be integrated into the branch svnmerge py avail show only the revision numbers svnmerge py avail log show logs of the revisions svnmerge py avail

    Original URL path: https://www.orcaware.com/svn/wiki/Svnmerge.py (2016-04-24)
    Open archived version from archive



  •