rtinit [-s schema] [-qv] [db]
Running rtinit is only the first step; the user must then at least:
rtinit also recognizes a partially constructed directory, and endeavours not to overwrite any existing files.
% ls % rtinit /opt/antelope/data/db/demo/demo % ls bin/ dbmaster/ orb/ rtexec.pf state/ db/ logs/ pf/ rtsys/ % rtm % ls db/ dbmaster/ junk/ pf/ rtexec.pf % rtinit -v making bin db already exists. dbmaster already exists. making logs making orb pf already exists. making rtsys making state creating descriptor file for dbmaster/db descriptor file db/db already exists. network table already has a record. site table already has a record. rtexec.pf already exists pf/orb2db.pf already exists. pf/orbserver.pf already exists. pf/elog.pf already exists. pf/rtm.pf already exists. % ls bin/ dbmaster/ logs/ pf/ rtsys/ db/ junk/ orb/ rtexec.pf state/ % rtinit -s css3.1 example No database (descriptor file) example seems to exist % ls bin/ db/ dbmaster/ idserver/ logs/ orb/ pf/ rtexec.pf rtlogs/ rtsys/ state/ % ls db example % dbfilenames db/example database: db/example schema: css3.1 path: ../dbmaster locking: local idserver: relation #rows w? add? filename network 1 y y dbmaster/example.network site 1 y y dbmaster/example.site % cat dbmaster/example.site ZZZZ 2012306 -1 -999.0000000 -999.0000000 -999.0000 - - - 0.00000 0.00000 1351797685.72387
rtexec(1) rtexec_setup(5) install_boot_scripts(1) rt(5) rtsetup(8)
If the database from the command line does not exist, site and network tables are still created with a single record each containing dummy values.