Menu
▾
▴
astlinux-devel — The AstLinux development environment, compilation, etc
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
(41) |
Apr
(35) |
May
(18) |
Jun
(5) |
Jul
(4) |
Aug
(37) |
Sep
(9) |
Oct
(20) |
Nov
(50) |
Dec
(217) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(212) |
Feb
(76) |
Mar
(113) |
Apr
(88) |
May
(130) |
Jun
(54) |
Jul
(208) |
Aug
(223) |
Sep
(112) |
Oct
(63) |
Nov
(131) |
Dec
(103) |
| 2010 |
Jan
(247) |
Feb
(130) |
Mar
(43) |
Apr
(92) |
May
(40) |
Jun
(43) |
Jul
(43) |
Aug
(80) |
Sep
(44) |
Oct
(74) |
Nov
(21) |
Dec
(46) |
| 2011 |
Jan
(36) |
Feb
(11) |
Mar
(21) |
Apr
(33) |
May
(4) |
Jun
(12) |
Jul
(5) |
Aug
(20) |
Sep
|
Oct
(64) |
Nov
(26) |
Dec
(71) |
| 2012 |
Jan
(13) |
Feb
(24) |
Mar
(11) |
Apr
(2) |
May
(10) |
Jun
(5) |
Jul
(13) |
Aug
(7) |
Sep
(26) |
Oct
(22) |
Nov
(17) |
Dec
(16) |
| 2013 |
Jan
(6) |
Feb
(6) |
Mar
(6) |
Apr
(8) |
May
(20) |
Jun
|
Jul
(1) |
Aug
(4) |
Sep
(18) |
Oct
(3) |
Nov
(14) |
Dec
(33) |
| 2014 |
Jan
(26) |
Feb
(6) |
Mar
(69) |
Apr
(10) |
May
|
Jun
(8) |
Jul
(18) |
Aug
(22) |
Sep
(19) |
Oct
(17) |
Nov
|
Dec
(4) |
| 2015 |
Jan
(14) |
Feb
(18) |
Mar
|
Apr
|
May
(26) |
Jun
(8) |
Jul
(9) |
Aug
(10) |
Sep
(15) |
Oct
(2) |
Nov
(30) |
Dec
(33) |
| 2016 |
Jan
(1) |
Feb
(24) |
Mar
(19) |
Apr
(1) |
May
|
Jun
(3) |
Jul
(1) |
Aug
(1) |
Sep
(20) |
Oct
(5) |
Nov
(14) |
Dec
(4) |
| 2017 |
Jan
(15) |
Feb
(35) |
Mar
(10) |
Apr
(9) |
May
(14) |
Jun
(33) |
Jul
(1) |
Aug
(27) |
Sep
(7) |
Oct
|
Nov
(10) |
Dec
(15) |
| 2018 |
Jan
(29) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(11) |
Jun
|
Jul
(1) |
Aug
(8) |
Sep
(11) |
Oct
(22) |
Nov
(9) |
Dec
(13) |
| 2019 |
Jan
(1) |
Feb
(7) |
Mar
(3) |
Apr
(21) |
May
(34) |
Jun
(36) |
Jul
(18) |
Aug
(17) |
Sep
(19) |
Oct
(8) |
Nov
(3) |
Dec
|
| 2020 |
Jan
|
Feb
(4) |
Mar
(8) |
Apr
(29) |
May
(50) |
Jun
(8) |
Jul
(2) |
Aug
(10) |
Sep
(1) |
Oct
(7) |
Nov
(9) |
Dec
(19) |
| 2021 |
Jan
(2) |
Feb
(9) |
Mar
(6) |
Apr
(21) |
May
(13) |
Jun
(11) |
Jul
(2) |
Aug
(1) |
Sep
(3) |
Oct
(26) |
Nov
(2) |
Dec
(16) |
| 2022 |
Jan
(8) |
Feb
(7) |
Mar
(1) |
Apr
(13) |
May
(1) |
Jun
(4) |
Jul
(4) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
| 2023 |
Jan
(2) |
Feb
(3) |
Mar
(16) |
Apr
|
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(13) |
Sep
(8) |
Oct
(6) |
Nov
(4) |
Dec
|
| 2024 |
Jan
(3) |
Feb
(3) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(5) |
Aug
|
Sep
(1) |
Oct
|
Nov
(5) |
Dec
|
| 2025 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
(11) |
May
(1) |
Jun
(9) |
Jul
(18) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
1
|
2
|
3
|
4
|
5
|
|
6
(2) |
7
|
8
(1) |
9
|
10
|
11
(2) |
12
(6) |
|
13
(2) |
14
(4) |
15
|
16
(7) |
17
|
18
|
19
|
|
20
(13) |
21
|
22
(2) |
23
(1) |
24
|
25
(1) |
26
|
|
27
|
28
(2) |
29
|
30
|
|
|
|
|
From: Lonnie A. <li...@lo...> - 2010-06-14 15:13:10
|
Ron, The sshd banner can be set with the NETISSUE variable. I understand what you are saying, don't really know if 'history' is why it is the way it is, or if there was a good reason. Lonnie On Jun 14, 2010, at 10:00 AM, Ron Byer wrote: > Yes, the diff is backwards,my apologies. > > The custom changes are not necessary, but sure save my sanity on occasion: > > ClientAliveInterval 60 > ClientAliveCountMax 20 > > Also I change the banner. > > It looks like the line > if [ ! -f /tmp/etc/sshd_config ]; then > > needs to be /tmp/etc/ssh/sshd_config > > > The practical result of this is that the /mnt/kd/ssh/sshd_config, which is linked to /tmp/etc/ssh/sshd_config doesn't get overwritten. Whether that was the intent or not is unclear, and I haven't dwelled on it. > > It was a little odd to see stuff getting overwritten on the kd, which doesn't usually happen. Would think that the consistent approach would be, instead of linking /tmp/etc/ssh/sshd_config to the kd version, instead: > - generate the /tmp/etc/ssh/sshd_config from scratch on every boot (essentially when /etc/init.d/sshd init runs). > - concatenate the contents of /mnt/kd/sshd, which should then only contain additional/different parameters from the standard. > > Would have to check to see if restating a conf parameter (like the banner) would be a problem, or sshd would simply use the last definition. > > Anyway, my $0.02, use or discard as you fellows see fit. > > Ron > > > Lonnie Abelbeck wrote: >> On Jun 11, 2010, at 4:19 PM, Ron Byer wrote: >> >> >> >>> From: "Ron Byer Jr." <ro...@ne...> >>> >>> Date: June 11, 2010 1:25:32 PM CDT >>> To: AstLinux Developers Mailing List >>> <ast...@li...> >>> >>> Subject: really minor issue >>> >>> >>> Greetings, >>> >>> I think the following microscopic change in /etc/init.d/sshd is in order. >>> >>> --- sshd Fri Jun 11 14:18:28 2010 >>> +++ sshd.old Fri Jun 11 14:21:25 2010 >>> @@ -17,7 +17,7 @@ >>> # if we change the values for SSHDPORT or SSHDROOT, but >>> # /mnt/kd/ssh/sshd_config exists, it will not be updated. >>> # it will need to be removed to get these new values. >>> - if [ ! -f /tmp/etc/ssh/sshd_config ]; then >>> + if [ ! -f /tmp/etc/sshd_config ]; then >>> : > /tmp/etc/ssh/sshd_config >>> >>> if [ -L /tmp/etc/ssh ]; then >>> >>> >>> the way it was, any custom settings in /mnt/kd/ssh/sshd_config would get obliterated on each reboot. >>> >>> >>> Thanks and regards, >>> >>> Ron >>> >>> >> >> Ron, >> >> Your 'diff' is backwards... but as the comment states "/mnt/kd/ssh/sshd_config" needs to be regenerated at every boot. >> >> What sshd_config custom changes do you need? >> >> Why the [ ! -f /tmp/etc/sshd_config ] test is necessary I'm not sure, maybe Philip knows. >> >> Lonnie >> >> >> >> ------------------------------------------------------------------------------ >> ThinkGeek and WIRED's GeekDad team up for the Ultimate >> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >> lucky parental unit. See the prize list and enter to win: >> >> http://p.sf.net/sfu/thinkgeek-promo >> >> _______________________________________________ >> Astlinux-devel mailing list >> >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> >> >> Donations to support AstLinux are graciously accepted via PayPal to >> pa...@kr... >> . >> >> >> > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo_______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Ron B. <ron...@ne...> - 2010-06-14 15:00:39
|
Yes, the diff is backwards,my apologies. The custom changes are not necessary, but sure save my sanity on occasion: ClientAliveInterval 60 ClientAliveCountMax 20 Also I change the banner. It looks like the line if [ ! -f /tmp/etc/sshd_config ]; then needs to be /tmp/etc/ssh/sshd_config The practical result of this is that the /mnt/kd/ssh/sshd_config, which is linked to /tmp/etc/ssh/sshd_config doesn't get overwritten. Whether that was the intent or not is unclear, and I haven't dwelled on it. It was a little odd to see stuff getting overwritten on the kd, which doesn't usually happen. Would think that the consistent approach would be, instead of linking /tmp/etc/ssh/sshd_config to the kd version, instead: - generate the /tmp/etc/ssh/sshd_config from scratch on every boot (essentially when /etc/init.d/sshd init runs). - concatenate the contents of /mnt/kd/sshd, which should then only contain additional/different parameters from the standard. Would have to check to see if restating a conf parameter (like the banner) would be a problem, or sshd would simply use the last definition. Anyway, my $0.02, use or discard as you fellows see fit. Ron Lonnie Abelbeck wrote: > On Jun 11, 2010, at 4:19 PM, Ron Byer wrote: > > >> From: "Ron Byer Jr." <ro...@ne...> >> Date: June 11, 2010 1:25:32 PM CDT >> To: AstLinux Developers Mailing List <ast...@li...> >> Subject: really minor issue >> >> >> Greetings, >> >> I think the following microscopic change in /etc/init.d/sshd is in order. >> >> --- sshd Fri Jun 11 14:18:28 2010 >> +++ sshd.old Fri Jun 11 14:21:25 2010 >> @@ -17,7 +17,7 @@ >> # if we change the values for SSHDPORT or SSHDROOT, but >> # /mnt/kd/ssh/sshd_config exists, it will not be updated. >> # it will need to be removed to get these new values. >> - if [ ! -f /tmp/etc/ssh/sshd_config ]; then >> + if [ ! -f /tmp/etc/sshd_config ]; then >> : > /tmp/etc/ssh/sshd_config >> >> if [ -L /tmp/etc/ssh ]; then >> >> >> the way it was, any custom settings in /mnt/kd/ssh/sshd_config would get obliterated on each reboot. >> >> >> Thanks and regards, >> >> Ron >> > > Ron, > > Your 'diff' is backwards... but as the comment states "/mnt/kd/ssh/sshd_config" needs to be regenerated at every boot. > > What sshd_config custom changes do you need? > > Why the [ ! -f /tmp/etc/sshd_config ] test is necessary I'm not sure, maybe Philip knows. > > Lonnie > > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > |
|
From: Darrick H. <dha...@dj...> - 2010-06-14 12:59:04
|
This is normal behavior. These are informational notices when the time changes on the system. On 06/14/2010 03:05 AM, Tom Chadwin wrote: > For info, this appears to be occurring in one of our five boxes (all 0.7.2 > net5501s). Time-related logs below: > > No Dahdi hw (3 boxes): > > Jun 14 06:36:29 coquetdalepbx daemon.info ntpd[2233]: synchronized to > 193.238.80.20, stratum 3 > Jun 14 06:50:57 coquetdalepbx daemon.notice ntpd[2233]: time reset -0.528836 > s > Jun 14 06:50:57 coquetdalepbx user.info kernel: dahdi: Detected time shift. > Jun 14 06:54:55 coquetdalepbx daemon.info ntpd[2233]: synchronized to > LOCAL(0), stratum 5 > Jun 14 06:57:01 coquetdalepbx daemon.info ntpd[2233]: synchronized to > 193.238.80.20, stratum 3 > Jun 14 07:11:10 coquetdalepbx daemon.notice ntpd[2233]: time reset -0.547192 > s > Jun 14 07:11:10 coquetdalepbx user.info kernel: dahdi: Detected time shift. > Jun 14 07:14:34 coquetdalepbx daemon.info ntpd[2233]: synchronized to > LOCAL(0), stratum 5 > Jun 14 07:16:44 coquetdalepbx daemon.info ntpd[2233]: synchronized to > 193.238.80.20, stratum 3 > Jun 14 07:30:44 coquetdalepbx daemon.notice ntpd[2233]: time reset -0.533600 > s > Jun 14 07:30:44 coquetdalepbx user.info kernel: dahdi: Detected time shift. > Jun 14 07:35:04 coquetdalepbx daemon.info ntpd[2233]: synchronized to > LOCAL(0), stratum 5 > Jun 14 07:36:10 coquetdalepbx daemon.info ntpd[2233]: synchronized to > 193.238.80.20, stratum 3 > Jun 14 07:50:12 coquetdalepbx daemon.notice ntpd[2233]: time reset -0.528582 > s > Jun 14 07:50:12 coquetdalepbx user.info kernel: dahdi: Detected time shift. > Jun 14 07:54:26 coquetdalepbx daemon.info ntpd[2233]: synchronized to > LOCAL(0), stratum 5 > Jun 14 07:55:29 coquetdalepbx daemon.info ntpd[2233]: synchronized to > 193.238.80.20, stratum 3 > > Jun 13 11:49:49 eastburnpbx daemon.notice ntpd[2257]: kernel time sync > status change 0001 > Jun 13 12:24:01 eastburnpbx daemon.notice ntpd[2257]: kernel time sync > status change 4001 > Jun 13 14:06:28 eastburnpbx daemon.notice ntpd[2257]: kernel time sync > status change 0001 > Jun 13 14:40:37 eastburnpbx daemon.notice ntpd[2257]: kernel time sync > status change 4001 > Jun 13 15:48:52 eastburnpbx daemon.notice ntpd[2257]: kernel time sync > status change 0001 > Jun 13 16:57:10 eastburnpbx daemon.notice ntpd[2257]: kernel time sync > status change 4001 > Jun 13 17:14:16 eastburnpbx daemon.notice ntpd[2257]: kernel time sync > status change 0001 > Jun 13 18:22:32 eastburnpbx daemon.notice ntpd[2257]: kernel time sync > status change 4001 > Jun 13 18:39:37 eastburnpbx daemon.notice ntpd[2257]: kernel time sync > status change 0001 > Jun 13 19:30:51 eastburnpbx daemon.notice ntpd[2257]: kernel time sync > status change 4001 > Jun 13 20:04:59 eastburnpbx daemon.notice ntpd[2257]: kernel time sync > status change 0001 > Jun 13 21:47:27 eastburnpbx daemon.notice ntpd[2257]: kernel time sync > status change 4001 > Jun 13 22:38:41 eastburnpbx daemon.notice ntpd[2257]: kernel time sync > status change 0001 > > Jun 14 01:55:00 oncebrewedpbx daemon.notice ntpd[2338]: kernel time sync > status change 4001 > Jun 14 04:28:42 oncebrewedpbx daemon.notice ntpd[2338]: kernel time sync > status change 0001 > Jun 14 06:28:16 oncebrewedpbx daemon.notice ntpd[2338]: kernel time sync > status change 4001 > Jun 14 06:45:21 oncebrewedpbx daemon.notice ntpd[2338]: kernel time sync > status change 0001 > > Dahdi card (2 boxes): > > Jun 13 09:21:33 ingrampbx daemon.notice ntpd[2205]: kernel time sync status > change 0001 > Jun 13 10:46:52 ingrampbx daemon.notice ntpd[2205]: kernel time sync status > change 4001 > Jun 13 11:38:04 ingrampbx daemon.notice ntpd[2205]: kernel time sync status > change 0001 > Jun 13 12:29:18 ingrampbx daemon.notice ntpd[2205]: kernel time sync status > change 4001 > Jun 13 12:46:23 ingrampbx daemon.notice ntpd[2205]: kernel time sync status > change 0001 > Jun 13 13:54:43 ingrampbx daemon.notice ntpd[2205]: kernel time sync status > change 4001 > Jun 13 14:46:01 ingrampbx daemon.notice ntpd[2205]: kernel time sync status > change 0001 > Jun 13 15:20:10 ingrampbx daemon.notice ntpd[2205]: kernel time sync status > change 4001 > Jun 13 15:37:16 ingrampbx daemon.notice ntpd[2205]: kernel time sync status > change 0001 > Jun 13 16:45:32 ingrampbx daemon.notice ntpd[2205]: kernel time sync status > change 4001 > Jun 13 17:53:49 ingrampbx daemon.notice ntpd[2205]: kernel time sync status > change 0001 > Jun 13 18:27:58 ingrampbx daemon.notice ntpd[2205]: kernel time sync status > change 4001 > Jun 13 19:19:10 ingrampbx daemon.notice ntpd[2205]: kernel time sync status > change 0001 > Jun 13 20:10:22 ingrampbx daemon.notice ntpd[2205]: kernel time sync status > change 4001 > > May 26 03:17:45 haltwhistlepbx daemon.info ntpd[2268]: synchronized to > 83.169.19.225, stratum 2 > May 26 07:09:21 haltwhistlepbx daemon.notice ntpd[2268]: kernel time sync > status change 4001 > May 26 07:26:24 haltwhistlepbx daemon.notice ntpd[2268]: kernel time sync > status change 0001 > May 26 08:00:52 haltwhistlepbx daemon.notice ntpd[2268]: time reset > -0.190380 s > May 26 08:00:52 haltwhistlepbx daemon.notice ntpd[2268]: kernel time sync > status change 4001 > May 26 08:05:08 haltwhistlepbx daemon.info ntpd[2268]: synchronized to > LOCAL(0), stratum 5 > May 26 08:05:08 haltwhistlepbx daemon.notice ntpd[2268]: kernel time sync > status change 0001 > May 26 08:06:13 haltwhistlepbx daemon.info ntpd[2268]: synchronized to > 83.169.19.225, stratum 2 > May 26 11:18:42 haltwhistlepbx daemon.info ntpd[2268]: synchronized to > LOCAL(0), stratum 5 > May 26 11:20:09 haltwhistlepbx daemon.info ntpd[2268]: synchronized to > 83.169.19.225, stratum 2 > May 26 13:16:38 haltwhistlepbx daemon.info ntpd[2268]: synchronized to > LOCAL(0), stratum 5 > > Anything of interest? > > Tom > > > ________________________________ > > From: John Reynolds [mailto:rey...@gm...] > Sent: 08 June 2010 04:57 > To: AstLinux Developers Mailing List > Subject: Re: [Astlinux-devel] Dahdi: "Detected time shift." > > > > > On Sun, Jun 6, 2010 at 1:40 PM, Darrick Hartman > <dha...@dj...> wrote: > > > On 06/06/2010 02:30 PM, Philip Prindeville wrote: > > I'm running 3966 and seeing a lot of: > > > > Jun 5 23:40:43 pbx user.info kernel: dahdi: Detected time > shift. > > Jun 6 00:00:58 pbx user.info kernel: dahdi: Detected time > shift. > > Jun 6 00:21:05 pbx user.info kernel: dahdi: Detected time > shift. > > Jun 6 00:40:42 pbx user.info kernel: dahdi: Detected time > shift. > > Jun 6 01:00:27 pbx user.info kernel: dahdi: Detected time > shift. > > Jun 6 01:21:29 pbx user.info kernel: dahdi: Detected time > shift. > > Jun 6 01:41:00 pbx user.info kernel: dahdi: Detected time > shift. > > Jun 6 02:00:52 pbx user.info kernel: dahdi: Detected time > shift. > > Jun 6 02:21:02 pbx user.info kernel: dahdi: Detected time > shift. > > Jun 6 02:41:19 pbx user.info kernel: dahdi: Detected time > shift. > > Jun 6 03:01:06 pbx user.info kernel: dahdi: Detected time > shift. > > Jun 6 03:20:49 pbx user.info kernel: dahdi: Detected time > shift. > > Jun 6 03:40:38 pbx user.info kernel: dahdi: Detected time > shift. > > Jun 6 04:00:00 pbx user.info kernel: dahdi: Detected time > shift. > > Jun 6 04:20:24 pbx user.info kernel: dahdi: Detected time > shift. > > > > > > Anyone else seeing this? > > > > This is with 2.3.0... > > > > I haven't see that on any of the systems I have with dahdi > hardware. > Looks like the system time is changing and being sync'ed > every 20 minutes. > > > > -- > Darrick Hartman > DJH Solutions, LLC > http://www.djhsolutions.com > > > > > I'm seeing this... but I'm not smart enough to know if it is related > to your time messages: > > > Jun 7 10:29:20 pbx daemon.notice ntpd[1188]: kernel time sync > status change 4001 > Jun 7 10:46:25 pbx daemon.notice ntpd[1188]: kernel time sync > status change 0001 > Jun 7 11:20:35 pbx daemon.notice ntpd[1188]: kernel time sync > status change 4001 > Jun 7 11:54:41 pbx daemon.notice ntpd[1188]: kernel time sync > status change 0001 > Jun 7 13:37:09 pbx daemon.notice ntpd[1188]: kernel time sync > status change 4001 > Jun 7 14:28:26 pbx daemon.notice ntpd[1188]: kernel time sync > status change 0001 > Jun 7 15:19:39 pbx daemon.notice ntpd[1188]: kernel time sync > status change 4001 > Jun 7 16:27:58 pbx daemon.notice ntpd[1188]: kernel time sync > status change 0001 > Jun 7 17:53:18 pbx daemon.notice ntpd[1188]: kernel time sync > status change 4001 > > > perhaps this is perfectly normal... I just don't have the expirence > to know better. > > John R. > > > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com |
|
From: Tom C. <nnp...@go...> - 2010-06-14 08:06:04
|
For info, this appears to be occurring in one of our five boxes (all 0.7.2 net5501s). Time-related logs below: No Dahdi hw (3 boxes): Jun 14 06:36:29 coquetdalepbx daemon.info ntpd[2233]: synchronized to 193.238.80.20, stratum 3 Jun 14 06:50:57 coquetdalepbx daemon.notice ntpd[2233]: time reset -0.528836 s Jun 14 06:50:57 coquetdalepbx user.info kernel: dahdi: Detected time shift. Jun 14 06:54:55 coquetdalepbx daemon.info ntpd[2233]: synchronized to LOCAL(0), stratum 5 Jun 14 06:57:01 coquetdalepbx daemon.info ntpd[2233]: synchronized to 193.238.80.20, stratum 3 Jun 14 07:11:10 coquetdalepbx daemon.notice ntpd[2233]: time reset -0.547192 s Jun 14 07:11:10 coquetdalepbx user.info kernel: dahdi: Detected time shift. Jun 14 07:14:34 coquetdalepbx daemon.info ntpd[2233]: synchronized to LOCAL(0), stratum 5 Jun 14 07:16:44 coquetdalepbx daemon.info ntpd[2233]: synchronized to 193.238.80.20, stratum 3 Jun 14 07:30:44 coquetdalepbx daemon.notice ntpd[2233]: time reset -0.533600 s Jun 14 07:30:44 coquetdalepbx user.info kernel: dahdi: Detected time shift. Jun 14 07:35:04 coquetdalepbx daemon.info ntpd[2233]: synchronized to LOCAL(0), stratum 5 Jun 14 07:36:10 coquetdalepbx daemon.info ntpd[2233]: synchronized to 193.238.80.20, stratum 3 Jun 14 07:50:12 coquetdalepbx daemon.notice ntpd[2233]: time reset -0.528582 s Jun 14 07:50:12 coquetdalepbx user.info kernel: dahdi: Detected time shift. Jun 14 07:54:26 coquetdalepbx daemon.info ntpd[2233]: synchronized to LOCAL(0), stratum 5 Jun 14 07:55:29 coquetdalepbx daemon.info ntpd[2233]: synchronized to 193.238.80.20, stratum 3 Jun 13 11:49:49 eastburnpbx daemon.notice ntpd[2257]: kernel time sync status change 0001 Jun 13 12:24:01 eastburnpbx daemon.notice ntpd[2257]: kernel time sync status change 4001 Jun 13 14:06:28 eastburnpbx daemon.notice ntpd[2257]: kernel time sync status change 0001 Jun 13 14:40:37 eastburnpbx daemon.notice ntpd[2257]: kernel time sync status change 4001 Jun 13 15:48:52 eastburnpbx daemon.notice ntpd[2257]: kernel time sync status change 0001 Jun 13 16:57:10 eastburnpbx daemon.notice ntpd[2257]: kernel time sync status change 4001 Jun 13 17:14:16 eastburnpbx daemon.notice ntpd[2257]: kernel time sync status change 0001 Jun 13 18:22:32 eastburnpbx daemon.notice ntpd[2257]: kernel time sync status change 4001 Jun 13 18:39:37 eastburnpbx daemon.notice ntpd[2257]: kernel time sync status change 0001 Jun 13 19:30:51 eastburnpbx daemon.notice ntpd[2257]: kernel time sync status change 4001 Jun 13 20:04:59 eastburnpbx daemon.notice ntpd[2257]: kernel time sync status change 0001 Jun 13 21:47:27 eastburnpbx daemon.notice ntpd[2257]: kernel time sync status change 4001 Jun 13 22:38:41 eastburnpbx daemon.notice ntpd[2257]: kernel time sync status change 0001 Jun 14 01:55:00 oncebrewedpbx daemon.notice ntpd[2338]: kernel time sync status change 4001 Jun 14 04:28:42 oncebrewedpbx daemon.notice ntpd[2338]: kernel time sync status change 0001 Jun 14 06:28:16 oncebrewedpbx daemon.notice ntpd[2338]: kernel time sync status change 4001 Jun 14 06:45:21 oncebrewedpbx daemon.notice ntpd[2338]: kernel time sync status change 0001 Dahdi card (2 boxes): Jun 13 09:21:33 ingrampbx daemon.notice ntpd[2205]: kernel time sync status change 0001 Jun 13 10:46:52 ingrampbx daemon.notice ntpd[2205]: kernel time sync status change 4001 Jun 13 11:38:04 ingrampbx daemon.notice ntpd[2205]: kernel time sync status change 0001 Jun 13 12:29:18 ingrampbx daemon.notice ntpd[2205]: kernel time sync status change 4001 Jun 13 12:46:23 ingrampbx daemon.notice ntpd[2205]: kernel time sync status change 0001 Jun 13 13:54:43 ingrampbx daemon.notice ntpd[2205]: kernel time sync status change 4001 Jun 13 14:46:01 ingrampbx daemon.notice ntpd[2205]: kernel time sync status change 0001 Jun 13 15:20:10 ingrampbx daemon.notice ntpd[2205]: kernel time sync status change 4001 Jun 13 15:37:16 ingrampbx daemon.notice ntpd[2205]: kernel time sync status change 0001 Jun 13 16:45:32 ingrampbx daemon.notice ntpd[2205]: kernel time sync status change 4001 Jun 13 17:53:49 ingrampbx daemon.notice ntpd[2205]: kernel time sync status change 0001 Jun 13 18:27:58 ingrampbx daemon.notice ntpd[2205]: kernel time sync status change 4001 Jun 13 19:19:10 ingrampbx daemon.notice ntpd[2205]: kernel time sync status change 0001 Jun 13 20:10:22 ingrampbx daemon.notice ntpd[2205]: kernel time sync status change 4001 May 26 03:17:45 haltwhistlepbx daemon.info ntpd[2268]: synchronized to 83.169.19.225, stratum 2 May 26 07:09:21 haltwhistlepbx daemon.notice ntpd[2268]: kernel time sync status change 4001 May 26 07:26:24 haltwhistlepbx daemon.notice ntpd[2268]: kernel time sync status change 0001 May 26 08:00:52 haltwhistlepbx daemon.notice ntpd[2268]: time reset -0.190380 s May 26 08:00:52 haltwhistlepbx daemon.notice ntpd[2268]: kernel time sync status change 4001 May 26 08:05:08 haltwhistlepbx daemon.info ntpd[2268]: synchronized to LOCAL(0), stratum 5 May 26 08:05:08 haltwhistlepbx daemon.notice ntpd[2268]: kernel time sync status change 0001 May 26 08:06:13 haltwhistlepbx daemon.info ntpd[2268]: synchronized to 83.169.19.225, stratum 2 May 26 11:18:42 haltwhistlepbx daemon.info ntpd[2268]: synchronized to LOCAL(0), stratum 5 May 26 11:20:09 haltwhistlepbx daemon.info ntpd[2268]: synchronized to 83.169.19.225, stratum 2 May 26 13:16:38 haltwhistlepbx daemon.info ntpd[2268]: synchronized to LOCAL(0), stratum 5 Anything of interest? Tom ________________________________ From: John Reynolds [mailto:rey...@gm...] Sent: 08 June 2010 04:57 To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Dahdi: "Detected time shift." On Sun, Jun 6, 2010 at 1:40 PM, Darrick Hartman <dha...@dj...> wrote: On 06/06/2010 02:30 PM, Philip Prindeville wrote: > I'm running 3966 and seeing a lot of: > > Jun 5 23:40:43 pbx user.info kernel: dahdi: Detected time shift. > Jun 6 00:00:58 pbx user.info kernel: dahdi: Detected time shift. > Jun 6 00:21:05 pbx user.info kernel: dahdi: Detected time shift. > Jun 6 00:40:42 pbx user.info kernel: dahdi: Detected time shift. > Jun 6 01:00:27 pbx user.info kernel: dahdi: Detected time shift. > Jun 6 01:21:29 pbx user.info kernel: dahdi: Detected time shift. > Jun 6 01:41:00 pbx user.info kernel: dahdi: Detected time shift. > Jun 6 02:00:52 pbx user.info kernel: dahdi: Detected time shift. > Jun 6 02:21:02 pbx user.info kernel: dahdi: Detected time shift. > Jun 6 02:41:19 pbx user.info kernel: dahdi: Detected time shift. > Jun 6 03:01:06 pbx user.info kernel: dahdi: Detected time shift. > Jun 6 03:20:49 pbx user.info kernel: dahdi: Detected time shift. > Jun 6 03:40:38 pbx user.info kernel: dahdi: Detected time shift. > Jun 6 04:00:00 pbx user.info kernel: dahdi: Detected time shift. > Jun 6 04:20:24 pbx user.info kernel: dahdi: Detected time shift. > > > Anyone else seeing this? > > This is with 2.3.0... I haven't see that on any of the systems I have with dahdi hardware. Looks like the system time is changing and being sync'ed every 20 minutes. -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com I'm seeing this... but I'm not smart enough to know if it is related to your time messages: Jun 7 10:29:20 pbx daemon.notice ntpd[1188]: kernel time sync status change 4001 Jun 7 10:46:25 pbx daemon.notice ntpd[1188]: kernel time sync status change 0001 Jun 7 11:20:35 pbx daemon.notice ntpd[1188]: kernel time sync status change 4001 Jun 7 11:54:41 pbx daemon.notice ntpd[1188]: kernel time sync status change 0001 Jun 7 13:37:09 pbx daemon.notice ntpd[1188]: kernel time sync status change 4001 Jun 7 14:28:26 pbx daemon.notice ntpd[1188]: kernel time sync status change 0001 Jun 7 15:19:39 pbx daemon.notice ntpd[1188]: kernel time sync status change 4001 Jun 7 16:27:58 pbx daemon.notice ntpd[1188]: kernel time sync status change 0001 Jun 7 17:53:18 pbx daemon.notice ntpd[1188]: kernel time sync status change 4001 perhaps this is perfectly normal... I just don't have the expirence to know better. John R. |
