I'm sure the best way to implement it is to not let the LDAP driver in
Kernel::System::CustomerUser::LDAP die if it can not connect. If you
would add that functionality, I'm sure we'd be open to accept such
patches!
--
Mike
On Sun, Sep 23, 2012 at 6:04 PM, Stefano Ricci
<stefano.ri...@riccimatic.com> wrote:
> ok, thanks for the response.
>
> now i test the ping control, and if generate problem...
>
>
> On 23 September 2012 17:03, Gerald Young <cryth...@gmail.com> wrote:
>>
>> I wouldn't *exactly* use the terminology "event" for this purpose.
>> Essentially, you may be correct, but Config.pm is a module that is
>> accessed to provide configuration attributes according to how
>> Config.pm evaluates the expression for a given "variable" or
>> "attribute". Config.pm is being used *everywhere* for practically
>> everything that has user-definable modifications. But, then again,
>> when any module calls Config.pm, be it "event", or "operation", it
>> will rely on the evaluated expression returned by Config.pm for the
>> requested parameter.
>>
>> Lots of caveats there, to be sure, but if it makes sense to you, the
>> short answer to your question is "yes", though in a much bigger scope
>> than you propose.
>>
>> "What's an evaluated expression?"
>> Config.pm might have a variable (array key/value) set:
>> $Self->{Database} = 'otrs';
>>
>> This is a pure assignment of value to an array key.
>> It could be something like:
>> $Self->{Database} = 'otrs' . '_dev';
>> Which means the expression of "concatenate" 'otrs' and '_dev' is
>> evaluated -- 'otrs_dev' -- and assigned to $Self->{Database}
>>
>> It can be further defined such as:
>> my $foo = true;
>> $Self->{Database} = 'otrs';
>> if ($foo = true) { $Self->{Database} = 'otrs_test'; }
>> which would mean that the call to Config as a perl module will return
>> $Self->{Database} as 'otrs_test' instead of 'otrs';
>>
>> If you create a test for connectivity before assignment of variables
>> to connect, you can likewise do as you request.
>>
>> On Sun, Sep 23, 2012 at 10:02 AM, Stefano Ricci
>> <stefano.ri...@riccimatic.com> wrote:
>> > ok, from your response, i understand that the script in config.pm are
>> > executed on new incoming event.. i thnik that these events are:
>> >
>> > new email fetched
>> > customer login
>> > agent login
>> >
>> >
>> > is that correct?
>> >
>> > On 22 September 2012 23:52, Gerald Young <cryth...@gmail.com> wrote:
>> >>
>> >> It may be possible to do that as Config.pm is perl ... "How?" You'd
>> >> have to search for Net::Ping or query the LDAP module itself to set
>> >> the auth method based upon the LDAP availability.
>> >>
>> >> On Sat, Sep 22, 2012 at 1:13 PM, Stefano Ricci
>> >> <stefano.ri...@riccimatic.com> wrote:
>> >> > hi to all... i user otrs 3.1.7 to work with my company customer and
>> >> > today i
>> >> > have some problems.
>> >> >
>> >> > my configuration is that: otrs in datacenter connected with customers
>> >> > active
>> >> > directory throught vpn connections and, if the customer is small,
>> >> > only
>> >> > the
>> >> > local database.
>> >> >
>> >> > today the vpn connection go down for 2 customers, and the platform
>> >> > block
>> >> > the
>> >> > login for agents and others customers... to solve the problem i
>> >> > remove
>> >> > the
>> >> > customers unreachable from config.pm...
>> >> >
>> >> > i want to know if is possible write some code in config.pm to check
>> >> > with
>> >> > ping the primary domain controller status, and if is offline, ignore
>> >> > the
>> >> > part of code that connect this active directory...
>> >> >
>> >> > thanks fo the help
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > OTRS mailing list: otrs - Webpage: http://otrs.org/
>> >> > Archive: http://lists.otrs.org/pipermail/otrs
>> >> > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
>> >> ---------------------------------------------------------------------
>> >> OTRS mailing list: otrs - Webpage: http://otrs.org/
>> >> Archive: http://lists.otrs.org/pipermail/otrs
>> >> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > OTRS mailing list: otrs - Webpage: http://otrs.org/
>> > Archive: http://lists.otrs.org/pipermail/otrs
>> > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
>> ---------------------------------------------------------------------
>> OTRS mailing list: otrs - Webpage: http://otrs.org/
>> Archive: http://lists.otrs.org/pipermail/otrs
>> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
>
>
>
> ---------------------------------------------------------------------
> OTRS mailing list: otrs - Webpage: http://otrs.org/
> Archive: http://lists.otrs.org/pipermail/otrs
> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
