Ken Raeburn <[EMAIL PROTECTED]> writes: > Monica Lau <[EMAIL PROTECTED]> writes: >> I have a master kdc and a slave kdc. In the master kdc, I run a >> script that executes kprop to propagate the database to the slave >> every 2 seconds (for testing purposes). On the slave kdc, I run the >> "df" command periodically. I noticed that the disk space percentage >> usage climbs up slowly. Eventually, it goes up to 100%, and my >> slave machine crashes. I don't understand how/why kprop could cause >> the disk space in the slave machine to go up because the master >> database is always the same size. If I stop the propagation, the >> disk space in the slave doesn't go down, until I reboot the machine. > > It sounds like unreferenced files being kept around for some reason. > Try looking for old processes hanging around for some reason (is > kpropd not exiting properly?), or get the "lsof" tool and use it to > see what processes might have extra files kept open.
Someone here pointed out the "every 2 seconds" part that I overlooked. Trying it out like that, I think I've reproduced the problem. I'll investigate further. > Roughly, it goes like this on the slave side: > - kpropd gets a connection > - data is saved (default: $localstatedir/krb5kdc/slave_datatrans) Actually, slave_datatrans is on the master side. It's from_master on the slave. Ken ________________________________________________ Kerberos mailing list [EMAIL PROTECTED] https://mailman.mit.edu/mailman/listinfo/kerberos
