Squid

davidh_at_niitsa.com

To: <fedora-list@redhat.com>
Date: Thu, 23 Sep 2004 11:52:51 +0200


--
		Matthew Saltzman
Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs
------------------------------
Message: 2
Date: Wed, 22 Sep 2004 22:06:22 -0400
From: Jim Cornette <fc-cornette@sbcglobal.net>
Subject: passing resolution options to anaconda?
To: For users of Fedora Core releases <fedora-list@redhat.com>
Message-ID: <41522F9E.5070007@sbcglobal.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
I found out that setting the resolution of the display to 800 x 600
worked for someone to overcome an installer problem. What options can be
used to pass these options to the installer?
I did not have to pass options to the installer earlier regarding
setting resolution specs.
Links to documentation or a simple how to apreciated.
Jim
------------------------------
Message: 3
Date: Thu, 23 Sep 2004 10:08:10 +0800
From: Ow Mun Heng <Ow.Mun.Heng@wdc.com>
Subject: Re: Dell Latitude D600 touchpad problem
To: Fedora-List <fedora-list@redhat.com>
Message-ID: <1095905290.28469.7.camel@neuromancer.home.net>
Content-Type: text/plain
On Wed, 2003-12-31 at 06:41, mikko nuotio wrote:
> I have Dell Latitude D600, 512MB/1.4 GHz/ATI Radeon 9000/Alps GlidePoint
> (might be only sold in EU).
I hve the same laptop on FC2
> The problem is I _really_ dislike Alps
> GlidePoint (dual, pad and stick) tapping feature.
I kinda like it actually. The *** that is.
> I want to disable tapping from both stick and pad (or disable the pad)
Not too sure how to do that. Could be possible from the XFree config.
Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "IMPS/2"  <----??
        Option      "Device" "/dev/input/mice"
        Option      "ZAxisMapping" "4 5"
        Option      "Emulate3Buttons" "yes"
