The reaons for the command line switches for the nowindow/log* would be to
override the channel settings. I would like if run fron cron different
options than if I brought up the GUI.
Robert OConnor said:
> On 24 Sep 2002 at 9:34, Wesley Mason wrote:
>> nowindow When updating from cron or any background process
>> I'd like it to be silent. Defaulting to a log file or
>> stdout. Channel failure should go to stderr.
>> logfile specify a log file to write to other than the default
>> logdir specify directory to put log file(s) in
>> logchan log parsing to log files based on section names
>> the other log file would contain info on what channels
>> worked/failed. (in some way someone could parse out the
>> sections)
>
> I agree 100% with these. I think they might be better off though as
> progress options in GUI, with the rest of these type of settings: i.e
> in addition to progress dialog and console window, there would be 2
> more additions to the list of where to show progress information: none,
> or to log. Or maybe just add 'none' to the list, and have a separate
> log checkbox so you can log any of dialog, none, or console window to a
> specified log file.
>
These below are for scriptability. I have already with some creative
scripting gotten the list of sections from the plucker.ini (I'll show why
at the end of the e-mail...). But it would be better if I didn't need to
rely on the plucker.ini and look to your program fir this information
since it maintains the plucker.ini.
Robert OConnor also said:
>> channels list all the channels one per line
>> sections list all sections one per line
>> chandue list all channels due one per line
>> secdue list all sections due one per line
>
> Is there a particular use of why you want these? Is it so you know what
> channels you can then update via a --update-selected? Or another tool
> to interface with it?
>
These also are for scriptability. But less required. Since with some
work, I probably could just run plucker-build.
Robert OConnor also said:
>> {options} set some of the config items temporarily from the command
>> line.
>> proxy would be one, maybe even console/progress option
>
> There might be a passthough of options available, but all the
> parameter/switches are pretty much designed to be set up in the GUI,
> then do some action with them later. There is always a capacity already
> available of using plucker-build if want to override the commandline
> options.
>
Glad you like the idea for status errors. They will come in helpful.
Robert OConnor also said:
>> status set exit status based on failure of channels (this should
>> not be an option, should always be set).
>> 1 = failed channel
>> 2 = more than one failed channel
>> 10 = no channels to process (none due)
>> 11 = can't write log file(s)
>> ...
>
> I agree 100% there should be better exit codes. Will have to work back
> through the program flow to keep track of them.
>
>> version return version info of this desktop
>
> The version and build date are on the top of a usage, but a version is
> certainly a common and hence expected option, so seems very reasonable.
>
> I'll add these into the TODO.
>
> Best wishes,
> Rober
> _______________________________________________
> plucker-list mailing list
> [EMAIL PROTECTED]
> http://lists.rubberchicken.org/mailman/listinfo/plucker-list
Now the reason I was asking for all this was currently I have a scripted
system to pluck all my channels. I would like to replace most of this
with 'plucker-desktop -d'. I currently have it look at the exist status
and if there was an error it would e-mail me the log file alerting me to
the failing channel.
EX:
---runoplucker--
#!/usr/bin/ksh
#
##
. ~/.profile
PATH=$PATH:/usr/local/bin
PLUCKERDIR=/export/store0/misc/PluckerOut
ALERT=wesmason
CHANNEL=`grep '^\[' ~/.pluckerrc | tr -d "[]\r" | fgrep -vf
~/.plucker/ignore | grep -w "$1"`
export CHANNEL PLUCKERDIR PATH
shift
if [[ "x$CHANNEL" != "x" ]]; then
# echo "====================================================="
# echo Running Channel \"$CHANNEL\"
# echo "Extra options: $*"
# echo "-----------------------------------------------------"
plucker-build --pluckerdir=$PLUCKERDIR -s $CHANNEL -f $CHANNEL $*
> $PLUCKERDIR/$CHANNEL.log 2>&1
ST=$?
# echo STATUS: $ST
if [[ "$ST" != "0" ]]; then
mailx -s "Plucker Error: $CHANNEL - Status: $ST" $ALERT
<$PLUCKERDIR/$CHANNEL.log
fi
else
echo "Channel $1 does not exist in ~/.pluckerrc."
fi
-----------------
The idea of using plucker-desktop would mean being able to better schedule
when these channels get updated. And a GUI interface to boot.
--Wes
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list
