[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Safest DB modification to repeat.
- To: "Henry B. Hotz" <hotz@jpl.nasa.gov>
- Subject: Re: Safest DB modification to repeat.
- From: Dave Love <d.love@dl.ac.uk>
- Date: Thu, 07 Apr 2005 16:56:09 +0100
- Cc: heimdal-discuss@sics.se
- In-Reply-To: <e490221b6e6f3a8dea72ed227f0c0cff@jpl.nasa.gov> (Henry B. Hotz's message of "Thu, 31 Mar 2005 10:25:12 -0800")
- References: <e490221b6e6f3a8dea72ed227f0c0cff@jpl.nasa.gov>
- Sender: owner-heimdal-discuss@sics.se
- User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3 (gnu/linux)
"Henry B. Hotz" <hotz@jpl.nasa.gov> writes:
> I'm setting up a cron job to generate some iprop traffic on a regular
> basis. First thought was "cpw -r iproptraffic", but that cycles the
> kvno, which would be "bad" at some point.
For what it's worth, frobbing a principal's attributes doesn't change
the kvno. Presumably you'd have to cycle an attribute to generate the
traffic, but that would just mean separate cron entries.
This does sound like a good idea for monitoring problems in the
propagation.