Bit again by the mail address meant to send to list. Grrr..
Mike Noyes wrote:
David,
Thanks for the suggestion. I'll run it by one of the SF staff members
this week. I'm not hopeful they'll allow this, though.
I'm not sure why not. When I say "user space", I mean cfengine can run
as
On Mon, 2006-04-17 at 11:39, KP Kirchdoerfer wrote:
> 3) Do you have opened adding docs and they'll included on a daily basis? we
> can add man pages and whatever independently. Do we have to respect some yet
> unkown rules (like adding as xml)?
KP,
I probably wasn't clear in my last post. :-(
On Mon, 2006-04-17 at 11:39, KP Kirchdoerfer wrote:
> Am Freitag, 14. April 2006 16:45 schrieb Mike Noyes:
> > Thank you for helping me generate this script. :-)
> >
> > crontab -e
> >
> > # LEAF project daily documentation build.
> > 35 2 * * * /home/groups/l/le/leaf/admin/
Hello Mike;
thx for your work.
Am Freitag, 14. April 2006 16:45 schrieb Mike Noyes:
> On Thu, 2006-04-13 at 20:20, Charles Steinkuehler wrote:
> > Looks good to me...once again, I can't comment on the document building
> > commands, but the overall script looks very robust.
>
> Charles,
> Thank y
On Thu, 2006-04-13 at 20:20, Charles Steinkuehler wrote:
> Looks good to me...once again, I can't comment on the document building
> commands, but the overall script looks very robust.
Charles,
Thank you for helping me generate this script. :-)
crontab -e
# LEAF project d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Noyes wrote:
> On Sat, 2006-04-08 at 13:05, Mike Noyes wrote:
>> I placed revision 1.12 in cvs yesterday. Please take a look at it if you
>> have a chance. Comments and feedback are welcome.
>
> Everyone,
> The formatting on this post should be a
On Sat, 2006-04-08 at 13:05, Mike Noyes wrote:
> I placed revision 1.12 in cvs yesterday. Please take a look at it if you
> have a chance. Comments and feedback are welcome.
Everyone,
The formatting on this post should be a bit better.
*** Begin doc-build.sh ***
#! /bin/bash
# PROGRAM:
# PURPO
On Wed, 2006-04-12 at 06:50, Charles Steinkuehler wrote:
> > I placed revision 1.12 in cvs yesterday. Please take a look at it if you
> > have a chance. Comments and feedback are welcome. If everyone thinks
> > it's usable, I'll enable it in crontab on Monday.
> >
> > RCS file: /cvsroot/le
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Noyes wrote:
> Everyone,
> I placed revision 1.12 in cvs yesterday. Please take a look at it if you
> have a chance. Comments and feedback are welcome. If everyone thinks
> it's usable, I'll enable it in crontab on Monday.
>
> RCS file: /
Everyone,
I placed revision 1.12 in cvs yesterday. Please take a look at it if you
have a chance. Comments and feedback are welcome. If everyone thinks
it's usable, I'll enable it in crontab on Monday.
RCS file: /cvsroot/leaf/sourceforge/admin/doc-build.sh,v
Next task: Mediawiki install.
On Wed, 2006-04-05 at 12:38, David Douthitt wrote:
> Mike Noyes wrote:
> > Instead of me running cron
> > jobs from my home directory, I'll now run them from our new admin
> > directory in our project space. All of our project members with project
> > shell access (group leaf) can now run doc-build
Mike Noyes wrote:
On Thu, 2006-03-30 at 13:47, Charles Steinkuehler wrote:
A lockfile as used by your
shell script is just a normal file in our SF project space, removable by
anyone with rights to delete the file (should at least be any project
admins, and could safely be any project develope
On Thu, 2006-03-30 at 16:03, Charles Steinkuehler wrote:
> I'd put the lockfile in the same temporary directory you're using to
> create the documentation.
Charles,
I've incorporated your suggestions, and placed r1.10 in cvs. I made one
successful run with the script. Please let me know if I made
On Sat, 2006-04-01 at 08:05, KP Kirchdoerfer wrote:
> Am Samstag, 1. April 2006 16:30 schrieb Mike Noyes:
> > Instead of me running cron
> > jobs from my home directory, I'll now run them from our new admin
> > directory in our project space. All of our project members with project
> > shell acces
Am Samstag, 1. April 2006 16:30 schrieb Mike Noyes:
> On Thu, 2006-03-30 at 13:47, Charles Steinkuehler wrote:
>
>
> > A lockfile as used by your
> > shell script is just a normal file in our SF project space, removable by
> > anyone with rights to delete the file (should at least be any project
On Thu, 2006-03-30 at 13:47, Charles Steinkuehler wrote:
> A lockfile as used by your
> shell script is just a normal file in our SF project space, removable by
> anyone with rights to delete the file (should at least be any project
> admins, and could safely be any project developer, IMHO). No
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Noyes wrote:
> On Thu, 2006-03-30 at 13:47, Charles Steinkuehler wrote:
>> A lockfile as used by your shell script is just a normal file in our SF
>> project space, removable by anyone with rights to delete the file
>> (should at least be any pr
On Thu, 2006-03-30 at 13:47, Charles Steinkuehler wrote:
> Mike Noyes wrote:
> NOTE: A cvs lock is *NOT* a lockfile. It is a lock placed on file(s)
> in the CVS repository by a that can only be removed by someone with full
> access to the CVS repository (ie: SF Staff).
Charles,
Thanks for clari
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Noyes wrote:
> On Thu, 2006-03-30 at 04:41, Charles Steinkuehler wrote:
>> Mike Noyes wrote:
>> > Ugh! They went on for quite a while on that thread. I'm not sure what
>> > discussed method was finally used..
>> >
>> > http://moongroup.com/piperm
On Thu, 2006-03-30 at 08:17, Mike Noyes wrote:
> On Thu, 2006-03-30 at 04:41, Charles Steinkuehler wrote:
> > I mentioned the -l switch to lockfile since I
> > wasn't sure if your removal of the lockfile when trying to grab it
> > failed was unintentional, or an attempt at forcibly grabbing it.
>
On Thu, 2006-03-30 at 04:41, Charles Steinkuehler wrote:
> Mike Noyes wrote:
> > Ugh! They went on for quite a while on that thread. I'm not sure what
> > discussed method was finally used..
> >
> > http://moongroup.com/pipermail/shell.scripting/2005-February/thread.html#9396
>
> The reason they'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Noyes wrote:
> On Wed, 2006-03-29 at 16:29, Mike Noyes wrote:
>> The easiest one I've seen so far is here:
>>
>> http://moongroup.com/pipermail/shell.scripting/2005-February/009396.html
>
> Charles,
> Ugh! They went on for quite a while on that
On Wed, 2006-03-29 at 16:29, Mike Noyes wrote:
> The easiest one I've seen so far is here:
>
> http://moongroup.com/pipermail/shell.scripting/2005-February/009396.html
Charles,
Ugh! They went on for quite a while on that thread. I'm not sure what
discussed method was finally used..
http://moongr
On Wed, 2006-03-29 at 16:02, Mike Noyes wrote:
> On Wed, 2006-03-29 at 15:23, Charles Steinkuehler wrote:
> > lockfile -l 72000 ...
> >
> > would force removal of any existing lockfile older than 20 hours.
>
> Ok. I made the changes in doc-build.sh r1.8. I hope I did it correctly.
Charles,
All
On Wed, 2006-03-29 at 15:23, Charles Steinkuehler wrote:
> Mike Noyes wrote:
> > Pending:
> > * feedback on shell code in doc-build.sh
>
> I finally got a few free minutes to look at this.
Charles,
Thank you for helping. :-)
> Your script looks very clean except for one issue with the c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Noyes wrote:
> On Wed, 2006-03-29 at 14:07, KP Kirchdoerfer wrote:
>> Am Mittwoch, 29. März 2006 23:13 schrieb Mike Noyes:
>> > Here is an early run of our new document build script. I'm using the
>> > default docbook xsl currently. I'll work on a
On Wed, 2006-03-29 at 14:07, KP Kirchdoerfer wrote:
> Am Mittwoch, 29. März 2006 23:13 schrieb Mike Noyes:
> > Here is an early run of our new document build script. I'm using the
> > default docbook xsl currently. I'll work on a customization layer after
> > initial build testing, etc. are complet
Am Mittwoch, 29. März 2006 23:13 schrieb Mike Noyes:
> Subject was: Re: [leaf-devel] Re: adding a new menu
>
> On Wed, 2006-03-29 at 10:17, Mike Noyes wrote:
> > Anyway, I'm now able to validate our docbook xml. I'll continue working
> > on the new build script.
>
> Everyone,
> Here is an early run
28 matches
Mail list logo