Have the system login scripts fire up rsync and sync the proper file over to
the users home directory. Why make it harder on yourself than it needs to be.
Assuming you have a profile.d directory create a nsupdate-sync.sh & .csh
Good luck.
--
Jason Hellenthal
Voice: 95.30.17.6/616
JJH48-ARI
On 4/10/14, 4:33 PM, Martin G. McCormick wrote:
> One way to allow account-holders on a system to be able
> to do nsupdates is to place the keys in each user's directory but this
> makes changing the keys later a laborious task.
> Is there a proper way to create links to one key that will
>
Maybe this:
3212. [bug] rbtdb.c: failed to remove a node from the deadnodes
list prior to adding a reference to it leading a
possible assertion failure. [RT #23219]
source: ftp://ftp.isc.org/isc/bind9/9.8.6/CHANGES
Note: I stopped l
One way to allow account-holders on a system to be able
to do nsupdates is to place the keys in each user's directory but this
makes changing the keys later a laborious task.
Is there a proper way to create links to one key that will
produce the same effect?
I seem to recall trying
Hello,
We have ~125 servers. About 1330 Central yesterday, the named of 6 of
these crashed in 2 hours time (not at the same time, but within two hours).
Since then, there have been other asserts at the same machines and with several
other machines (total of 11 now). There hves been no c
I had something similar a while back.
view 1
{
include external tables
include common tables
}
view 2
{
include internal tables
include common tables
}
Read that as tables for ONLY-internal or ONLY-external view.
I define each entry exactly once, also pushing stuff off to
the common include me
6 matches
Mail list logo
