Re: CRON: Authentication token is no longer valid; new one required

2015-02-07 Thread Bob Proulx
ML mail wrote: > Bob Proulx wrote: > > It is the state of an expired password that is a problem. > > ... > > What does this say? Example from a system of mine. > > > > $ passwd --status root > > root P 05/01/2010 0 9 7 -1 > The result of running passwd --status tells me that the password

Re: CRON: Authentication token is no longer valid; new one required

2015-02-06 Thread Reco
Hi. On Fri, 6 Feb 2015 19:39:42 + (UTC) ML mail wrote: > So if I understand correctly it is not possible to use cron.d with simply the > "!" character in the shadow file? I need to have "!" + password? do I > understand that correctly? My current configuration is: # head -1 /etc/shadow

Re: CRON: Authentication token is no longer valid; new one required

2015-02-06 Thread ML mail
So if I understand correctly it is not possible to use cron.d with simply the "!" character in the shadow file? I need to have "!" + password? do I understand that correctly? On Friday, February 6, 2015 12:24 PM, Reco wrote: Hi. On Fri, Feb 06, 2015 at 05:07:58AM -0500, wolf.hal...@gmail.com

Re: CRON: Authentication token is no longer valid; new one required

2015-02-06 Thread Reco
Hi. On Fri, Feb 06, 2015 at 05:07:58AM -0500, wolf.hal...@gmail.com wrote: > The '!' Means root login is disabled, not that the root account is disabled. > su - > With a blank root password lets anyone switch user to root without slowing > down to crack the password. That is not a safe goal.

Re: CRON: Authentication token is no longer valid; new one required

2015-02-06 Thread wolf . halton
The '!' Means root login is disabled, not that the root account is disabled. su - With a blank root password lets anyone switch user to root without slowing down to crack the password. That is not a safe goal. Sent from my iPhone > On Feb 6, 2015, at 3:41 AM, ML mail wrote: > > The result o

Re: CRON: Authentication token is no longer valid; new one required

2015-02-06 Thread ML mail
The result of running passwd --status tells me that the password needs to be changed as actually I had in my /etc/shadow file only a "!" as password in order to safely disable the root account. It looks like this is not compatible with the cron.d system. I have changed the password and then lock

Re: CRON: Authentication token is no longer valid; new one required

2015-02-05 Thread Bob Proulx
ML mail wrote: > I am trying to run cron from /etc/cron.d with the root account which > has password disabled in order not to be able to login as root but > when the cron entry wants to run it simply does not and show the > following error message in the log file: > > CRON[16785]: Authentication t