| 1 |
On Monday 25 January 2010 22:12:05 Kyle Bader wrote: |
| 2 |
> This is rather blunt but... |
| 3 |
> |
| 4 |
> Find / -name "*"|xargs touch |
| 5 |
|
| 6 |
This might work better: |
| 7 |
|
| 8 |
find / -mtime -0 | xargs touch |
| 9 |
|
| 10 |
I *think* that will find everything with an mtime less than 0 (i.e. in the |
| 11 |
future). |
| 12 |
|
| 13 |
untested, it might eat kittens, ymmv, test it out yourself first and all that, |
| 14 |
yada yada yada .... |
| 15 |
|
| 16 |
|
| 17 |
|
| 18 |
> |
| 19 |
> On 1/25/10, Mark Knecht <markknecht@×××××.com> wrote: |
| 20 |
> > Hi, |
| 21 |
> > I've just rebuilt my new machine this morning playing with |
| 22 |
> > different ways to do things. Unfortunately I went sort of fast and |
| 23 |
> > forgot to set date/time/timezone. (Doing too much from memory this |
| 24 |
> > time.) Now when I try to set the system time to local and the hardware |
| 25 |
> > clock to Pacific time and turn on ntp-client/ntpd I'm getting lots of |
| 26 |
> > complaints about modification times in the future. |
| 27 |
> > |
| 28 |
> > This is completely my mistake and I can start over and fix it in a |
| 29 |
> > couple of hours but I'm wondering if there's an easy way out of this? |
| 30 |
> > |
| 31 |
> > Thanks, |
| 32 |
> > Mark |
| 33 |
> |
| 34 |
|
| 35 |
-- |
| 36 |
alan dot mckinnon at gmail dot com |
Archives