Subscribe to
NSLog(); Header Image

Why Rivet will Probably Not be a System Service

RivetSeveral people on the Cynical Peak forums have asked for Rivet to run as a system-level service so that they can access their media when they're logged out.

There are a few problems with that request, not the least of which are:

  • Whose iTunes and iPhoto libraries do you parse when nobody's logged in?
  • How do you change preferences when nobody's logged in?
  • What about permissions issues? Do you really want Rivet running as root? Not likely.

There are other concerns as well, but those are the biggies. For the time being, Rivet will remain an application (in the menu bar). Just make use of fast user switching or even hop back to the login screen if you need to.

P.S. Rivet 1.1 is in the works and has undergone not one but two major networking overhauls to make it work with even more of the funkier setups we've seen from users. Current projection is to have 1.1 in beta in a few days, and released the last week of June.

One Response to "Why Rivet will Probably Not be a System Service"

  1. You could have it run at boot time, but use the user's account. I.e. Similar to how MySQL and Apache run as the mysql and www accounts, respectively.

    If multiple users are logged in, you would need to have multiple background processes - one per user.