Hello.
I guess you should use either
Filename =
or
Listen =
directives in vusaged.conf.
Try, for example, commenting out line with "listen" by putting // in the beginning:
// Listen = 0.0.0.0:189;
HTH.
Wednesday, November 25, 2009, 9:56:37 AM, you wrote:
>
i hav given the follo
thanks for the solution. i tried to run
the vusaged by commenting out listen line in vusaged.conf and now i
think i can run it
#./vusaged
config: using
/home/vpopmail/etc/vusaged.conf
socket: listening on
/tmp/vusaged.sock
No i dont have ~vpopmail/etc/vusagec.conf. i have only domains directory in
/home/vpopmail~vpopmail directory.
vusaged.conf and vusagec.conf are present in /home/vpopmail/etc directory
Thanks.
>Do you have ~vpopmail/etc/vusagec.conf ?
Wednesday, November 25, 2009, 1:46:48 PM,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Does anyone have a non-production Solaris box laying around that they could
provide temporary access
to so that I may finalize the .29, and update the 5.5, vusage code, for that
operating system?
It would be greatly appreciated!
Thanks!
PS: I will
What type with what OS
Remo
On 11/25/09 7:56 AM, "Matt Brookings" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Does anyone have a non-production Solaris box laying around that they could
> provide temporary access
> to so that I may finalize the .29, and update the 5.5, vusage
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Remo Mattei wrote:
> What type with what OS
Solaris, preferably on a sparc, but intel is fine too.
- --
/*
Matt BrookingsGnuPG Key FAE0672C
Software developer Systems technician
Inter7 Internet Technologies, Inc
