Another note: *if* the
man 5 crontab
output correctly describes how *this* cron works, then
"In addition to LOGNAME, HOME, and SHELL, cron(8) will look
at MAILTO if it has any reason to send mail as a result of
running commands in ``this'' crontab. If MAILTO is
define
Philippe, if you're running this in a user crontab, ignore the indented stuff.
If this is in /private/etc/crontab, then you are asking cron to have the
user perl execute the command -e
And that will produce an error, which will pass through sendmail as
Sander points out.
You need to b
[EMAIL PROTECTED] (allan) wrote:
>thanks a lot for the head-file :-)
>
>i did what you said, moved HEAD,GET,POST and other lwp-named stuff into
>/usr/local/bin and moved binary head into /usr/bin.
>something still goes wrong in make - i simply dont get it :
>
>/usr/bin/ld: Undefined symbols:
>
but of course i want - thanks!!
Ken Williams wrote:
>
> [EMAIL PROTECTED] (allan) wrote:
> >im also trying to get started with mod:perl on osX
> >
> >below is a qoute from the cpan testers:
> >
> >>For a long time I couldn't get mod_perl to compile on Darwin. It
> >>turned out that when I insta
[EMAIL PROTECTED] (allan) wrote:
>im also trying to get started with mod:perl on osX
>
>below is a qoute from the cpan testers:
>
>>For a long time I couldn't get mod_perl to compile on Darwin. It
>>turned out that when I installed LWP (a prerequisite for running the
>>mod_perl tests) it created
[EMAIL PROTECTED] wrote:
>*This message was transferred with a trial version of CommuniGate(tm) Pro*
>Someone on this list pointed out to me where some mod_perl files could
>be found on MacOSX. How do you use those files to program mod_perl
>scripts? Where do you put your mod_perl scripts? I pe
On Monday, May 21, 2001, at 02:52 PM, Jim Cooper wrote:
> There was a big discussion of this last week,
>
> Jim Correia <[EMAIL PROTECTED]>
> was on the case
Unfortunately I still do not have the answer. Someone who was or is at
Apple built and configured perl correctly for the 10.0.0 rel
im also trying to get started with mod:perl on osX
below is a qoute from the cpan testers:
>For a long time I couldn't get mod_perl to compile on Darwin. It
>turned out that when I installed LWP (a prerequisite for running the
>mod_perl tests) it created /usr/bin/HEAD, which clobbered
>/usr/bin
At 2:41 PM -0400 5/21/01, Jim Correia wrote:
>On 2:37 PM 5/21/01 allan <[EMAIL PROTECTED]> wrote:
>
> > when i had the original macosX-shipped perl i never had this problem
> > so in a way it points to perl itself but then again - there are no
> > complaints when running programs directly from the
There was a big discussion of this last week,
Jim Correia <[EMAIL PROTECTED]>
was on the case
I have saved two terminals to the "MacPerl Support" folder in "BBEdit
Support"
the 6.1.2 docs says this name is supposed to change but it did not to
"Perl Support"
Anyway, when I choose run in t
Jim Correia wrote:
>
> On 2:37 PM 5/21/01 allan <[EMAIL PROTECTED]> wrote:
>
> > when i had the original macosX-shipped perl i never had this problem
> > so in a way it points to perl itself but then again - there are no
> > complaints when running programs directly from the commandline
>
> Per
On 2:37 PM 5/21/01 allan <[EMAIL PROTECTED]> wrote:
> when i had the original macosX-shipped perl i never had this problem
> so in a way it points to perl itself but then again - there are no
> complaints when running programs directly from the commandline
Perl as shipped with X doesn't have thi
> At 6:53 PM +0200 5/21/01, allan wrote:
> > > It's quite possible you're launching a new version of a shell, hence I'd
> > > guess to be sure your .cshrc (or-what-shell-have-you) should, mayhap
> > > have the environmental set (eg, setenv LANG "en_US")...
> >
> >i did that (before i installed per
>Should I reinstall the developer software, making sure I'm not leaving
>somthing out? (I can't remember if there is a 'custom' install possibility
>with the dev package that maybe I didn't check.) This might also fix the
>lack of echo when using CPAN. Am I the only one who gets this 'no-ech
At 6:53 PM +0200 5/21/01, allan wrote:
> > It's quite possible you're launching a new version of a shell, hence I'd
> > guess to be sure your .cshrc (or-what-shell-have-you) should, mayhap
> > have the environmental set (eg, setenv LANG "en_US")...
>
>i did that (before i installed perl 5.6.1)
>
>
The developer install doesn't have a customize option, so you get
everything. I don't know about this lack of echo, since I install Perl
modules manually, putting them in a non-standard place.
--
Edward Moy
Apple Computer,
It doesn't exist on my system, I do have a /System/Library/Perl/darwin/CORE
directory, but there is no perl.h anywhere on my computer, that I can find
(I used the 'find') command when logged in as root to make sure everything
was checked). The first thibg I did was install the developer packag
I seem to have /System/Library/Perl/darwin/CORE/perl.h on my system. Is
it that it doesn't exist on yours or it does, but you still get that error
message.
I would suppose that the include files in /System/Library/Perl/darwin/CORE
are not installed by default, but come from the developer pack
> It's quite possible you're launching a new version of a shell, hence I'd
> guess to be sure your .cshrc (or-what-shell-have-you) should, mayhap
> have the environmental set (eg, setenv LANG "en_US")...
i did that (before i installed perl 5.6.1)
setenv LC_ALL C
setenv LANG "en_US"
but the prob
At 6:42 PM +0200 5/21/01, [EMAIL PROTECTED] wrote:
>*This message was transferred with a trial version of CommuniGate(tm) Pro*
>Hello again,
>
>in your reply to my question regarding a potential conflict between
>MacOSX and cron, you said that "unless you've redirected STDOUT/ERR
>for the cron j
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Someone on this list pointed out to me where some mod_perl files could
be found on MacOSX. How do you use those files to program mod_perl
scripts? Where do you put your mod_perl scripts? I personally do not
think that th
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Hello again,
in your reply to my question regarding a potential conflict between
MacOSX and cron, you said that "unless you've redirected STDOUT/ERR for
the cron job, any output is mailed to the user who owns the cron jo
At 6:35 PM +0200 5/21/01, allan wrote:
>hello,
>
>i have posted this question on the bbedit mailing list, but maybe some
>of you guys know ...
>
>
>i have compiled perl 5.6.1 for osX, and perl programs behave as expected.
>
>when i from within bbedit 6.1 want to check syntax of a perl program or
>
hello,
i have posted this question on the bbedit mailing list, but maybe some
of you guys know ...
i have compiled perl 5.6.1 for osX, and perl programs behave as expected.
when i from within bbedit 6.1 want to check syntax of a perl program or
run it, i always get this annoying message:
perl
I've had the exact same problem, it's not a version 10.03 problem though,
this happened on 10.00 the same way. My CPAN has another 'issue' : when I
type into it it doesn't echo to the screen, not a big deal but pretty weird.
I know some perl on OS X geniuses out there have mentioned using CPAN
At 07.50 -0700 01-05-21, Daniel Lord wrote:
>Maybe it's in some release notes somewhere that I have missed, but
>has anyone noticed that the version variable is wrong?
>
>i.e, running the following program gives 'version=5.006' instead of
>the version shown by 'perl -v' , 'This is perl, v5.6.0 b
Maybe it's in some release notes somewhere that I have missed, but has
anyone noticed that the version variable is wrong?
i.e, running the following program gives 'version=5.006' instead of the
version shown by 'perl -v' , 'This is perl, v5.6.0 built for darwin' .
#!/usr/bin/perl
print "versi
At 4:37 PM +0200 5/21/01, Philippe de Rochambeau wrote:
>Hello,
>
>has anyone ever encountered a conflict between Perl 5.6.0 on MacOSX and cron?
>
>whenever I do crons such as
>
>0 3 * * * perl -e 'open(fh,"file.txt") or
>die; print fh "Hello"; close(fh)'
>
>I get an error
Hello,
has anyone ever encountered a conflict between Perl 5.6.0 on MacOSX and cron?
whenever I do crons such as
0 3 * * * perl -e 'open(fh,"file.txt") or die; print fh
"Hello"; close(fh)'
I get an error message in system.log stating that sendmail.cf has group
rights o
29 matches
Mail list logo
