Re: packaging help

ue, Apr 24, 2012 at 12:15 PM, Gergely Nagy wrote: > Whit Armstrong writes: > >>> I assume it has a main process, which when stopped, would result in the >>> workers being killed too. If that is so, I do not think you need to >>> store the pids of the workers anywhe

Re: packaging help

> I assume it has a main process, which when stopped, would result in the > workers being killed too. If that is so, I do not think you need to > store the pids of the workers anywhere. Perhaps I'm confusing terminology here. The main deamon does not spawn the workers. It and the workers are sta

Re: packaging help

:46 AM, Matt Zagrabelny wrote: > On Tue, Apr 24, 2012 at 8:16 AM, Whit Armstrong > wrote: >> Thanks, Daniel. >> >> I would be looking for 6-64999, assuming my package eventually >> made it into debian, I suppose it would need to have a 'globally >> a

Re: packaging help

Thanks, Daniel. I would be looking for 6-64999, assuming my package eventually made it into debian, I suppose it would need to have a 'globally allocated' uid. The idea is simply not to give users executing an R script on the machine root access. Regarding, reSIProcate, it's cdbs based? Wou

packaging help

First off, is this the right list to ask basic questions about packaging? I'm trying to package a small daemon that provdies a ZMQ remote execution facility for R. The code is here: https://github.com/armstrtw/deathstar.core I've read the package tutorials several times, but I'm having trouble f