[30811] in Perl-Users-Digest
Perl-Users Digest, Issue: 2056 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Dec 15 00:09:44 2008
Date: Sun, 14 Dec 2008 21:09:06 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Sun, 14 Dec 2008 Volume: 11 Number: 2056
Today's topics:
Re: a simple control in an nntp client <george@example.invalid>
Re: a simple control in an nntp client <george@example.invalid>
Re: a simple control in an nntp client <george@example.invalid>
Re: a simple control in an nntp client <tadmc@seesig.invalid>
Re: a simple control in an nntp client <tadmc@seesig.invalid>
Re: How to find cpu utilization for each process on WIn <veatchla@yahoo.com>
Re: Noob trying to understand simple Perl grep statemen <tim@burlyhost.com>
Re: Noob trying to understand simple Perl grep statemen <ced@blv-sam-01.ca.boeing.com>
Re: opening a file <rihad@mail.ru>
Re: opening a file <someone@example.com>
Re: opening a file <rihad@mail.ru>
Re: opening a file skeldoy@gmail.com
Re: opening a file <someone@example.com>
Re: opening a file <someone@example.com>
Re: opening a file xhoster@gmail.com
Re: querying Active Directory via LDAP in perl joseph85750@yahoo.com
Re: querying Active Directory via LDAP in perl <mvdwege_public@myrealbox.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sun, 14 Dec 2008 18:55:37 -0700
From: George <george@example.invalid>
Subject: Re: a simple control in an nntp client
Message-Id: <1cpkzum6kx3aq.q35kg7cfqvvg.dlg@40tude.net>
On Fri, 12 Dec 2008 21:47:14 -0600, Tad J McClellan wrote:
> George <george@example.invalid> wrote:
>
>
>> if ($_->[$from_offset] eq "George <george@example.invalid>")
>
>
> Execute this Perl program:
>
> $_ = "George <george@example.invalid>";
> print;
>
> and then use single quotes instead.
>
> :-)
ok
C:\MinGW\source> perl tad1.pl
George <george.invalid>
C:\MinGW\source> perl tad1.pl
George <george@example.invalid>
C:\MinGW\source>
Clearly, I want single quotes. What happened as a side effect from the
double-quoted one?
One thing that happens in perl that doesn't happen in fortran is that
you're halfway through the program, and a statement like
...($something, @arts)= ...
creates an array. This would be strictly forbidden in fortran.
--
George
The deliberate and deadly attacks which were carried out yesterday against
our country were more than acts of terror. They were acts of war.
George W. Bush
Picture of the Day http://apod.nasa.gov/apod/
------------------------------
Date: Sun, 14 Dec 2008 18:59:01 -0700
From: George <george@example.invalid>
Subject: Re: a simple control in an nntp client
Message-Id: <sn8g3mbkeovv.1fhvrtmtlwoon$.dlg@40tude.net>
On Fri, 12 Dec 2008 20:27:38 -0800, Tim Greer wrote:
> George wrote:
>
>> , why doesn't this:
>>
>> if ($_->[$from_offset] eq "George <george@example.invalid>")
>> {
>> print STDOUT "got a match\n";
>> }
>>
>> perl.exe says:
>>
>> Use of uninitialized value in string eq at script2.pl line 58.
>>
>> where line 58 is the test condition on the if control.
>
> I think you meant "George <george\@example.invalid>" or else 'George
> <george@example.invalid>', otherwise @example will mean something else.
That's one side of the comparison. I see that this should be
single-quoted.
The stumper is how to use $_-> and $from_offset to get the from attribute
from a given message.
I swear, control mechanisms in perl use stealth.
--
George
The United States of America will never be intimidated by thugs and
assassins. The killers will fail, and the Iraqi people will live in
freedom.
George W. Bush
Picture of the Day http://apod.nasa.gov/apod/
------------------------------
Date: Sun, 14 Dec 2008 19:15:55 -0700
From: George <george@example.invalid>
Subject: Re: a simple control in an nntp client
Message-Id: <1hfsf9zl3x314.1ktfto20zasdf.dlg@40tude.net>
On Fri, 12 Dec 2008 22:31:44 -0800, Jürgen Exner wrote:
> Jürgen Exner <jurgenex@hotmail.com> wrote:
>>George <george@example.invalid> wrote:
>>>if ($_->[$from_offset] eq "George <george@example.invalid>")
>>>
>>>perl.exe says:
>>>
>>>Use of uninitialized value in string eq at script2.pl line 58.
>>>
>>>where line 58 is the test condition on the if control.
>>
>>Well, what value does the array @example have?
>>Had you used warnings and strict as has been strongly recommended over
>>and over again then perl would (probably) have warned you at compile
>>time that @example was undefined.
>
> s/undefined/undeclared/
>
> of course
>
> jue
I don't see anything different after having added
use warnings;
and single quotes:
C:\MinGW\source>perl script2.pl
s4 is
Use of uninitialized value in string eq at script2.pl line 58.
C:\MinGW\source>perl script2.pl
s4 is
Use of uninitialized value in string eq at script2.pl line 59.
C:\MinGW\source>
#!/usr/bin/perl -w
use strict;
use warnings;
use Net::NNTP ();
use constant NUMBER_OF_ARTICLES => 10;
use constant GROUP_NAME => 'comp.lang.perl.misc';
use constant SERVER_NAME => 'news.individual.net';
use constant NNTP_DEBUG => 0;
my $nntp = Net::NNTP->new(SERVER_NAME, 'Debug' => NNTP_DEBUG) or die;
my $USER = '';
my $PASS = '';
$nntp->authinfo($USER,$PASS) or die $!;
my($article_count, $first_article, $last_article) =
$nntp->group(GROUP_NAME) or die;
# Which XOVER fields contain Subject: and From:?
my $count = 0;
my %xover_fmt = map( ($_, $count++), @{ $nntp->overview_fmt or die} );
die unless exists $xover_fmt{'Subject:'};
my $subject_offset = $xover_fmt{'Subject:'};
my $from_offset = $xover_fmt{'From:'};
my(@xover, $start_article);
RETRIEVE: while ($#xover+1 < NUMBER_OF_ARTICLES and $last_article >=
$first_article) {
# How many articles do we need? Stop retrieving if we have enough
my $articles_required = NUMBER_OF_ARTICLES - ($#xover+1) or last
RETRIEVE;
# Fetch overview information for the articles
$start_article = $last_article - ($articles_required-1);
$start_article = $start_article > $first_article ? $start_article :
$first_article;
my $xover_query = $start_article == $last_article ?
$start_article :
[$start_article, $last_article];
my $xover_ref = $nntp->xover($xover_query) or die;
# Store headers for the articles we've retrieved
foreach (sort {$b <=> $a} keys %$xover_ref) {
push @xover, $xover_ref->{$_};
}
} continue {
# Move the pointer forward to fetch previous articles
$last_article = $start_article - 1;
}
my $s4 = join( map ($_->[$from_offset],@xover));
print STDOUT " s4 is $s4\n";
if ($_->[$from_offset] eq 'George <george@example.invalid>')
{
print STDOUT "got a match\n";
}
$nntp->article($_,\*STDOUT) for @xover;
# Disconnect from the NNTP server
$nntp->quit;
# perl script2.pl
--
George
Now, there are some who would like to rewrite history - revisionist
historians is what I like to call them.
George W. Bush
Picture of the Day http://apod.nasa.gov/apod/
------------------------------
Date: Sun, 14 Dec 2008 21:06:42 -0600
From: Tad J McClellan <tadmc@seesig.invalid>
Subject: Re: a simple control in an nntp client
Message-Id: <slrngkbie2.r8a.tadmc@tadmc30.sbcglobal.net>
George <george@example.invalid> wrote:
> On Fri, 12 Dec 2008 21:47:14 -0600, Tad J McClellan wrote:
>
>> George <george@example.invalid> wrote:
>>
>>
>>> if ($_->[$from_offset] eq "George <george@example.invalid>")
>>
>>
>> Execute this Perl program:
>>
>> $_ = "George <george@example.invalid>";
>> print;
>>
>> and then use single quotes instead.
( or, escape the at-sign: $_ = "George <george\@example.invalid>" )
> C:\MinGW\source> perl tad1.pl
> George <george.invalid>
> C:\MinGW\source> perl tad1.pl
> George <george@example.invalid>
> C:\MinGW\source>
>
> Clearly, I want single quotes. What happened as a side effect from the
> double-quoted one?
It interpolated the @example array.
Since it was empty, it was replaced with the empty string.
You should always enable warnings when developing Perl code.
perl -we '$_ = "George <george@example.invalid>"; print'
Possible unintended interpolation of @example in string at -e line 1.
Name "main::example" used only once: possible typo at -e line 1.
> One thing that happens in perl that doesn't happen in fortran is that
> you're halfway through the program, and a statement like
>
> ...($something, @arts)= ...
>
> creates an array. This would be strictly forbidden in fortran.
^^^^^^
^^^^^^
You should also always enable strictures in Perl programs.
If you do, then such things are strictly forbidden in Perl too.
use warnings;
use strict;
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Sun, 14 Dec 2008 22:48:58 -0600
From: Tad J McClellan <tadmc@seesig.invalid>
Subject: Re: a simple control in an nntp client
Message-Id: <slrngkbodq.r8a.tadmc@tadmc30.sbcglobal.net>
George <george@example.invalid> wrote:
> On Fri, 12 Dec 2008 22:31:44 -0800, Jürgen Exner wrote:
>
>> Jürgen Exner <jurgenex@hotmail.com> wrote:
>>>George <george@example.invalid> wrote:
>>>>if ($_->[$from_offset] eq "George <george@example.invalid>")
>>>>
>>>>perl.exe says:
>>>>
>>>>Use of uninitialized value in string eq at script2.pl line 58.
>>>>
>>>>where line 58 is the test condition on the if control.
>>>
>>>Well, what value does the array @example have?
The more pertinent question is what value does $_ have...
> if ($_->[$from_offset] eq 'George <george@example.invalid>')
> {
> print STDOUT "got a match\n";
> }
You have not put anything into $_.
Perhaps you meant to loop over @xover instead?
foreach ( @xover ) {
if ($_->[$from_offset] eq 'George <george@example.invalid>') {
print STDOUT "got a match\n";
}
}
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Sun, 14 Dec 2008 16:45:44 -0600
From: l v <veatchla@yahoo.com>
Subject: Re: How to find cpu utilization for each process on WIndows Platform using perl
Message-Id: <Y4OdnbRhmNIFEdjUnZ2dnUVZ_jqdnZ2d@supernews.com>
zigzagdna@yahoo.com wrote:
> I am on Windows 2000 Server. Are there any perl programs which will
> show me cpu utilization of each process. I will like to schedule such
> a program to find which processes are taking most of cpu (similar to
> top or glance in UNIX).
Perl modules Win32::Process::Info or Win32::PerfLib may be what you want.
--
Len
------------------------------
Date: Sun, 14 Dec 2008 10:26:19 -0800
From: Tim Greer <tim@burlyhost.com>
Subject: Re: Noob trying to understand simple Perl grep statement
Message-Id: <gdc1l.63$a01.2@newsfe03.iad>
Greg Bacon wrote:
> Worrying about people who *choose* to be ignorant, as with any
> form of bigotry, is a complete waste of time. Don't try to teach
> a pig to dance, as the saying goes.
Alright then, I won't interrupt your reply to Randal about what you
feel.
--
Tim Greer, CEO/Founder/CTO, BurlyHost.com, Inc.
Shared Hosting, Reseller Hosting, Dedicated & Semi-Dedicated servers
and Custom Hosting. 24/7 support, 30 day guarantee, secure servers.
Industry's most experienced staff! -- Web Hosting With Muscle!
------------------------------
Date: Sun, 14 Dec 2008 12:10:00 -0800 (PST)
From: "C.DeRykus" <ced@blv-sam-01.ca.boeing.com>
Subject: Re: Noob trying to understand simple Perl grep statement
Message-Id: <7fed4465-73c9-4b5d-859a-185fd9d060b0@a26g2000prf.googlegroups.com>
On Dec 13, 8:09 pm, gba...@hiwaay.net (Greg Bacon) wrote:
> In article <86skp05d7o....@blue.stonehenge.com>,
> Randal L. Schwartz <mer...@stonehenge.com> wrote:
>
> : I still regret inventing JAPHs, which encouraged obfuperl, and in
> : some sense was the motivation for Perl golf. All three items
> : today harm Perl's public perception more than they help, and I'm
> : sad for that.
>
> Don't be a puritan. Perl is fun, and that's great! Snobs who look
> down their noses at jam sessions aren't worth worrying about.
>
I agree totally. Dismissive comments are for snobs -- Perl brings fun
back to programming. And seriously, an "Obfuscated C Contest" or a
Perl "golf" contest is often
serendipitous because you're looking in a language's nooks and
crannies to explore its capabilities. At times the bugs and mis-
features of a languare are exposed; at others, you reveal how the
gears and gizmos work under the covers. The "Obfuscated C contest"
regularly attracts world class C programmers. Larry's won a couple of
times as I recall.
Just think.. Perl may have been the result of his mis-spent
youth :)
--
Charles DeRykus
------------------------------
Date: Sun, 14 Dec 2008 08:24:52 -0800 (PST)
From: rihad <rihad@mail.ru>
Subject: Re: opening a file
Message-Id: <40d1f4db-4b9a-4005-8f06-994b4b430e70@t26g2000prh.googlegroups.com>
> Did you tried using:
> open(FOO, ">> /var/tmp/foo") or return;
Still the same. BTW: why would changing to append mode affect the
result?
> open FOO, '>', '/var/tmp/foo' or die "Can't open > /var/tmp/foo
Come on... we aren't language lawyers taking a cup of coffee during
lunch, are we? Your comments make me no closer to the solution.
------------------------------
Date: Sun, 14 Dec 2008 09:38:08 -0800
From: "John W. Krahn" <someone@example.com>
Subject: Re: opening a file
Message-Id: <%vb1l.5526$hs1.3114@newsfe04.iad>
rihad wrote:
> This function is from a daemon (long-lived process):
>
> sub foo($) {
> my ($command) = shift;
>
> BEGIN {
> open(FOO, ">/var/tmp/foo") or return;
> my $old_fh = select(FOO);
> $| = 1;
> select($old_fh);
> }
>
> print FOO "$command\n";
>
> END {
> close(FOO);
> }
> }
>
> /var/tmp/foo is a FIFO (mkfifo). It also has a reader daemon (not
> shown).
> Now when foo('blah-blah-blah') is called, nothing gets written to the
> FIFO. Even if I call it several times in succession. I need to stop
> the Perl daemon to see them finally output.
Nothing gets written? Or it does get written when you close the
filehandle (stop the Perl daemon?)
Unlike a terminal which has line buffering, it looks like you are
encountering full buffering which does not output on every newline.
Perhaps you might try unbuffered IO with sysopen and syswrite instead of
open and print:
perldoc -f sysopen
perldoc -f syswrite
perldoc perlopentut
man 2 open
John
--
Those people who think they know everything are a great
annoyance to those of us who do. -- Isaac Asimov
------------------------------
Date: Sun, 14 Dec 2008 10:33:25 -0800 (PST)
From: rihad <rihad@mail.ru>
Subject: Re: opening a file
Message-Id: <fccac5f2-d516-45c4-9404-77faa767e846@a12g2000pro.googlegroups.com>
> > /var/tmp/foo is a FIFO (mkfifo). It also has a reader daemon (not
> > shown).
> > Now when foo('blah-blah-blah') is called, nothing gets written to the
> > FIFO. Even if I call it several times in succession. I need to stop
> > the Perl daemon to see them finally output.
>
> Nothing gets written? Or it does get written when you close the
> filehandle (stop the Perl daemon?)
>
Yeah, they do get written when it's stopped, just like I think I
said ;)
> Unlike a terminal which has line buffering, it looks like you are
> encountering full buffering which does not output on every newline.
>
But but but... shouldn't $| = 1; flush the buffer upon every print?
See perlfaq5.
> Perhaps you might try unbuffered IO with sysopen and syswrite instead of
> open and print:
>
> perldoc -f sysopen
> perldoc -f syswrite
> perldoc perlopentut
> man 2 open
>
Thanks, I'll give them a try and see how it goes.
> Geeze, do I really need to tell you this?
Yeah you're right but the messages are surely in the buffer as they
are written as soon as I stop the Perl daemon. See above.
------------------------------
Date: Sun, 14 Dec 2008 10:43:40 -0800 (PST)
From: skeldoy@gmail.com
Subject: Re: opening a file
Message-Id: <11fae175-3de4-4d33-881f-2bda29b84c1d@o4g2000pra.googlegroups.com>
Try putting the $|=3D1; at the start of your program (right under any
use-statements that you may have). I have encountered various problems
when trying to reconfigure the buffering on the fly. Only two cents
here. Good luck!
> sub foo($) {
> =A0 =A0 =A0 =A0BEGIN {
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 open(FOO, ">/var/tmp/foo") or return;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 $| =3D 1;
------------------------------
Date: Sun, 14 Dec 2008 11:36:19 -0800
From: "John W. Krahn" <someone@example.com>
Subject: Re: opening a file
Message-Id: <Oed1l.15315$uS1.14793@newsfe19.iad>
rihad wrote:
>>> /var/tmp/foo is a FIFO (mkfifo). It also has a reader daemon (not
>>> shown).
>>> Now when foo('blah-blah-blah') is called, nothing gets written to the
>>> FIFO. Even if I call it several times in succession. I need to stop
>>> the Perl daemon to see them finally output.
>> Nothing gets written? Or it does get written when you close the
>> filehandle (stop the Perl daemon?)
>>
> Yeah, they do get written when it's stopped, just like I think I
> said ;)
>
>> Unlike a terminal which has line buffering, it looks like you are
>> encountering full buffering which does not output on every newline.
>>
> But but but... shouldn't $| = 1; flush the buffer upon every print?
> See perlfaq5.
>
>> Perhaps you might try unbuffered IO with sysopen and syswrite instead of
>> open and print:
>>
>> perldoc -f sysopen
>> perldoc -f syswrite
>> perldoc perlopentut
>> man 2 open
>>
> Thanks, I'll give them a try and see how it goes.
>
>> Geeze, do I really need to tell you this?
> Yeah you're right but the messages are surely in the buffer as they
> are written as soon as I stop the Perl daemon. See above.
I didn't write that last sentence. Why are you attributing that to me?
John
--
Those people who think they know everything are a great
annoyance to those of us who do. -- Isaac Asimov
------------------------------
Date: Sun, 14 Dec 2008 11:39:48 -0800
From: "John W. Krahn" <someone@example.com>
Subject: Re: opening a file
Message-Id: <3id1l.15316$uS1.14985@newsfe19.iad>
skeldoy@gmail.com wrote:
> Try putting the $|=1; at the start of your program (right under any
> use-statements that you may have). I have encountered various problems
> when trying to reconfigure the buffering on the fly. Only two cents
> here. Good luck!
$| only applies to the currently selected filehandle so at the start of
the program that is probably STDOUT.
John
--
Those people who think they know everything are a great
annoyance to those of us who do. -- Isaac Asimov
------------------------------
Date: 14 Dec 2008 20:48:12 GMT
From: xhoster@gmail.com
Subject: Re: opening a file
Message-Id: <20081214154659.685$kX@newsreader.com>
rihad <rihad@mail.ru> wrote:
> This function is from a daemon (long-lived process):
>
> sub foo($) {
> my ($command) = shift;
>
> BEGIN {
> open(FOO, ">/var/tmp/foo") or return;
Since the BEGIN isn't actually happening during the sub call,
it is not clear to me what the "or return" is going to do in
case of a failure.
> my $old_fh = select(FOO);
> $| = 1;
> select($old_fh);
> }
>
> print FOO "$command\n";
>
> END {
> close(FOO);
> }
> }
>
> /var/tmp/foo is a FIFO (mkfifo). It also has a reader daemon (not
> shown).
Are you sure your problem is not in the reader daemon? I can not reproduce
your problem using your code above (and the driver below), and using "cat"
as the reader.
foreach (1..10) {
foo($_);
sleep 5;
};
....
>
> Perl v5.8.8
> FreeBSD 7.0
But I am using Linux rather than FreeBSD. It seems unlikely they would
differ in this regard, but you never know.
Xho
--
-------------------- http://NewsReader.Com/ --------------------
The costs of publication of this article were defrayed in part by the
payment of page charges. This article must therefore be hereby marked
advertisement in accordance with 18 U.S.C. Section 1734 solely to indicate
this fact.
------------------------------
Date: Sun, 14 Dec 2008 10:52:36 -0800 (PST)
From: joseph85750@yahoo.com
Subject: Re: querying Active Directory via LDAP in perl
Message-Id: <25520dba-9cc0-4938-a33b-f0b8eb6c3556@i20g2000prf.googlegroups.com>
On Dec 13, 10:48 am, "Thrill5" <nos...@somewhere.com> wrote:
> <joseph85...@yahoo.com> wrote in message
>
> news:e34ecf39-ee6c-42de-8056-d462661916f6@i24g2000prf.googlegroups.com...
> On Dec 11, 7:11 pm, "Thrill5" <nos...@somewhere.com> wrote:
>
>
>
> > <joseph85...@yahoo.com> wrote in message
>
> >news:03a34234-c330-464e-9a0c-6bd65c28b96b@k36g2000pri.googlegroups.com...
>
> > > I've been poking at this on and off over the past few months, never
> > > having much success. I was never sure what sort of crazy query string
> > > the AD server wanted. But then it occurred to me that my Linux
> > > Evolution email client does this without any problems-- only using the
> > > IP address of the Active Directory LDAP server. I can query/search,
> > > and it immediately returns all matches.
>
> > > How can it do this without the big ugly
> > > "cn=users,dc=foo,dc=blah,o=acme......" string ?
>
> > >Since this is obviously possible and simple(except for me), how could
> > > I do this same simple query in perl-- only armed with the IP address
> > > of my AD/LDAP server?
>
> > > Curiously,
> > > JS
>
> > Google "LDAP query syntax", and you will find a whole bunch of information
> > about querying AD via LDAP.
> >Yes, google returns many articles mentioning query strings, such as:
>
> >search DN: ou=groups,ou=@company,dc=corp,dc=trx,dc=com
>
> >But back to my original question-- Evolution doesn't seem to need any
> >of this. In Evolution, you simply give it the IP address of your AD/
> >LDAP server and it all magically works. Evolution is running on a
> >linux box, which has no knowledge of the query string variables.
>
> >I even tried running a tcpdump on the connection to figure out what it
> >was doing but couldn't figure it out.
>
> You obviously haven't read them, if you did you would know how to do this.
> You need only to specify the CN to search for, the base DN (where to start
> the search) along with setting the appropriate seach scope (i.e. subtree).
How does the Evolution mail client know how to query the AD Ldap
then? I specified no CN, DN, or subtree; only the IP address of the
AD Ldap.
------------------------------
Date: Sun, 14 Dec 2008 23:16:26 +0100
From: Mart van de Wege <mvdwege_public@myrealbox.com>
Subject: Re: querying Active Directory via LDAP in perl
Message-Id: <86iqpmcshx.fsf@gareth.avalon.lan>
joseph85750@yahoo.com writes:
> On Dec 13, 10:48 am, "Thrill5" <nos...@somewhere.com> wrote:
>> <joseph85...@yahoo.com> wrote in message
>>
>> news:e34ecf39-ee6c-42de-8056-d462661916f6@i24g2000prf.googlegroups.com...
>> On Dec 11, 7:11 pm, "Thrill5" <nos...@somewhere.com> wrote:
>>
<snip>
>> > Google "LDAP query syntax", and you will find a whole bunch of information
>> > about querying AD via LDAP.
>> >Yes, google returns many articles mentioning query strings, such as:
>>
>> >search DN: ou=groups,ou=@company,dc=corp,dc=trx,dc=com
>>
>> >But back to my original question-- Evolution doesn't seem to need any
>> >of this. In Evolution, you simply give it the IP address of your AD/
>> >LDAP server and it all magically works. Evolution is running on a
>> >linux box, which has no knowledge of the query string variables.
>>
>> >I even tried running a tcpdump on the connection to figure out what it
>> >was doing but couldn't figure it out.
>>
>> You obviously haven't read them, if you did you would know how to do this.
>> You need only to specify the CN to search for, the base DN (where to start
>> the search) along with setting the appropriate seach scope (i.e. subtree).
>
> How does the Evolution mail client know how to query the AD Ldap
> then? I specified no CN, DN, or subtree; only the IP address of the
> AD Ldap.
Evolution does specify the CN:
mvdwege@gareth:/usr/lib/evolution$ find . -exec strings \{} \; | grep -i 'cn ='
cn = %s
Furthermore, I concur with the previous poster: *read* those search
entries. LDAP query syntax isn't that hard to understand, it's just
verbose.
Mart
--
"We will need a longer wall when the revolution comes."
--- AJS, quoting an uncertain source.
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 2056
***************************************
