Re: Conflict between MacOS X Perl 5.6 and cron?
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 message in system.log stating that sendmail.cf has group rights on it, etc. etc. on all unix systems that I am familiar with, unless you've redirected STDOUT/ERR for the cron job, any output is mailed to the user who owns the cron job. Since sendmail, in its out-of-the-box configuration on Mac OS X has some issues, that is why you are getting the error message. -s- I do not really see what sendmail.cf has to do with with Perl, especially when I do not use sendmail commands within my Perl scripts, as shown above. Perhaps there is some kind of conflict between Perl and the sendmail file which Communigate Pro creates during the installation process. -- sandor w. sklar unix systems administrator stanford university itss-css
Re: installing modules
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 --any ideas on how to get this working?? It would be much appreciated! -Aaron At 12:21 AM 5/13/01 -0800, nellA hciR wrote: i have tried to install several moudles, both using cpan and at the command line. i always get the following error, what am i missing/doing wrong? i just reinstall X (10.0.3) (You get this message, because MakeMaker could not find /System/Library/Perl/darwin/CORE/perl.h) thanks for any suggestions - hcir Made with a Mac! Aaron Lawson, Ph.D Linguistic Researcher MNIS-TextWise Labs, LLC (315)426-9311, ext. 260 [EMAIL PROTECTED]
re: mod_perl on MacOSX
*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 those files can be used since the version of Apache supplied with MacOS X does not include the mod_perl module (httpd -l does not list mod_perl). Philippe de Rochambeau
Re: Conflict between MacOSX and cron?
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 job, any output is mailed to the user who owns the cron job. Pardon my asking, but how do you redirect STDOUT/ERR for the cron job? I know how to redirect to STDERR within a Perl or Java script, but not within cron. * * * * * /i/am/the/command/running/in/cron /home/outputlog 2 /home/errorlog (or, if you don't want any output) ... * * * * * /i/am/the/command /dev/null 21 and so on ... Furthermore, simply replacing perl -e '... by /usr/bin/perl -e... seemed to solve the problem, although I am not yet quite sure what caused it. hmmm, I believe that when cron spawns a shell (which is what it does everytime it runs a command), it doesn't necessarily read your login files, so I suspect that the path variable used by that cron job did not contain /usr/bin; the error that cron tried to mail to you was probably something like: perl: command not found. it's always a good idea to use the full path in cron. Philippe de Rochambeau -- sandor w. sklar unix systems administrator stanford university itss-css
Re: perl in bbedit - LC_ALL LANG
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 problem is still there (only from bbedit) thanks allan
Re: installing modules
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 package. -- Edward Moy Apple Computer, Inc. [EMAIL PROTECTED] (This message is from me as a reader of this list, and not a statement from Apple.) On Monday, May 21, 2001, at 09:30 AM, Aaron Lawson wrote: 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 --any ideas on how to get this working?? It would be much appreciated! At 12:21 AM 5/13/01 -0800, nellA hciR wrote: i have tried to install several moudles, both using cpan and at the command line. i always get the following error, what am i missing/doing wrong? i just reinstall X (10.0.3) (You get this message, because MakeMaker could not find /System/Library/ Perl/darwin/CORE/perl.h)
Re: installing modules
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 package on both of my G4s, neither of them has perl.h in this directory. 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-echo' effect when using CPAN? It happens on both of my computers! -Aaron At 09:53 AM 5/21/01 -0700, Edward Moy wrote: 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 package. -- Edward Moy Apple Computer, Inc. [EMAIL PROTECTED] (This message is from me as a reader of this list, and not a statement from Apple.) On Monday, May 21, 2001, at 09:30 AM, Aaron Lawson wrote: 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 --any ideas on how to get this working?? It would be much appreciated! At 12:21 AM 5/13/01 -0800, nellA hciR wrote: i have tried to install several moudles, both using cpan and at the command line. i always get the following error, what am i missing/doing wrong? i just reinstall X (10.0.3) (You get this message, because MakeMaker could not find /System/Library/ Perl/darwin/CORE/perl.h) Aaron Lawson, Ph.D Linguistic Researcher MNIS-TextWise Labs, LLC (315)426-9311, ext. 260 [EMAIL PROTECTED]
Re: installing modules
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, Inc. [EMAIL PROTECTED] (This message is from me as a reader of this list, and not a statement from Apple.) On Monday, May 21, 2001, at 10:39 AM, Aaron Lawson wrote: 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-echo' effect when using CPAN? It happens on both of my computers!
Re: perl in bbedit - LC_ALL LANG
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 commandline Perl as shipped with X doesn't have this problem. I don't know how Apple built it or configured it to not have this problem (it did in development versions of the OS but that was fixed before it shipped). Anything you set in .cshrc or the like won't affect BBEdit since it inherits the environment from the Finder and loginwindow. Unless, mayhap, you specifically do a open bbedit from a terminal? Hmmm - now there's a clue. Perhaps the environmentals should be added to whatever startup profile the Finder and/or loginwindow uses!? Bohdan I don't know the answer other than reverting to 5.6 for the time being if you don't really need 5.6.1.
mod_perl - head - HEAD - lwp
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/head, which is necessary during the build process. When I cleared this up, mod_perl built tested flawlessly. how do one clear this up? thanks allan
Re: perl in bbedit - LC_ALL LANG
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 release. 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 The updater doesn't change the name of an existing folder. MacPerl Support is supported for the time being so we don't break people's installations. You can change the name to Perl Support. The MacPerl Support name won't be supported forever. Anyway, when I choose run in terminal, or Debug (which defaults to terminal) the message seems to be picking up the user variables from my own environment.min file (There are samples in /usr/share/init/tcsh/ written by Fred Sanchez) anyway, inside BBEDIT no one has yet pro-offered how BBEDIT is getting it's information... I include this quote from Jim Correia [EMAIL PROTECTED] That comes in the 5.6.0 version which he is running. and in the BBEdit document. However, magically after I saved the terminal snapshot in the Mac Perl folder... the terminal prints out my whole environment set-up. That is because the terminal invokes a shell which runs all of those initialization files. BBEdit invokes perl, and perl inherites BBEdit's environment. We are looking into where these environment variables are set for GUI apps and how you might adjust them, but the documentation is a bit lacking.
re: mod_perl on MacOSX
[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 personally do not think that those files can be used since the version of Apache supplied with MacOS X does not include the mod_perl module (httpd -l does not list mod_perl). mod_perl is included, but as a DSO (dynamically loaded) and not statically compiled in. You can use it by adding the following lines to your httpd.conf: LoadModule perl_module libexec/httpd/libperl.so AddModule mod_perl.c ------ Ken Williams Last Bastion of Euclidity [EMAIL PROTECTED]The Math Forum
Re: mod_perl - head - HEAD - lwp
[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 /usr/bin/HEAD, which clobbered /usr/bin/head, which is necessary during the build process. When I cleared this up, mod_perl built tested flawlessly. That's from me. You'll need to find someone with the proper 'head' binary (much easier than finding the source and compiling it yourself) and have them mail it to you as an attachment or whatever. Then move 'HEAD' into /usr/local/bin/ (along with GET and POST and a few lwp-* programs), and put the real 'head' into /usr/bin/. I can send you the 'head' binary if you want. ------ Ken Williams Last Bastion of Euclidity [EMAIL PROTECTED]The Math Forum
Re: mod_perl - head - HEAD - lwp
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 installed LWP (a prerequisite for running the mod_perl tests) it created /usr/bin/HEAD, which clobbered /usr/bin/head, which is necessary during the build process. When I cleared this up, mod_perl built tested flawlessly. That's from me. You'll need to find someone with the proper 'head' binary (much easier than finding the source and compiling it yourself) and have them mail it to you as an attachment or whatever. Then move 'HEAD' into /usr/local/bin/ (along with GET and POST and a few lwp-* programs), and put the real 'head' into /usr/bin/. I can send you the 'head' binary if you want. ------ Ken Williams Last Bastion of Euclidity [EMAIL PROTECTED]The Math Forum
Re: Conflict between MacOS X Perl 5.6 and cron?
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 be sure that something good happens when you--as the user for whom cron is executing the task-- echo Test | mail -s some subject root (or perhaps the user whose user crontab is being dealt with in place of root). As Mac OS X is shipped, there is a group write permission on / . sendmail annoyingly but wisely doesn't like that, since, obviously / is in the path to sendmail's configuration file. sudo chmod g-w / will deal with that (each Mac OS X update so far has put the group write back onto /). Then, you'll get a different error if the significant username is root: Apple shipped root with a .forward file containing /dev/null This does achieve discarding the message...it also puts a complaint into system.log about the . I've changed my Mac OS X so that mail to root is shipped off to an ISP account (full time connection makes that feasible). --John At 7:38 -0700 5/21/2001, Sandor W. Sklar wrote: 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 message in system.log stating that sendmail.cf has group rights on it, etc. etc. on all unix systems that I am familiar with, unless you've redirected STDOUT/ERR for the cron job, any output is mailed to the user who owns the cron job. Since sendmail, in its out-of-the-box configuration on Mac OS X has some issues, that is why you are getting the error message. -s- I do not really see what sendmail.cf has to do with with Perl, especially when I do not use sendmail commands within my Perl scripts, as shown above. Perhaps there is some kind of conflict between Perl and the sendmail file which Communigate Pro creates during the installation process. -- sandor w. sklar unix systems administrator stanford university itss-css -- John Baxter [EMAIL PROTECTED] Port Ludlow, WA, USA
