On 6/21/06, Odhiambo WASHINGTON <[EMAIL PROTECTED]> wrote:
> * On 21/06/06 14:27 -0700, Paul Lesniewski wrote:
> | On 6/21/06, Tomas Kuliavas <[EMAIL PROTECTED]> wrote:
> | > > | > Hello Squirrels ;)
> | > > | >
> | > > | >
> | > > | > I am one happy sysadmin who uses this wonderful piece of code.
* On 21/06/06 14:27 -0700, Paul Lesniewski wrote:
| On 6/21/06, Tomas Kuliavas <[EMAIL PROTECTED]> wrote:
| > > | > Hello Squirrels ;)
| > > | >
| > > | >
| > > | > I am one happy sysadmin who uses this wonderful piece of code.
| > > | > Thanks to Paul and Ryan for the good job.
| > > | >
| > > | >
On 6/21/06, Tomas Kuliavas <[EMAIL PROTECTED]> wrote:
> > | > Hello Squirrels ;)
> > | >
> > | >
> > | > I am one happy sysadmin who uses this wonderful piece of code.
> > | > Thanks to Paul and Ryan for the good job.
> > | >
> > | > However, I do have two problems at the moment and I am not sure i
> | > Hello Squirrels ;)
> | >
> | >
> | > I am one happy sysadmin who uses this wonderful piece of code.
> | > Thanks to Paul and Ryan for the good job.
> | >
> | > However, I do have two problems at the moment and I am not sure it's
> | > the fault of the plugin, the fault of SM, or my own fault.
> | > | >1. I have had cases where a user's .prefs file has been changed.
> | > | > What I mean is that [EMAIL PROTECTED] has ended up
> | > | > having [EMAIL PROTECTED] as the e-mail address, for
> | > | > example. How this happens has left me stumped. This is very
> | > | > dangerous, bec
* On 21/06/06 23:25 +0300, Tomas Kuliavas wrote:
| > * On 21/06/06 10:33 -0700, Paul Lesniewski wrote:
| > | >1. I have had cases where a user's .prefs file has been changed.
| > | > What I mean is that [EMAIL PROTECTED] has ended up
| > | > having [EMAIL PROTECTED] as the e-mail address, for
|
* On 21/06/06 20:32 +0300, Tomas Kuliavas wrote:
| >
| > Hello Squirrels ;)
| >
| >
| > I am one happy sysadmin who uses this wonderful piece of code.
| > Thanks to Paul and Ryan for the good job.
| >
| > However, I do have two problems at the moment and I am not sure it's
| > the fault of the plug
> * On 21/06/06 10:33 -0700, Paul Lesniewski wrote:
> | >1. I have had cases where a user's .prefs file has been changed.
> | > What I mean is that [EMAIL PROTECTED] has ended up
> | > having [EMAIL PROTECTED] as the e-mail address, for
> | > example. How this happens has left me stumped. Thi
* On 21/06/06 10:33 -0700, Paul Lesniewski wrote:
| >1. I have had cases where a user's .prefs file has been changed.
| > What I mean is that [EMAIL PROTECTED] has ended up
| > having [EMAIL PROTECTED] as the e-mail address, for
| > example. How this happens has left me stumped. This is very
> 1. I have had cases where a user's .prefs file has been changed.
>What I mean is that [EMAIL PROTECTED] has ended up
>having [EMAIL PROTECTED] as the e-mail address, for
>example. How this happens has left me stumped. This is very
>dangerous, because then, when [EMAIL PROTECTED] s
>
> Hello Squirrels ;)
>
>
> I am one happy sysadmin who uses this wonderful piece of code.
> Thanks to Paul and Ryan for the good job.
>
> However, I do have two problems at the moment and I am not sure it's
> the fault of the plugin, the fault of SM, or my own fault.
>
> 1. I have had cases where
Hello Squirrels ;)
I am one happy sysadmin who uses this wonderful piece of code.
Thanks to Paul and Ryan for the good job.
However, I do have two problems at the moment and I am not sure it's
the fault of the plugin, the fault of SM, or my own fault.
1. I have had cases where a user's .prefs
12 matches
Mail list logo