EndSection
> tpconfig - I disable gpm, boot to runlevel 3 run manually "tpconfig
> --tapmode=0" it says ALPS tapping OFF, but when I start X tapping is
> still there, even using any existing mouse driver (PS/2, Alps).
>
> Does "tpconfig --tapmode=0" only affect on stick ?
I don't use synaptic nor ALPS at all. What I have is whatever is already in
the kernel.
I don't get the tapping for the ***. Only the Pad.
--
Ow Mun Heng
Fedora GNU/Linux Core 2 on D600 1.4Ghz CPU kernel
2.6.7-2.jul1-interactive
Neuromancer 10:04:55 up 2 days, 11:01, 5 users, load average: 0.20,
0.65, 0.98
------------------------------
Message: 4
Date: Wed, 22 Sep 2004 21:12:15 -0500
From: Jeff Vian <jvian10@charter.net>
Subject: Re: Detecting inactive accounts
To: For users of Fedora Core releases <fedora-list@redhat.com>
Message-ID: <1095905535.3064.108.camel@goliath.lab.net>
Content-Type: text/plain
On Wed, 2004-09-22 at 17:49, Paul Stepowski wrote:
> Hi,
>
> I'm trying to write a script that will detect if an account
> is due to be (or has been) disabled so users get sent an
> email notification telling them to change there password or
> login to make sure the account is not disabled for being
> inactive for too long.
>
> The password expiry part is easy enough to do but detecting
> the time of the last login reliably is giving me problems.
>
> NOTE: I don't want to look at last logs to get the last
> login time because they are rotated off the box frequently.
>
> # chage -l <account>
> Minimum:        0
> Maximum:        60
> Warning:        14
> Inactive:       60
> Last Change:            Sep 10, 2004
> Password Expires:       Nov 09, 2004
> Password Inactive:      Jan 08, 2005
> Account Expires:        Never
>
> So if this account is inactive for 60 days, it gets locked.
> I need to be able to detect this reliably.  According to
> the man page, this information should be stored in the
> shadow file (see below).
>
> # man 5 shadow
> ---snip---
> shadow contains the encrypted password information for user's accounts and
optional the password aging information.
>
> Included is
> Login name
> Encrypted password
> Days since Jan 1, 1970 that password was last changed
> Days before password may be changed
> Days after which password must be changed
> Days before password is to expire that user is warned
> Days after password expires that account is disabled
> Days since Jan 1, 1970 that account is disabled
> A reserved field
> ---snip---
>
> # cat /etc/shadow | grep <account>
> proxy:<crypted_pwd>:12671:0:60:14:60::
>
write your script (perl does this nicely) to parse the line in the
shadow file.
In this case, 12671 + 60 is the password expiration, and 12671 + 60 -14
would be the date when notice should be sent out.
The account is automatically disabled at 12671 +60 +60 unless the
password gets reset.
You do not really care when they last logged in, you are only concerned
about password expiration and account getting disabled.
The time they last logged in has NO effect on when the password expires
or the account gets disabled, only the password change date as shown in
the shadow file affects that.
> The last two values aren't set in the shadow file for
> this account.  Is there any way to get this information?
> Is there some reason that these fields are not defined
> in the /etc/shadow file?
>
> Thanks,
>
> Paul
>
------------------------------
Message: 5
Date: Wed, 22 Sep 2004 19:14:14 -0700
From: Timothy Payne <tim@tmpco.com>
Subject: Re: Instant messenger on Linux
To: For users of Fedora Core releases <fedora-list@redhat.com>
Message-ID: <1095905654.4132.55.camel@localhost.localdomain>
Content-Type: text/plain
Michael, your right it is in FC2 and on my machine.  What a bone head it
was right there.  Thanks Tim...
On Wed, 2004-09-22 at 12:45, Michael Schwendt wrote:
> On Wed, 22 Sep 2004 14:52:00 -0400, Alexandre Moore wrote:
>
> > On Tue, 21 Sep 2004 20:51:29 -0700, Timothy Payne <tim@tmpco.com> wrote:
> > > Use gaim!  :o)
> > > > http://gaim.sourceforge.net/
> > >
> > > They suggest using one of the mirrors for FC2, but I couldn't find in
in
> > > any of the West's mirrors.  Any idea why, yum couldn't find it ether.
> > >
> > > Tim..
> > >
> > http://dag.wieers.com/packages/gaim/
>
> Gaim is included with Fedora Core and has been updated several times
> for FC2.
>
> Alternatively, Psi is nice, too.
> Search for 'psi' at http://www.fedoratracker.org
>
> --
> Fedora Core release 2.91 (FC3 Test 2) - Linux 2.6.8-1.541
> loadavg: 1.34 1.28 1.17
>
------------------------------
Message: 6
Date: Wed, 22 Sep 2004 18:12:17 -0700
From: Nifty Hat Mitch <mitch48@sbcglobal.net>
Subject: Re: Time difference between Win98 and Fedora
To: For users of Fedora Core releases <fedora-list@redhat.com>
Message-ID: <20040923011216.GE1066@xtl1.xtl.tenegg.com>
Content-Type: text/plain; charset=us-ascii
On Wed, Sep 22, 2004 at 07:08:32PM -0500, Jeff Vian wrote:
> From: Jeff Vian <jvian10@charter.net>
> To: For users of Fedora Core releases <fedora-list@redhat.com>
> Date: Wed, 22 Sep 2004 19:08:32 -0500
> Subject: Re: Time difference between Win98 and Fedora
> Reply-To: For users of Fedora Core releases <fedora-list@redhat.com>
>
> On Wed, 2004-09-22 at 07:43, James Wilkinson wrote:
> > Rob "Hairysocks" wrote:
> > > I have a dual-boot PC and notice that I can't get the time
> > > correct on both Win98 and Fedora. When the Win98 time is correct
> > > then the time on Fedora is one hour ahead.
....
> Please provide details on how this is accomplished to keep both OSes
> happy with the time.
>
> I have been unable to find the details for what you say, and I am one of
> those affected by my occasional boot to Win98 and the time change.
The key here is that Linux keeps time as UTS time
and with the ctime() library converts to a local
view of time for  each user (a global view).
When the system shuts down by default it writes UTS time to the RTC
and on boots it looks at a battery driven local hardware Real Time
Clock (RTC) to discover what time it is.
Windows keeps local time and writes local time to the RTC.
Since the Unix/Linux default does not match the WindowZ view
Linux has the configuration option of keeping local time in the RTC.
On the Time Zone tab of:
   /usr/bin/system-config-date
You will see a button that indicates that System Clock uses UTC.
If you check it you have the normal Unix/Linux use of the RTC.
Uncheck it and local time will be saved.
The configuration is saved in /etc/sysconfig/clock
and mine looks like:
     ZONE="America/Los_Angeles"
     UTC=false
     ARC=false
