Adding the Sparrow user group list here, since this question may be helpful to others!
If you want to run sleep tasks, you'll probably want to write your own frontend and backend, which will be similar to the proto frontend/backend (except that instead of running a CPU-intensive computation for some period of time, they'll just sleep).
The use of the backend is to actually run the tasks. An application running with Sparrow has 3 components. There is a Sparrow Daemon running on each machine; each Sparrow Daemon includes a Scheduler (which schedules tasks) and a NodeMonitor, which monitors what's running on the machine, ensures that some maximum number of tasks are running, and communicates with other schedulers that are trying to run tasks. Now, applications are decomposed into a frontend and a backend. The frontend submits jobs to the Sparrow scheduler. A backend runs on each worker machine; when a Sparrow daemon on a worker machine is assigned a task to run on the machine, it passes the task description (which is opaque to Sparrow) to the worker. You can see this if you look at the ProtoBackend code -- the ProtoBackend implements the launchTask method (part of the BackendService interface), which the Sparrow node monitor uses to pass tasks to the backend. To run sleep tasks, you'll want to replace the code in runBenchmark in the ProtoBackend to sleep for a period of time (most of the other code in ProtoBackend is for logging purposes -- it records how many tasks were launched and the rate of task launch for debugging purposes).
You're exactly right that, without a configuration file, the frontend will use a default configuration.
I'm guessing the problem that you're having has to do with inconsistency in how the hostname is represented. Can you send the full log messages?