Le Monday 27 February 2006 20:55, Ryan Novosielski a écrit :
> That would be my first reaction too -- jobuid is the uid that the job
> will run as. While there currently isn't this capability that I'm aware
> of, and I guess it's questionable whether it would ever be needed (ie.
> if you'd WANT the
> I my mind, uid and jobuid are not the same thing but we can
> also call it jobuuid ?
> (uuid stands for a Universal Unique IDentifier)
That would work.
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that
> > We can call it "jobuid" ?
>
> Yes. That is really nice. It is exactly what I was looking
> for. Thanks.
How about "jobseq" or "jobserial"? My first reaction to "jobuid" is "the
uid that this job runs under".
---
This SF.Net email is s
On Tuesday 28 February 2006 09:45, BOLLENGIER Eric wrote:
> Le Monday 27 February 2006 20:55, Ryan Novosielski a écrit :
> > That would be my first reaction too -- jobuid is the uid that the job
> > will run as. While there currently isn't this capability that I'm aware
> > of, and I guess it's que
That would be my first reaction too -- jobuid is the uid that the job
will run as. While there currently isn't this capability that I'm aware
of, and I guess it's questionable whether it would ever be needed (ie.
if you'd WANT the fd to somehow read files as an unprivileged user if it
were poss
On Monday 27 February 2006 15:41, David Boyes wrote:
> > > We can call it "jobuid" ?
> >
> > Yes. That is really nice. It is exactly what I was looking
> > for. Thanks.
>
> How about "jobseq" or "jobserial"? My first reaction to "jobuid" is "the
> uid that this job runs under".
Since very few use
Hi,
> 3. The Job (a unique identifier for a job that runs). The Job looks
> something like kernsave.2006-02-25_12.38.07. I.e. it is a combination of
> the Job Name and the date/time the job ran. No two jobs start at the same
> time, so it is unique -- providing you never use the same JobName in
On Sunday 26 February 2006 19:12, Eric Bollengier wrote:
> Hi,
>
> > 3. The Job (a unique identifier for a job that runs). The Job looks
> > something like kernsave.2006-02-25_12.38.07. I.e. it is a combination of
> > the Job Name and the date/time the job ran. No two jobs start at the
> > same
On Sunday 26 February 2006 15:36, Eric Bollengier wrote:
> Hi,
>
> I have to run jobs in a synchronous way for integrate them into a complex
> network scheduler (RunBefore and RunAfter are not sufficient for me)
>
> I want to add 2 options on wait command.
> - jobid=nnn
> - job=xxx
>
> My patch a