What does your /etc/sysconfig/clock look like?
--
	T o m  M i t c h e l l
	Me, I would "Rather" Not.
------------------------------
Message: 7
Date: Thu, 23 Sep 2004 12:21:51 +1000
From: Paul Stepowski <p.stepowski@qut.edu.au>
Subject: Re: Detecting inactive accounts
To: For users of Fedora Core releases <fedora-list@redhat.com>
Message-ID: <4152333F.6030201@qut.edu.au>
Content-Type: text/plain; charset=us-ascii; format=flowed
Jeff Vian wrote:
> On Wed, 2004-09-22 at 17:49, Paul Stepowski wrote:
>
>>Hi,
>>
>>I'm trying to write a script that will detect if an account
>>is due to be (or has been) disabled so users get sent an
>>email notification telling them to change there password or
>>login to make sure the account is not disabled for being
>>inactive for too long.
>>
>>The password expiry part is easy enough to do but detecting
>>the time of the last login reliably is giving me problems.
>>
>>NOTE: I don't want to look at last logs to get the last
>>login time because they are rotated off the box frequently.
>>
>># chage -l <account>
>>Minimum:        0
>>Maximum:        60
>>Warning:        14
>>Inactive:       60
>>Last Change:            Sep 10, 2004
>>Password Expires:       Nov 09, 2004
>>Password Inactive:      Jan 08, 2005
>>Account Expires:        Never
>>
>>So if this account is inactive for 60 days, it gets locked.
>>I need to be able to detect this reliably.  According to
>>the man page, this information should be stored in the
>>shadow file (see below).
>>
>># man 5 shadow
>>---snip---
>>shadow contains the encrypted password information for user's accounts and
optional the password aging information.
>>
>>Included is
>>Login name
>>Encrypted password
>>Days since Jan 1, 1970 that password was last changed
>>Days before password may be changed
>>Days after which password must be changed
>>Days before password is to expire that user is warned
>>Days after password expires that account is disabled
>>Days since Jan 1, 1970 that account is disabled
>>A reserved field
>>---snip---
>>
>># cat /etc/shadow | grep <account>
>>proxy:<crypted_pwd>:12671:0:60:14:60::
>>
>
>
> write your script (perl does this nicely) to parse the line in the
> shadow file.
>
> In this case, 12671 + 60 is the password expiration, and 12671 + 60 -14
> would be the date when notice should be sent out.
> The account is automatically disabled at 12671 +60 +60 unless the
> password gets reset.
>
I've already got this bit down.  No problem.
> You do not really care when they last logged in, you are only concerned
> about password expiration and account getting disabled.
>
> The time they last logged in has NO effect on when the password expires
> or the account gets disabled, only the password change date as shown in
> the shadow file affects that.
I don't follow you here.  I understand that the chage "Inactive:" field
is meant to disable accounts that have been inactive (i.e. no logins)
for x days.  Can you please clarify?
Thanks,
Paul
>
>
>
>>The last two values aren't set in the shadow file for
>>this account.  Is there any way to get this information?
>>Is there some reason that these fields are not defined
>>in the /etc/shadow file?
>>
>>Thanks,
>>
>>Paul
>>
>
>
>
------------------------------
Message: 8
Date: Wed, 22 Sep 2004 19:31:00 -0700
From: Timothy Payne <tim@tmpco.com>
Subject: Re: FC1 to FC2 on dual-boot: problems?
To: For users of Fedora Core releases <fedora-list@redhat.com>
Message-ID: <1095906659.4132.69.camel@localhost.localdomain>
Content-Type: text/plain
I started a reply I hope it doesn't post twice.  I have win98 as a
second drive and someone on the list told me there is a bug in FC2 that
reports the drive geometry to windows wrong.  I never looked up the bug
but you might see if it applies to win2k.  I can't defrag the drive with
norton or the win util. it just gags on it so I am assuming they were
correct.
Tim...
On Wed, 2004-09-22 at 13:39, Bob Hartung wrote:
> Hi all,
>    I have a dual boot T40 with Win2K and FC1 happily living together.  I
> would like to upgrade to FC2.  Does anyone know if I will have the dual
> boot problems that have been discussed here with a FC2 fresh install?
>
> TIA
>
> Bob
>
------------------------------
Message: 9
Date: Wed, 22 Sep 2004 23:36:11 -0300 (ART)
From: Clodoaldo Pinto Neto <clodoaldo_pinto@yahoo.com.br>
Subject: Pen drive install - Loading usb-storage driver...
To: fedora-list@redhat.com
Message-ID: <20040923023611.36098.qmail@web40908.mail.yahoo.com>
Content-Type: text/plain; charset=iso-8859-1
Hello,
When doing a FC2 pen drive install it gets stuck with the message:
-----| Loading SCSI driver |-----
|                               |
| Loading usb-storage driver... |
|                               |
---------------------------------
The pen drive I'm using is SanDisk 256MB Cruzer Mini:
http://www.sandisk.com/retail/cruzer-mini.asp
Regards,
Clodoaldo
_______________________________________________________
Yahoo! Messenger 6.0 - jogos, emoticons sonoros e muita diversco. Instale
agora!
http://br.download.yahoo.com/messenger/
------------------------------
Message: 10
Date: Wed, 22 Sep 2004 22:37:16 -0400
From: "Scot L. Harris" <webid@cfl.rr.com>
Subject: Re: Time difference between Win98 and Fedora
To: For users of Fedora Core releases <fedora-list@redhat.com>
Message-ID: <1095907036.29058.6.camel@lathe.slh.lan>
Content-Type: text/plain
On Wed, 2004-09-22 at 22:03, Matthew Saltzman wrote:
> On Wed, 22 Sep 2004, Jeff Vian wrote:
>
> > On Wed, 2004-09-22 at 07:43, James Wilkinson wrote:
> > > Rob "Hairysocks" wrote:
> > > > I have a dual-boot PC and notice that I can't get the time
> > > > correct on both Win98 and Fedora. When the Win98 time is correct
> > > > then the time on Fedora is one hour ahead.
A couple of years ago a laptop running windows 2000 was having problems
keeping the correct time.  Not sure why but it seemed that the time
would change by one hour sometimes but not others.  I figured it had to
do with the day light savings time settings.
The resolved this problem by running a program called automacron.  It
was an NTP like utility written for windows.  This would reset the clock
correctly when the system was booted.
As others have said trying to resolve this any other way is futile.
Since then I have reloaded the laptop with FC2 and have not run windows
on it since.
--
Scot L. Harris
webid@cfl.rr.com
The only function of economic forecasting is to make astrology look
respectable.
		-- John Kenneth Galbraith
