| 1 |
Mark Haney, mused, then expounded: |
| 2 |
> Bob Sanders wrote: |
| 3 |
> >Mark Haney, mused, then expounded: |
| 4 |
> >>I've got a warning (or error) when I boot up or shot down saying that |
| 5 |
> >>/etc/conf.d/clock is still set to 'Factory'. However, when I look at |
| 6 |
> >>that file it actually set to 'local'. Is anyone else seeing this? |
| 7 |
> >> |
| 8 |
> > |
| 9 |
> >Did you uncomment the "#TIMEZONE="Factory"" and change it to your |
| 10 |
> >local timzone? |
| 11 |
> > |
| 12 |
> >Bob |
| 13 |
> >- |
| 14 |
> Well, I don't have that option in my /etc/conf.d/clock file. I know I |
| 15 |
> updated a few things and went through dispatch-conf, which is when I |
| 16 |
> noticed, but on any files I haven't edited, I generally select the 'use |
| 17 |
> new' option. So either this file didn't get updated properly or something. |
| 18 |
> |
| 19 |
|
| 20 |
It's part of - |
| 21 |
|
| 22 |
sys-apps/baselayout-1.12.9 (/etc/conf.d/clock) |
| 23 |
|
| 24 |
Perhaps check the emerge? Or simply add the TIMEZONE="" statement? |
| 25 |
|
| 26 |
Bob |
| 27 |
- |
| 28 |
-- |
| 29 |
gentoo-amd64@g.o mailing list |
Archives