On Sunday 13 July 2014 17:30:43 Mick wrote:
> On Sunday 13 Jul 2014 16:54:54 Dale wrote:
> > Dale wrote:
> > > Mick wrote:
> > >> Please try this: Go the PC that keeps getting these messages in its
> > >> logs. Run: $ chrony chronyc> password password:
> > >> If the passwd is wrong, or some
> > >>
On Sunday 13 Jul 2014 16:54:54 Dale wrote:
> Dale wrote:
> > Mick wrote:
> >> Please try this: Go the PC that keeps getting these messages in its
> >> logs. Run: $ chrony chronyc> password password:
> >> If the passwd is wrong, or some
> >> characters are incompatible with the terminal, then you w
Dale wrote:
> Mick wrote:
>> Please try this: Go the PC that keeps getting these messages in its
>> logs. Run: $ chrony chronyc> password password:
>> If the passwd is wrong, or some
>> characters are incompatible with the terminal, then you will get:
>> "Password: 501 Not authorised --- Reply not
Mick wrote:
> Please try this: Go the PC that keeps getting these messages in its
> logs. Run: $ chrony chronyc> password password:
> If the passwd is wrong, or some
> characters are incompatible with the terminal, then you will get:
> "Password: 501 Not authorised --- Reply not authenticated" You
On Sunday 13 Jul 2014 10:20:47 Peter Humphrey wrote:
> On Tuesday 01 July 2014 15:01:33 I wrote:
> > On Tuesday 01 July 2014 12:13:39 Mick wrote:
> > > On Tuesday 01 Jul 2014 10:48:12 Peter Humphrey wrote:
> > > > Hell list,
> > > >
> > > > I don't know when it started, but recently I've been gett
On Tuesday 01 July 2014 15:01:33 I wrote:
> On Tuesday 01 July 2014 12:13:39 Mick wrote:
> > On Tuesday 01 Jul 2014 10:48:12 Peter Humphrey wrote:
> > > Hell list,
> > >
> > > I don't know when it started, but recently I've been getting error
> > > e-mails
> > > from cron, thus:
> > >
> > > Passw
On Tuesday 01 July 2014 12:13:39 Mick wrote:
> On Tuesday 01 Jul 2014 10:48:12 Peter Humphrey wrote:
> > Hell list,
> >
> > I don't know when it started, but recently I've been getting error e-mails
> > from cron, thus:
> >
> > Password: 501 Not authorised --- Reply not authenticated
> >
> > The
On Tuesday 01 July 2014 12:57:53 Alan McKinnon wrote:
> the error looks like an http error.
> Got any crons running wget, curl or lynx?
I thought so too, but no, I have none of those called by cron. I do have an
rsync job every 5 minutes to back up my home directory to the file server, and
I th
Alan McKinnon wrote:
> On 01/07/2014 11:48, Peter Humphrey wrote:
>> Hell list,
>>
>> I don't know when it started, but recently I've been getting error e-mails
>> from cron, thus:
>>
>> Password: 501 Not authorised --- Reply not authenticated
>>
>> They're all timed at 03:10:0x, i.e. one minute a
On Tuesday 01 Jul 2014 10:48:12 Peter Humphrey wrote:
> Hell list,
>
> I don't know when it started, but recently I've been getting error e-mails
> from cron, thus:
>
> Password: 501 Not authorised --- Reply not authenticated
>
> They're all timed at 03:10:0x, i.e. one minute after cron.daily ta
On 01/07/2014 11:48, Peter Humphrey wrote:
> Hell list,
>
> I don't know when it started, but recently I've been getting error e-mails
> from cron, thus:
>
> Password: 501 Not authorised --- Reply not authenticated
>
> They're all timed at 03:10:0x, i.e. one minute after cron.daily tasks are
>
Hell list,
I don't know when it started, but recently I've been getting error e-mails
from cron, thus:
Password: 501 Not authorised --- Reply not authenticated
They're all timed at 03:10:0x, i.e. one minute after cron.daily tasks are run,
and they occur at 7- or 8-day intervals. The only files
12 matches
Mail list logo