------------------------------
Message: 11
Date: Wed, 22 Sep 2004 22:50:31 -0400
From: Gene Heskett <gene.heskett@verizon.net>
Subject: fubared modprobe.conf
To: For users of Fedora Core releases <fedora-list@redhat.com>
Message-ID: <200409222250.31835.gene.heskett@verizon.net>
Content-Type: text/plain;  charset="us-ascii"
Greetings;
I just made the usb driver for the prolific pl2303 serial-usb
interface a module, and I added the line:
alias char-major-188 pl2303
and rebooted.  But I still had to modprobe it in by hand after the
reboot.
Whats the usual syntax for that in modprobe.conf?
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
------------------------------
Message: 12
Date: Wed, 22 Sep 2004 21:00:27 -0600
From: "Rodolfo J. Paiz" <rpaiz@simpaticus.com>
Subject: Re: Time difference between Win98 and Fedora
To: For users of Fedora Core releases <fedora-list@redhat.com>
Message-ID: <1095908426.2590.3.camel@rodolfo.paiz.org>
Content-Type: text/plain
On Wed, 2004-09-22 at 11:36, Matthew Saltzman wrote:
> If you are running Linux with the hardware clock set
> to LOCAL at the time change, then Linux will make the change successfully.
> If you then reboot to Windows, Linux updates the hardware clock on
> shutdown.  When you next boot into Windows, it will realize that it's the
> first boot since the change and adjust software and hardware clocks again.
> Now you are an hour off in Windows, and when you boot Linux, it assumes
> the hardware clock has the correct local time, so you're an hour off there
> too.
>
You are, of course, correct. I should have said that you can get things
to be correct in both OS's, and reboot to either at will, by setting the
time to local on both sides. This will work 363 days per year... and
twice per year, you'll get thrown off.
I do not know of a "perfect" way to keep both clocks correct, showing
local time, and not upsetting each other. I just consider two time
corrections per year the "necessary evil" of dual-booting. :-(
Cheers,
--
Rodolfo J. Paiz <rpaiz@simpaticus.com>
Simpaticus.com
------------------------------
Message: 13
Date: Wed, 22 Sep 2004 22:06:15 -0500
From: "rhl" <rhl@farorbit.com>
Subject: RE: Time difference between Win98 and Fedora
To: "'For users of Fedora Core releases'" <fedora-list@redhat.com>
Message-ID: <200409230312.i8N3C8UQ005551@isis.farorbit.com>
Content-Type: text/plain;	charset="us-ascii"
You could just use atomic clock in 98 and setup ntp in linux... then no
hands!
-----Original Message-----
From: fedora-list-bounces@redhat.com [mailto:fedora-list-bounces@redhat.com]
On Behalf Of Rodolfo J. Paiz
Sent: Wednesday, September 22, 2004 10:00 PM
To: For users of Fedora Core releases
Subject: Re: Time difference between Win98 and Fedora
On Wed, 2004-09-22 at 11:36, Matthew Saltzman wrote:
> If you are running Linux with the hardware clock set
> to LOCAL at the time change, then Linux will make the change successfully.
> If you then reboot to Windows, Linux updates the hardware clock on
> shutdown.  When you next boot into Windows, it will realize that it's the
> first boot since the change and adjust software and hardware clocks again.
> Now you are an hour off in Windows, and when you boot Linux, it assumes
> the hardware clock has the correct local time, so you're an hour off there
> too.
>
You are, of course, correct. I should have said that you can get things
to be correct in both OS's, and reboot to either at will, by setting the
time to local on both sides. This will work 363 days per year... and
twice per year, you'll get thrown off.
I do not know of a "perfect" way to keep both clocks correct, showing
local time, and not upsetting each other. I just consider two time
corrections per year the "necessary evil" of dual-booting. :-(
Cheers,
--
Rodolfo J. Paiz <rpaiz@simpaticus.com>
Simpaticus.com
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
------------------------------
Message: 14
Date: Thu, 23 Sep 2004 00:23:30 -0300 (ART)
From: Clodoaldo Pinto Neto <clodoaldo_pinto@yahoo.com.br>
Subject: yum update - Package epiphany needs mozilla = 37:1.7.2
To: fedora-list@redhat.com
Message-ID: <20040923032330.7551.qmail@web40909.mail.yahoo.com>
Content-Type: text/plain; charset=iso-8859-1
FC2:
# yum update
Gathering header information file(s) from server(s)
Server: Fedora Core 2 - i386 - Base
Server: Fedora Core 2 - i386 - Released Updates
Finding updated packages
Downloading needed headers
mozilla-dom-inspector-37- 100% |=========================| 3.8 kB
00:00
epiphany-0-1.2.7-0.2.1.i3 100% |=========================| 8.1 kB
00:00
mozilla-chat-37-1.7.3-0.2 100% |=========================| 3.3 kB
00:00
mozilla-nspr-37-1.7.3-0.2 100% |=========================| 3.4 kB
00:00
mozilla-nss-37-1.7.3-0.2. 100% |=========================| 3.7 kB
00:00
mozilla-js-debugger-37-1. 100% |=========================| 3.3 kB
00:00
mozilla-mail-37-1.7.3-0.2 100% |=========================| 5.6 kB
00:00
mozilla-37-1.7.3-0.2.0.i3 100% |=========================|  21 kB
00:00
mozilla-devel-37-1.7.3-0. 100% |=========================| 100 kB
00:01
devhelp-devel-0-0.9.1-0.2 100% |=========================| 2.3 kB
00:00
mozilla-nspr-devel-37-1.7 100% |=========================| 6.4 kB
00:00
devhelp-0-0.9.1-0.2.1.i38 100% |=========================| 5.0 kB
00:00
mozilla-nss-devel-37-1.7. 100% |=========================| 9.4 kB
00:00
Resolving dependencies
....Unable to satisfy dependencies
Package epiphany needs mozilla = 37:1.7.2, this is not available.
_______________________________________________________
Yahoo! Messenger 6.0 - jogos, emoticons sonoros e muita diversco. Instale
agora!
http://br.download.yahoo.com/messenger/
------------------------------
Message: 15
Date: Thu, 23 Sep 2004 13:29:51 +1000
From: Paul Stepowski <p.stepowski@qut.edu.au>
Subject: Re: Detecting inactive accounts
To: For users of Fedora Core releases <fedora-list@redhat.com>
Message-ID: <4152432F.2050209@qut.edu.au>
Content-Type: text/plain; charset=us-ascii; format=flowed
Hmmm...I RTFM and answered my own question.  Thanks. :-)
Paul Stepowski wrote:
>
>
> Jeff Vian wrote:
>
>> On Wed, 2004-09-22 at 17:49, Paul Stepowski wrote:
>>
>>> Hi,
>>>
>>> I'm trying to write a script that will detect if an account
>>> is due to be (or has been) disabled so users get sent an
>>> email notification telling them to change there password or
>>> login to make sure the account is not disabled for being
>>> inactive for too long.
>>>
>>> The password expiry part is easy enough to do but detecting
>>> the time of the last login reliably is giving me problems.
>>>
>>> NOTE: I don't want to look at last logs to get the last
>>> login time because they are rotated off the box frequently.
>>>
>>> # chage -l <account>
>>> Minimum:        0
>>> Maximum:        60
>>> Warning:        14
>>> Inactive:       60
>>> Last Change:            Sep 10, 2004
>>> Password Expires:       Nov 09, 2004
>>> Password Inactive:      Jan 08, 2005
>>> Account Expires:        Never
>>>
>>> So if this account is inactive for 60 days, it gets locked.
>>> I need to be able to detect this reliably.  According to
>>> the man page, this information should be stored in the
>>> shadow file (see below).
>>>
>>> # man 5 shadow
>>> ---snip---
>>> shadow contains the encrypted password information for user's
>>> accounts and optional the password aging information.
>>>
>>> Included is
>>> Login name
>>> Encrypted password
>>> Days since Jan 1, 1970 that password was last changed
>>> Days before password may be changed
>>> Days after which password must be changed
>>> Days before password is to expire that user is warned
>>> Days after password expires that account is disabled
>>> Days since Jan 1, 1970 that account is disabled
>>> A reserved field
>>> ---snip---
>>>
>>> # cat /etc/shadow | grep <account>
>>> proxy:<crypted_pwd>:12671:0:60:14:60::
>>>
>>
>>
>> write your script (perl does this nicely) to parse the line in the
>> shadow file.
>>
>> In this case, 12671 + 60 is the password expiration, and 12671 + 60 -14
>> would be the date when notice should be sent out.
>> The account is automatically disabled at 12671 +60 +60 unless the
>> password gets reset.
>>
>
> I've already got this bit down.  No problem.
>
>> You do not really care when they last logged in, you are only concerned
>> about password expiration and account getting disabled.
>>
>> The time they last logged in has NO effect on when the password expires
>> or the account gets disabled, only the password change date as shown in
>> the shadow file affects that.
>
>
> I don't follow you here.  I understand that the chage "Inactive:" field
> is meant to disable accounts that have been inactive (i.e. no logins)
> for x days.  Can you please clarify?
>
> Thanks,
>
> Paul
>
>>
>>
>>
>>> The last two values aren't set in the shadow file for
>>> this account.  Is there any way to get this information?
>>> Is there some reason that these fields are not defined
>>> in the /etc/shadow file?
>>>
>>> Thanks,
>>>
>>> Paul
>>>
>>
>>
>>
>
>
------------------------------
Message: 16
Date: Wed, 22 Sep 2004 20:57:47 -0700
From: Kenneth Porter <shiva@sewingwitch.com>
Subject: Re: NTP syncing
To: For users of Fedora Core releases <fedora-list@redhat.com>
Message-ID: <114B8357656A351CC8288CA4@[10.0.0.4]>
Content-Type: text/plain; charset=us-ascii; format=flowed
--On Wednesday, September 22, 2004 11:04 AM -0600 "Rodolfo J. Paiz"
<rpaiz@simpaticus.com> wrote:
> By the way, all my DHCP servers provide a pointer to my NTP servers. How
> do I get clients (Fedora Linux and Windows) to use this pointer? Anyone
> have any idea? Can't find docs to tell me.
I don't think Windows will use it. What we need is a Win32 client that will
issue DHCPINFORM to get the setting and invoke "net time /setsntp" to stash
it away, as well as starting the Windows Time service to use it.
For Linux, look at the ISC DHCP client. It has a script that gets all
options and rewrites various config files. I believe the RH-provided one
clobbers your ntp.conf if that setting is provided and an
interface-specific setting doesn't disable the overwrite. Just checked...
the package is dhclient (a subpackage of the ISC dhcp SRPM) and the script
is /bin/dhclient-script. Browse that to see how it works.
------------------------------
--
fedora-list mailing list
fedora-list@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-list
End of fedora-list Digest, Vol 7, Issue 245
*******************************************
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list