From kevinc at gci.net Mon May 1 17:30:28 2000 From: kevinc at gci.net (K Creason) Date: Wed Aug 4 23:56:47 2004 Subject: Barnes and Noble deal Message-ID: <003d01bfb3bc$db24aa60$6000030a@k2> B&N has a great deal on their bargain table near the registers. It's the complete O'Reilly Perl package boxed and ready to go at $25, regularly $150. If I wasn't broke I would have bought them both and given one as a gift! Any buddy need a break from computing and want to buy my Harley project?? ;-) Computers can figure out all sorts of problems except the things in the world that just don't add up.--James Magoy ================================================= Mailing list info: If at any time you wish to (un|re)subscribe to the list send the request to majordomo@hfb.pm.org. All requests should be in the body, and look like such subscribe anchorage-pm-list unsubscribe anchorage-pm-list From prdugan at aurora.alaska.com Mon May 1 19:26:18 2000 From: prdugan at aurora.alaska.com (P. Dugan) Date: Wed Aug 4 23:56:47 2004 Subject: Barnes and Noble deal In-Reply-To: <003d01bfb3bc$db24aa60$6000030a@k2> Message-ID: <000101bfb3cd$089ae620$0100a8c0@Aurora> Thanks for the info on the books, the wife picked me up the last set. Philip > -----Original Message----- > From: owner-anchorage-pm-list@pm.org > [mailto:owner-anchorage-pm-list@pm.org]On Behalf Of K Creason > Sent: Monday, May 01, 2000 2:30 PM > To: anchorage-pm-list@happyfunball.pm.org > Subject: Barnes and Noble deal > > > B&N has a great deal on their bargain table near the registers. > It's the complete O'Reilly Perl package boxed and ready to go at $25, > regularly $150. If I wasn't broke I would have bought them both and given > one as a gift! > > Any buddy need a break from computing and want to buy my Harley project?? > ;-) > > Computers can figure out all sorts of problems except the things in the > world that just don't add up.--James Magoy > > ================================================= > Mailing list info: If at any time you wish to (un|re)subscribe to > the list send the request to majordomo@hfb.pm.org. All requests > should be in the body, and look like such > subscribe anchorage-pm-list > unsubscribe anchorage-pm-list > ================================================= Mailing list info: If at any time you wish to (un|re)subscribe to the list send the request to majordomo@hfb.pm.org. All requests should be in the body, and look like such subscribe anchorage-pm-list unsubscribe anchorage-pm-list From rox at tara-lu.com Fri May 5 14:05:27 2000 From: rox at tara-lu.com (Roxanne Reid-Bennett) Date: Wed Aug 4 23:56:47 2004 Subject: Using Net::LDAP::LDIF Message-ID: <39131B77.CB8D6442@tara-lu.com> Has anybody here used this package, and have a handy example? I'm getting an error that kind-of makes sense, and kind-of doesn't. perl code: Net::LDAP::LDIF->new(\*STDOUT,"w")->write($mesg->entries); error message: Can't locate object method "new" via package "Net::LDAP::LDIF" at ldap.pl line 33. I've tried breaking that line into two statements, the new and then the write, but the same error occurs for the "new". The only thing that makes sense to me is that the (\*STDOUT, "w") doesn't match the footprint for the constructor which should be : new ( [FILE [, MODE]] ) And at the moment I don't even remember where I found the example for writing out the ldap entries resulting from a query. So, anybody have any ideas? Rox -- Roxanne Reid-Bennett rox@tara-lu.com President, Tara-Lu Corporation http://www.tara-lu.com/ Quality brings its own reward. ================================================= Mailing list info: If at any time you wish to (un|re)subscribe to the list send the request to majordomo@hfb.pm.org. All requests should be in the body, and look like such subscribe anchorage-pm-list unsubscribe anchorage-pm-list From wolfm at pobox.alaska.net Fri May 5 14:42:43 2000 From: wolfm at pobox.alaska.net (Michael Fowler) Date: Wed Aug 4 23:56:47 2004 Subject: Using Net::LDAP::LDIF In-Reply-To: <39131B77.CB8D6442@tara-lu.com>; from rox@tara-lu.com on Fri, May 05, 2000 at 11:05:27AM -0800 References: <39131B77.CB8D6442@tara-lu.com> Message-ID: <20000505114242.Y539@shoebox.net> On Fri, May 05, 2000 at 11:05:27AM -0800, Roxanne Reid-Bennett wrote: > Has anybody here used this package, and have a handy example? Well, no, not really, but I may be able to help anyways. > I'm getting an error that kind-of makes sense, and kind-of doesn't. > > perl code: > Net::LDAP::LDIF->new(\*STDOUT,"w")->write($mesg->entries); > error message: > Can't locate object method "new" via package "Net::LDAP::LDIF" at ldap.pl line > 33. This error usually means you either haven't loaded the Net::LDAP::LDIF module (and thus didn't load any of the methods), or that the Net::LDAP::LDIF module really doesn't have that method. After taking a look at the module, and testing the new method, I see it -does- have the method, so I'm inclined to thing it's the former (that you didn't load the module). > I've tried breaking that line into two statements, the new and then the > write, but the same error occurs for the "new". The only thing that makes > sense to me is that the (\*STDOUT, "w") doesn't match the footprint for > the constructor which should be : new ( [FILE [, MODE]] ) No, that wouldn't do it. The only enforcement of a subroutine's arguments is through the prototyping mechanism, and prototyping doesn't work for methods (AFAIK). > And at the moment I don't even remember where I found the example for > writing out the ldap entries resulting from a query. Well, Net::LDAP may be more appropriate for this (I'm not sure what exactly you're doing, and I'm not terribly familiar with the whole ldap thing). The synopsis for the module shows what appears to be a good example of doing exactly that. Michael -- Administrator www.shoebox.net Programmer, System Administrator www.gallanttech.com -- ================================================= Mailing list info: If at any time you wish to (un|re)subscribe to the list send the request to majordomo@hfb.pm.org. All requests should be in the body, and look like such subscribe anchorage-pm-list unsubscribe anchorage-pm-list From corliss at odinicfoundation.org Fri May 5 15:55:44 2000 From: corliss at odinicfoundation.org (Arthur Corliss) Date: Wed Aug 4 23:56:47 2004 Subject: Using Net::LDAP::LDIF In-Reply-To: <20000505114242.Y539@shoebox.net> Message-ID: On Fri, 5 May 2000, Michael Fowler wrote: > On Fri, May 05, 2000 at 11:05:27AM -0800, Roxanne Reid-Bennett wrote: > > Has anybody here used this package, and have a handy example? > > Well, no, not really, but I may be able to help anyways. It's a misleading error. I've gotten this with several modules, and it usually comes down to an error the script. Something's bracketed wrong, or some other type of syntactical error. --Arthur Corliss Bolverk's Lair -- http://www.odinicfoundation.org/arthur/ "Live Free or Die, the Only Way to Live" -- NH State Motto ================================================= Mailing list info: If at any time you wish to (un|re)subscribe to the list send the request to majordomo@hfb.pm.org. All requests should be in the body, and look like such subscribe anchorage-pm-list unsubscribe anchorage-pm-list From rox at tara-lu.com Fri May 5 18:17:41 2000 From: rox at tara-lu.com (Roxanne Reid-Bennett) Date: Wed Aug 4 23:56:47 2004 Subject: Using Net::LDAP::LDIF References: <39131B77.CB8D6442@tara-lu.com> <20000505114242.Y539@shoebox.net> Message-ID: <39135695.D765785F@tara-lu.com> Michael Fowler wrote: >[...] > This error usually means you either haven't loaded the Net::LDAP::LDIF > module (and thus didn't load any of the methods), or that the > Net::LDAP::LDIF module really doesn't have that method. hunh. That was it. I added a use Net::LDAP::LDIF; just below the user Net::LDAP; and the error goes away. Thank you! Rox -- Roxanne Reid-Bennett rox@tara-lu.com President, Tara-Lu Corporation http://www.tara-lu.com/ Quality brings its own reward. ================================================= Mailing list info: If at any time you wish to (un|re)subscribe to the list send the request to majordomo@hfb.pm.org. All requests should be in the body, and look like such subscribe anchorage-pm-list unsubscribe anchorage-pm-list From kevinc at gci.net Thu May 11 19:08:57 2000 From: kevinc at gci.net (K Creason) Date: Wed Aug 4 23:56:47 2004 Subject: Perl script with `command` in cron not right Message-ID: <001701bfbba6$44de2e40$6000030a@k2> This may seem a little twisted, if so, I'd appreciate being straightened out. I've cross posted this with the Perl user group and the linux group, because I'm not sure where the problem lies. I have a Perl script I scheduled in cron. BUT (of course there's a but to this) this line: $r=`cat /home/911/alert.msg |smbclient -M $mac[$c] -R wins -U "911 Alert"`; will do every thing up to the included pipe command. The script works perfect from the command line, cron just doesn't do that part. I know cron does some of it's won redirections, so is it the multiple redirect*s that go on in a cron job? I've tried the cron job scheduled like these two ways, following my HP-UX experience: * * * * * /home/911/ptel.pl >/home/911/ptel.log and * * * * * /home/911/ptel.pl It's never logged a thing to the cron piped log, so maybe that HP function isn't included in linux. I 've altered the perl line to include full path to the smbclient binary, no fix the problem. The cat function works, the alert.msg file is always updated. Computers can figure out all sorts of problems except the things in the world that just don't add up.--James Magoy ================================================= Mailing list info: If at any time you wish to (un|re)subscribe to the list send the request to majordomo@hfb.pm.org. All requests should be in the body, and look like such subscribe anchorage-pm-list unsubscribe anchorage-pm-list From corliss at alaskapm.org Thu May 11 19:36:51 2000 From: corliss at alaskapm.org (corliss@alaskapm.org) Date: Wed Aug 4 23:56:47 2004 Subject: Perl script with `command` in cron not right In-Reply-To: <001701bfbba6$44de2e40$6000030a@k2> Message-ID: On Thu, 11 May 2000, K Creason wrote: > This may seem a little twisted, if so, I'd appreciate being straightened > out. I've cross posted this with the Perl user group and the linux group, > because I'm not sure where the problem lies. > > I have a Perl script I scheduled in cron. > BUT (of course there's a but to this) > this line: > $r=`cat /home/911/alert.msg |smbclient -M $mac[$c] -R wins -U "911 Alert"`; > > will do every thing up to the included pipe command. The script works > perfect from the command line, cron just doesn't do that part. > I know cron does some of it's won redirections, so is it the multiple > redirect*s that go on in a cron job? > I've tried the cron job scheduled like these two ways, following my HP-UX > experience: > * * * * * /home/911/ptel.pl >/home/911/ptel.log > and > * * * * * /home/911/ptel.pl > > It's never logged a thing to the cron piped log, so maybe that HP function > isn't included in linux. I 've altered the perl line to include full path to > the smbclient binary, no fix the problem. > The cat function works, the alert.msg file is always updated. I'd check to see if smbclient is in the path (cron runs with stricter restrictions that shells do). --Arthur Corliss Perl Monger/Alaska Perl Mongers http://www.alaskapm.org/ ================================================= Mailing list info: If at any time you wish to (un|re)subscribe to the list send the request to majordomo@hfb.pm.org. All requests should be in the body, and look like such subscribe anchorage-pm-list unsubscribe anchorage-pm-list From wolfm at pobox.alaska.net Thu May 11 19:49:00 2000 From: wolfm at pobox.alaska.net (Michael Fowler) Date: Wed Aug 4 23:56:47 2004 Subject: Perl script with `command` in cron not right In-Reply-To: <001701bfbba6$44de2e40$6000030a@k2>; from kevinc@gci.net on Thu, May 11, 2000 at 04:08:57PM -0800 References: <001701bfbba6$44de2e40$6000030a@k2> Message-ID: <20000511164900.X310@shoebox.net> On Thu, May 11, 2000 at 04:08:57PM -0800, K Creason wrote: > I have a Perl script I scheduled in cron. > BUT (of course there's a but to this) > this line: > $r=`cat /home/911/alert.msg |smbclient -M $mac[$c] -R wins -U "911 Alert"`; Just as a note, this is one of those notorious Useless Uses of Cat. $r = `smbclient -M $mac[$c] -R wins -U "911 Alert" < /home/911/alert.msg` > will do every thing up to the included pipe command. The script works > perfect from the command line, cron just doesn't do that part. If it works on the command line and not when executed by cron it's usually an environment issue; you're making some assumption about the environment, or using some environmental variable, that doesn't exist within cron. Are there any environmental variables smbclient relies on to work properly in this situation? My smbclient man page mentions USER and PASSWD. USER shouldn't be required because you're specifying a username, but PASSWD may be. Your Perl script may also rely on its environment in some way, perhaps for setting $mac[$c]. > I know cron does some of it's won redirections, so is it the multiple > redirect*s that go on in a cron job? Whatever cron may or may not do with respect to redirections shouldn't affect fork/exec within your program. > I've tried the cron job scheduled like these two ways, following my HP-UX > experience: > * * * * * /home/911/ptel.pl >/home/911/ptel.log > and > * * * * * /home/911/ptel.pl > > It's never logged a thing to the cron piped log, so maybe that HP function > isn't included in linux. Every version of cron I've seen uses /bin/sh to execute the command. Any shell metacharacters would, therefore, be recognized. Both of the above lines should work as you intended. > I've altered the perl line to include full path to the smbclient binary, > no fix the problem. > The cat function works, the alert.msg file is always updated. You may want to replace your cat-to-smbclient line with: $r = `cat /home/911/alert.msg` and print $r out, to verify there are messages there at the point the cron job is run. That's about all I can think of at the moment. Michael -- Administrator www.shoebox.net Programmer, System Administrator www.gallanttech.com -- ================================================= Mailing list info: If at any time you wish to (un|re)subscribe to the list send the request to majordomo@hfb.pm.org. All requests should be in the body, and look like such subscribe anchorage-pm-list unsubscribe anchorage-pm-list From kevinc at gci.net Fri May 12 13:30:54 2000 From: kevinc at gci.net (K Creason) Date: Wed Aug 4 23:56:47 2004 Subject: Perl script with `command` in cron not right References: Message-ID: <001b01bfbc40$3530c260$6000030a@k2> It was a path thing after all. I specified the full path to all executables, but there was tiny little file read that I missed and so the whole subroutine wasn't running when cron did the job. I started paying close attention to the email from cron.. "couldn't open file handle" got me thinking... dangerous, but it paid off this time. Sheesh. Boy do I feel sheepish. ================================================= Mailing list info: If at any time you wish to (un|re)subscribe to the list send the request to majordomo@hfb.pm.org. All requests should be in the body, and look like such subscribe anchorage-pm-list unsubscribe anchorage-pm-list From corliss at odinicfoundation.org Wed May 31 16:32:40 2000 From: corliss at odinicfoundation.org (Arthur Corliss) Date: Wed Aug 4 23:56:47 2004 Subject: Linux Business to Avoid Message-ID: Greetings: Just a heads up to everyone on the level of service you can expect to recieve from one of the more prominent Linux vendors: EBIZ Enterprises, Inc. These people own and operate The Linux Store, The Linux Lab, Linux Wired, and InfoMagic, among other things. I recently purchased some hardware from them and found some of it defective. Even after going through their procedure of filling out an on-line RMA request form (that had the gall to ask for a CC#), it took repeated e-mail barrages to get them to even provide that. After finally getting an RMA, and shipping the hardware down to them at my expense, they had the gall to refuse acceptance of it, and so it ended up in my lap once more. These people promised via telephone and e-mail to get this resolved, and it appears that was a blatant lie. This definitely ranks as one of my worst buying experiences, and I will never order from them again. Unless you wish to dare experiencing the same, I would recommend that you avoid them as well. Just an FYI, do what you will. ;-) --Arthur Corliss Bolverk's Lair -- http://www.odinicfoundation.org/arthur/ "Live Free or Die, the Only Way to Live" -- NH State Motto ================================================= Mailing list info: If at any time you wish to (un|re)subscribe to the list send the request to majordomo@hfb.pm.org. All requests should be in the body, and look like such subscribe anchorage-pm-list unsubscribe anchorage-pm-list From zakhurlb at ptialaska.net Wed May 31 17:25:55 2000 From: zakhurlb at ptialaska.net (Civileme) Date: Wed Aug 4 23:56:47 2004 Subject: Linux Business to Avoid References: Message-ID: <39359172.D6A5E893@ptialaska.net> Arthur Corliss wrote: > Greetings: > > Just a heads up to everyone on the level of service you can expect to recieve > from one of the more prominent Linux vendors: EBIZ Enterprises, Inc. These > people own and operate The Linux Store, The Linux Lab, Linux Wired, and > InfoMagic, among other things. > > I recently purchased some hardware from them and found some of it defective. > Even after going through their procedure of filling out an on-line RMA > request form (that had the gall to ask for a CC#), it took repeated e-mail > barrages to get them to even provide that. > > After finally getting an RMA, and shipping the hardware down to them at my > expense, they had the gall to refuse acceptance of it, and so it ended up in > my lap once more. > > These people promised via telephone and e-mail to get this resolved, and it > appears that was a blatant lie. This definitely ranks as one of my worst > buying experiences, and I will never order from them again. Unless you wish > to dare experiencing the same, I would recommend that you avoid them as well. > > Just an FYI, do what you will. ;-) > > --Arthur Corliss > Bolverk's Lair -- http://www.odinicfoundation.org/arthur/ > "Live Free or Die, the Only Way to Live" -- NH State Motto \Second Arthur's experience .... annnnnd they also do CPU MicroMart. Their marketing is hype and empty promises (Example: www.planetPIA.com has been "Coming Soon" for almost 9 months). They sell a linux-powered box they call a Personal Internet Appliance with Debian installed and ... Of all things, a PCTel Software modem. This is an authentic copy of a genuine imitation of a $3 Rockwell Chipset that has Gateway computers giving ISPs headaches nationwide. A blasted linmodem! Getting the root passowrd out of them for one of those PIAs went the distance--two weeks, 17 phone calls and 7 emails. Someone had shut it down improperly and needed the root password to get to maintenance mode (The PIA comes unequipped with extravagant options like CDROM drives and floppy drives). The mainboard of the PIA appears to be a PCChips M748MR or equivalent with any of a dozen brand names used by the notorious PCChips, the progenitors of the "fake cache chip fiasco of 1996." InfoMagic was once a linux innovator, but over the past few years they have gone to seed, and EBIZ picked them up I suppose because the name was still worth something. Last time I dealt with InfoMagic, they could not solve the problem of Win98 boxes refusing to talk to their WorkGroup Server, and their latest innovation and big sale item is supplying Webmin for headless server boxes along with a nicely written tutorial. (I think when I am finished with my docbook chapter on Webmin for the Linux-Mandrake reference manual that we will have a superior product, but InfoMagic definitely fits well with the EBIZ sales hype.) And CPU MIcroMart is the sort of Other/Locally Built that makes every survey on PCs show Dell to be a high-end product, because they drag down the curve of user opinions. CPU Micromart will teach you every way to spell C-H-E-A-P except in relation to your wallet. Some of the experience I had was direct (they lost my order) and a lot of it was cleaning up after their disasters. I guess you can tell I am totally thrilled that they use the linux name. YMMV of course. Civileme ================================================= Mailing list info: If at any time you wish to (un|re)subscribe to the list send the request to majordomo@hfb.pm.org. All requests should be in the body, and look like such subscribe anchorage-pm-list unsubscribe anchorage-pm-list From corliss at odinicfoundation.org Wed May 31 18:18:02 2000 From: corliss at odinicfoundation.org (Arthur Corliss) Date: Wed Aug 4 23:56:47 2004 Subject: Linux Business to Avoid In-Reply-To: <39359172.D6A5E893@ptialaska.net> Message-ID: On Wed, 31 May 2000, Civileme wrote: > Getting the root passowrd out of them for one of those PIAs went the > distance--two weeks, 17 phone calls and 7 emails. Someone had shut it down > improperly and needed the root password to get to maintenance mode (The PIA > comes unequipped with extravagant options like CDROM drives and floppy drives). ;-) I'm par for the course, then. I've sent them nine e-mails and three phone calls, but only recieved five e-mails to date. They've ignored me at intervals of a week at a time (this had been going on for two months now), and never once responded to my pleasant e-mails. Only when I flame them and threaten to report to the BBB and the Linux community in general do they bother to respond. For whatever good that did, since they just refused to accept the hardware *they* issued an RMA for. Bastards. :-P --Arthur Corliss Bolverk's Lair -- http://www.odinicfoundation.org/arthur/ "Live Free or Die, the Only Way to Live" -- NH State Motto ================================================= Mailing list info: If at any time you wish to (un|re)subscribe to the list send the request to majordomo@hfb.pm.org. All requests should be in the body, and look like such subscribe anchorage-pm-list unsubscribe anchorage-pm-list