Search Again:

Re: Optigold v2.5.7 Questions

From: Technical Staff
Date: Monday, October 2, 2000
Time: 3:01:27 pm

On 10/2/00 12:26 AM, "Charley Webb" <charley@esslink.com> wrote:

> I just upgraded to the latest Optigold and have a question about one of the
> new features, which is when you place a customer on hold, you can also set
> Optigold to place a customers additional Email account(s) on hold.
>
> The problem is that we run UNIX servers here, and lets say that john doe
> customer who has 5 Email accounts get's placed on hold. Optigold will make 5
> telnet sessions to place this customers Email accounts on hold, but the
> problem us that it tries to place them on hold all at the same time, big
> boo-boo. UNIX password databases do not like the password file(s) to be
> modified all at the same time. Is there a way to have Optigold do it one
> Email at a time?
>
> Thankx


Just a suggestion - Why not try things a little differently
* * NOTE: This is completely Untested * *

I assume you are currently using ht Unix Hold script provided on OG support
page? If you are.. The following may work in your situation for the time
being until OG has the capabilities

These are examples that I would enter if we were using this set up ourselves
(which we are not) so you'll obviously need to modify this slightly.

In OG 'Auto Server Setup' --> 'Hold'

We are using Command Line (using Telscript)
And would enter something like

rsh your.servers.ip.address -l optigold "sudo echo <Login> >> HoldFile"



This task would be so quick that I highly doubt any overlap would occur,
since the telnet session that OG opens are not all at the 'exact' same time
- and actually have a slight lag behind one another, this would allow for
the previous command to finish (IMHO)


Anyway. Your server would then have a file called HoldFile (or whatever)
with the following

User1
User2
User3
User4
User5


Now that you have a local file with the customers to go on hold, you can let
Unix handle it from there.

Set up a cron job to run every 5 minutes.. Or 1 hour or each day that will
run an external program like



#!/usr/bin/perl5

open (USERS, "<HoldFile") or die "Couldn't open user list";

while (<USERS>) {
chomp;
system ("/root/scripts/hold.pl", "-h", $_);
}

close (USERS);

unlink <HoldFile>;


My Perl is a little rusty and rough around the edges.. Another way is a
simple executable shell script like run by cron in the same way (and since
my Perl is a little rusty, I would personally would feel safer with this
with less testing. I believe the Perl would work as is, but I can't make
any guarantees :) So, a simple shell script of:


cat HoldFile



Messages In This Thread:



Return to Digital Point Solutions' Home Page