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".
  • Ocaml-pxp-users Administrator Authentication
    otherwise no administrative changes will take effect Session cookies are used in Mailman s administrative interface so that you don t need to re authenticate with every administrative operation This cookie will expire automatically when you exit your browser or you can explicitly expire the cookie by hitting the Logout link under Other Administrative Activities which you ll see once you successfully log in Ocaml pxp users list run by

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


  • Ocaml-pxp-users list: member options login page
    unsubscribe from this list click on the Unsubscribe button and a confirmation message will be sent to you Important From this point on you must have cookies enabled in your browser otherwise none of your changes will take effect Email address Password Unsubscribe By clicking on the Unsubscribe button a confirmation message will be emailed to you This message will have a link that you should click on to complete

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

  • Svnmerge Administrator Authentication
    browser otherwise no administrative changes will take effect Session cookies are used in Mailman s administrative interface so that you don t need to re authenticate with every administrative operation This cookie will expire automatically when you exit your browser or you can explicitly expire the cookie by hitting the Logout link under Other Administrative Activities which you ll see once you successfully log in Svnmerge list run by blair

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

  • System Configurations - SubversionWiki
    a single repository than different repositories Now let s create a directory 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

    Original URL path: https://www.orcaware.com/svn/mediawiki/index.php?title=System_Configurations&oldid=1631 (2016-04-24)
    Open archived version from archive

  • Log in - SubversionWiki
    logging in Forgot your password Retrieved from https www orcaware com svn wiki Special UserLogin Navigation menu Personal tools 81 198 240 36 Talk for this IP address Log in Namespaces Special page Variants Views More Search Navigation Main page

    Original URL path: https://www.orcaware.com/svn/mediawiki/index.php?title=Special:UserLogin&returnto=System+Configurations (2016-04-24)
    Open archived version from archive

  • Talk:System Configurations - SubversionWiki
    index php title Talk System Configurations oldid 1618 Navigation menu Personal tools 81 198 240 36 Talk for this IP address Log in Namespaces Page Discussion Variants Views Read View source View history More Search Navigation Main page Recent changes Random page Help Tools What links here Related changes Special pages Printable version Permanent link Page information This page was last modified on 11 June 2007 at 01 52 Content

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

  • View source for System Configurations - SubversionWiki
    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 tt maschine tt 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 tt username tt to each command only works reasonably well with the tt file tt 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 tt usr local bin svn sysadmin tt bin bash Taken from http www orcaware com svn wiki System Configurations if nowiki z SYSADMIN nowiki then SYSADMIN read p Your non root login name NAME dev tty dev tty echo NAME fi if nowiki z SYSADMIN nowiki 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 tt nowiki tunnels nowiki tt section of your tt subversion config tt tunnels sysadmin usr local bin svn sysadmin On the machine where the reporitory is create a new user named tt sysadmin svn tt 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 tt ssh keygen tt 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 tt sysadmin svn ssh authorized keys tt 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

    Original URL path: https://www.orcaware.com/svn/mediawiki/index.php?title=System_Configurations&action=edit (2016-04-24)
    Open archived version from archive

  • Revision history of "System Configurations" - SubversionWiki
    TkeXwy cur prev 10 03 14 July 2007 TkeXwy Talk contribs m 5 120 bytes 4 424 cur prev 06 18 11 June 2007 Martin von Gagern Talk contribs m 9 544 bytes 0 Typos cur prev 07 33 23 January 2007 Lamikae Talk contribs 9 544 bytes 75 fixed typo Simple case cur prev 06 41 8 January 2007 Martin von Gagern Talk contribs 9 469 bytes 1 942

    Original URL path: https://www.orcaware.com/svn/mediawiki/index.php?title=System_Configurations&action=history (2016-04-24)
    Open archived version from archive