Skip to main content

Startup programs/services on Mac OS 10.5

UPDATE: This page has a better tutorial which I have adapted in this post.

From this page [osxfaq.com]:
  1. Startup commands are found under /Library/StartupItems/
  2. Each application has its own folder
  3. The folder has:
    XXX - A startup shell script
    StartupParameters.plist - A message and information file
    Resources - A folder with translations for strings etc.
  4. XXX is a shell script with root ownership e.g.:
    #!/bin/sh
    . /etc/rc.common
    ConsoleMessage "Starting RRiki"
    cd /path/to/rriki/
    rrikiserver &
  5. StartupParameters.plist is a text file with some info:
    {
    Description = "RRiki server";
    Provides = ("RRiki");
    Requires = ("MySQL");
    Uses = ("Ruby");
    OrderPreference = "Last"; (can be Late,Last,None)
    Messages =
    {
    start = "Starting RRiki server";
    stop = "Stopping RRiki server";
    };
    }


  6. sudo /sbin/service
    is the commandline way of manipulating services.

Labels:

Comments

  1. AnonymousJune 20, 2009 at 11:16 PM

    hi. Do startupitems still work in OS X 10.5.7?

    I am having trouble in OS X 10.5.7 and can't seem to get one to actually work.

    ReplyDelete

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or
Post a Comment
Read more

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty
Post a Comment
Read more