{"id":16087016,"url":"https://github.com/noha/stone-creator","last_synced_at":"2025-10-23T02:31:46.936Z","repository":{"id":1677371,"uuid":"2404469","full_name":"noha/stone-creator","owner":"noha","description":"builds a directory to hold a new stone","archived":true,"fork":false,"pushed_at":"2011-09-17T10:58:26.000Z","size":102,"stargazers_count":3,"open_issues_count":0,"forks_count":2,"subscribers_count":3,"default_branch":"master","last_synced_at":"2024-12-18T21:28:52.512Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/noha.png","metadata":{"files":{"readme":"Readme","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2011-09-17T10:56:47.000Z","updated_at":"2023-10-09T12:21:30.000Z","dependencies_parsed_at":"2022-09-07T03:21:34.301Z","dependency_job_id":null,"html_url":"https://github.com/noha/stone-creator","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/noha%2Fstone-creator","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/noha%2Fstone-creator/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/noha%2Fstone-creator/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/noha%2Fstone-creator/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/noha","download_url":"https://codeload.github.com/noha/stone-creator/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":237769067,"owners_count":19363250,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-10-09T13:26:57.347Z","updated_at":"2025-10-23T02:31:41.670Z","avatar_url":"https://github.com/noha.png","language":"Shell","funding_links":[],"categories":[],"sub_categories":[],"readme":"stone creator util\n==================\n\nThe gemstone OO database can work with multiple stones/images. This little utility\nhelps creating new stones from a standard gemstone installation (2.4.4.1 at the time\nof writing).\n\ncreate a new stone\n-------------------------\n\n1. If you installed gemstone the usual way you ended up with gemstone being installed in\n   /opt/gemstone/product\n   In this case you can skip this step. If you installed your gemstone somewhere else than\n   you need to edit the file gemstone.conf and enter the path of your installation\n\n2. Invoke the helper script to create a stone. If you want to install a new stone with the\n   name \"saphir\" in a directory \"/opt/application/saphir\" and you want a virgin gemstone\n   copied in place than you need to invoke\n\n   ./create-stone.sh -n saphir -d /opt/application/saphir -f\n\nTo see all available commandline options just invoke\n  \n   ./create-stone.sh\n\nadd the start/stop script to the system\n---------------------------------------\n\nA system V start/stop script is created in the stone directory that can start/stop this\nsingle stone instance. The script has the same name as the stone. The example choice \nabove \"saphir\" would have led to a script called \"saphir\" in the stone directory. \n\n   ./saphir start|stop\n\nstarts or stops the stone instance. You can link this script into the system start\nscript directory\n\n   ln -s /opt/application/saphir/saphir /etc/init.d\n\nFor debian based systems you can do \n\n   update-rc.d saphir defaults\n\nThis will add the script to the normal runlevels so that it will be started if the\nmachine starts\n\n\ninvoking a local script\n-----------------------\n\nFor maintenance is often desirable to run a script against the stone. For this you use\nthe runTopazScript.sh script. Just create a smalltalk script with the form\n\nrun\n\u003cyour smalltalk script\u003e\n%\n\nYou can run this script by doing \n\n   sh bin/runTopazScript.sh myscript.st\n\nThe runTopazScript script is just a tiny wrapper around a topaz invocation. It reads an prepends \nthe login information to you script and pipes it to topaz. If you changed the password\nfor the DataCurator user in gemstone then you need to change that in the login.st file\n\nusing the environment provided\n------------------------------\n\nIf you like to have all of the configured variables active in your current working\nshell (e.g. to invoke commands like 'gslist -v') you can simply type\n\n   . ./env\n\nwhen you are in the stone directory\n\nQuestions, comments, feedback go to norbert@hartl.name\n\nmaintaining tranlog files\n-------------------------\n\nChanges commited to gemstone are added to a transaction log. The files are by default in the\nsame directory as the extent0.dbf file and have names like \"tranlogXX.dbf\" where XX is a\nnumber that increases whenever a new file is written.\nThe extent has information about what tranlog file it needs in order to be able to reconstruct\ndata after an unintentional shutdown. Over time new tranlog files are created and old one\nbecome obsolete. This wastes disk space without having any benfit.\n\nIn this distribution a script is included that can be used to delete old tranlog files. It\ndetects the last needed tranlog and deletes any older files that are obsolete. You can invoke\nit with\n\n   ./bin/delete-old-tranlogs.sh -d [directory] -g [path to gemstone] -r\n\nJust invoke the script without any arguments and you get the help printed. You can play with\nthe script. Unless you specify the -r (remove) argument the script only shows what it would\ndo. Nothing is done really. I added enough checks for a lot of conditions to be sure the \nscript does not do any unintentional delete of important data.  Although I took care you\nshould be very careful when invoking scripts that delete necessary data.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnoha%2Fstone-creator","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fnoha%2Fstone-creator","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnoha%2Fstone-creator/lists"}