Re: [gentoo-user] System won't boot if CMOS clock is slow
On 17 January 2013, at 15:35, Bruce Hill wrote: >> >> You've had lots of other suggestions here, but I think this is handled fine >> if you add ntp to the default runlevel (and assuming the system can connect >> to the net). > > The service would be ntpd (daemon) or ntp-client (client), but not ntp. Yes, obviously. Stroller.
[gentoo-user] Re: System won't boot if CMOS clock is slow
On 2013-01-17, Neil Bothwick wrote: > On Thu, 17 Jan 2013 22:47:17 + (UTC), Grant Edwards wrote: > >> By default, ntpd doesn't seem to want to do >> a step correction to fix large clock errors on startup (there's >> probably an option for that). > > That's for ntp-client to do. In additon to being a server, ntpd _is_ an ntp client. Are you talking about running ntpclient (http://doolittle.icarus.com/ntpclient) instead of ntpd? -- Grant Edwards grant.b.edwardsYow! I invented skydiving at in 1989! gmail.com
Re: [gentoo-user] System won't boot if CMOS clock is slow
On 18 January 2013, at 18:08, Grant Edwards wrote: > On 2013-01-17, Neil Bothwick wrote: >> On Thu, 17 Jan 2013 22:47:17 + (UTC), Grant Edwards wrote: >> >>> By default, ntpd doesn't seem to want to do >>> a step correction to fix large clock errors on startup (there's >>> probably an option for that). >> >> That's for ntp-client to do. > > In additon to being a server, ntpd _is_ an ntp client. > > Are you talking about running ntpclient > (http://doolittle.icarus.com/ntpclient) instead of ntpd? I'm pretty sure he's talking about making larger corrections to fix larger clock errors on startup. I believe I have both ntpd and ntp-client in the default runlevel on at least one system, although I won't swear to it. Stroller.
[gentoo-user] sane and xinetd
Hello,
i try to run the scanner over Network, but something sane not like in
the configuration.
Jan 18 22:15:54 gentoo-mobile xinetd[25116]: START: sane-port pid=25153
from=192.168.2.22
Jan 18 22:15:54 gentoo-mobile saned[25153]: saned from sane-backends 1.0.23
ready
Jan 18 22:15:54 gentoo-mobile saned[25153]: check_host: access by remote host:
192.168.2.22
Jan 18 22:15:54 gentoo-mobile saned[25153]: check_host: gethostbyname for local
hostname failed: Unknown host
Jan 18 22:15:54 gentoo-mobile saned[25153]: init: access granted to
siefke@192.168.2.22
Jan 18 22:15:58 gentoo-mobile saned[25153]: saned exiting
Jan 18 22:15:58 gentoo-mobile xinetd[25116]: EXIT: sane-port status=0 pid=25153
duration=4(sec)
But on the client xsane say "no device" .
gpasswd -a siefke scanner i have make
config on server:
gpasswd -a saned scanner
gentoo-mobile xinetd.d # cat /etc/xinetd.d/saned
service sane-port
{
socket_type = stream
server = /usr/sbin/saned
protocol = tcp
user = saned
group = scanner
wait = no
disable = no
}
The IPs are correct set in /etc/sane.d/saned.conf on the server and
on client in /etc/sane.d/net.conf.
Has anyone a idea whereis the problem?
Thanks for help. Greetings
Silvio
Re: [gentoo-user] System won't boot if CMOS clock is slow
Op vrijdag 18 januari 2013 18:47:31 schreef Stroller: > > On 18 January 2013, at 18:08, Grant Edwards wrote: > > > On 2013-01-17, Neil Bothwick wrote: > >> On Thu, 17 Jan 2013 22:47:17 + (UTC), Grant Edwards wrote: > >> > >>> By default, ntpd doesn't seem to want to do > >>> a step correction to fix large clock errors on startup (there's > >>> probably an option for that). > >> > >> That's for ntp-client to do. > > > > In additon to being a server, ntpd _is_ an ntp client. > > > > Are you talking about running ntpclient > > (http://doolittle.icarus.com/ntpclient) instead of ntpd? > > I'm pretty sure he's talking about making larger corrections to fix larger > clock errors on startup. > > I believe I have both ntpd and ntp-client in the default runlevel on at least > one system, although I won't swear to it. > > Stroller. > > I think you can either run ntp-client to set the time at startup, or ntpd -q. Both are run through ntp-client, but you can set it so that it uses ntpd to set the time. This is done by modifying /etc/conf.d/ntp-client. Mine looks like this, so you can see I'm actually using ntpd -q as ntp-client: # /etc/conf.d/ntp-client # Command to run to set the clock initially # Most people should just leave this line alone ... # however, if you know what you're doing, and you # want to use ntpd to set the clock, change this to 'ntpd' NTPCLIENT_CMD="ntpd" # Options to pass to the above command # This default setting should work fine but you should # change the default 'pool.ntp.org' to something closer # to your machine. See http://www.pool.ntp.org/ or # try running `netselect -s 3 pool.ntp.org`. #NTPCLIENT_OPTS="-s -b -u \ # 0.gentoo.pool.ntp.org 1.gentoo.pool.ntp.org \ # 2.gentoo.pool.ntp.org 3.gentoo.pool.ntp.org" NTPCLIENT_OPTS="-q" Paul
Re: [gentoo-user] Re: System won't boot if CMOS clock is slow
On Fri, 18 Jan 2013 18:08:50 + (UTC), Grant Edwards wrote: > >> By default, ntpd doesn't seem to want to do > >> a step correction to fix large clock errors on startup (there's > >> probably an option for that). > > > > That's for ntp-client to do. > > In additon to being a server, ntpd _is_ an ntp client. But ntpd will not handle large jumps in time, such as when booting with a broken CMOS clock. So you run /etc/init.d/ntp-client as well, which gets the clock right at boot time, then ntpd can keep it right. > Are you talking about running ntpclient > (http://doolittle.icarus.com/ntpclient) instead of ntpd? No. % qlist net-misc/ntp | grep init.d /etc/init.d/ntpd /etc/init.d/ntp-client -- Neil Bothwick Did you hear about the blind prostitute? You have to hand it to her. signature.asc Description: PGP signature
[gentoo-user] Re: System won't boot if CMOS clock is slow
On 2013-01-18, Neil Bothwick wrote: > On Fri, 18 Jan 2013 18:08:50 + (UTC), Grant Edwards wrote: > >> >> By default, ntpd doesn't seem to want to do >> >> a step correction to fix large clock errors on startup (there's >> >> probably an option for that). >> > >> > That's for ntp-client to do. >> >> In additon to being a server, ntpd _is_ an ntp client. > > But ntpd will not handle large jumps in time, such as when booting > with a broken CMOS clock. So you run /etc/init.d/ntp-client as well, > which gets the clock right at boot time, then ntpd can keep it right. Doh! I couldn't find a package named ntp-client or a program named ntp-client and didn't think to look in /etc/init.d... -- Grant Edwards grant.b.edwardsYow! If Robert Di Niro at assassinates Walter Slezak, gmail.comwill Jodie Foster marry Bonzo??
Re: [gentoo-user] Re: System won't boot if CMOS clock is slow
On 19/01/13 06:36, Neil Bothwick wrote: > On Fri, 18 Jan 2013 18:08:50 + (UTC), Grant Edwards wrote: > By default, ntpd doesn't seem to want to do a step correction to fix large clock errors on startup (there's probably an option for that). >>> >>> That's for ntp-client to do. >> >> In additon to being a server, ntpd _is_ an ntp client. > > But ntpd will not handle large jumps in time, such as when booting with a > broken CMOS clock. So you run /etc/init.d/ntp-client as well, which gets > the clock right at boot time, then ntpd can keep it right. > >> Are you talking about running ntpclient >> (http://doolittle.icarus.com/ntpclient) instead of ntpd? > > No. > > % qlist net-misc/ntp | grep init.d > /etc/init.d/ntpd > /etc/init.d/ntp-client > > It can handle large jumps, check out this in the "man ntp.conf": tinker panic 0 or the -g option to ntpd (again, its in a man page.) Basicly, you just need to read and configure it ... I have it working even on a raspberry pi which has HW clock :) Even the slew rate, or slew/jump can be set. BillK
