History log of /src/usr.sbin/rpc.statd/stat_proc.c |
Revision | | Date | Author | Comments |
1.9 |
| 23-Jan-2018 |
sevan | ansify - drop the K&R style prototypes & implementations.
|
1.8 |
| 18-Apr-2009 |
lukem | Fix -Wshadow and -Wcast-qual issues
|
1.7 |
| 03-Nov-2005 |
bouyer | branches: 1.7.28; When forking, we keep a reference to the status db file, and if the memory copy of the file is dirty, is will be synced when the child exists. But the parent may have done changes to the database in the meantime, resulting in a db corruption. Fix this by calling sync_file() just before the fork. The child will still have a reference to the db, but won't try to write it on exit.
|
1.6 |
| 09-Jun-2000 |
fvdl | branches: 1.6.4; 1.6.8; 1.6.10; Convert to tirpc interface, and to be af-independent.
|
1.5 |
| 06-Jun-2000 |
bouyer | Solaris hosts with multiple names (e.g. short & fqdn) sends notification with both names. So log the "Unsolicited notification" with LOG_DEBUG instead of LOG_ERR. Don't return failure if we received a notification for which the host is unknown, or we don't have outstanding requests. The remote host will retry forever otherwise.
|
1.4 |
| 21-Oct-1997 |
christos | branches: 1.4.8; Use a db(3) hash database instead of shared memory. Don't fork() to service requests in the database when restarting.
|
1.3 |
| 17-Oct-1997 |
lukem | WARNSify; generate ansi c code with rpcgen, cleanup manpage, add rcsids
|
1.2 |
| 17-Oct-1997 |
lukem | WARNSify; generate ansi c code with rpcgen, cleanup manpage, add rcsids
|
1.1 |
| 10-Mar-1997 |
scottr | Status monitor daemon by A.R. Gordon, ported from FreeBSD. While the functionality was not significantly altered, the code was KNFed and the build process cleaned up considerably.
|
1.4.8.1 |
| 22-Jun-2000 |
minoura | Sync w/ netbsd-1-5-base.
|
1.6.10.1 |
| 05-Nov-2005 |
tron | Pull up following revision(s) (requested by bouyer in ticket #932): usr.sbin/rpc.statd/stat_proc.c: revision 1.7 When forking, we keep a reference to the status db file, and if the memory copy of the file is dirty, is will be synced when the child exists. But the parent may have done changes to the database in the meantime, resulting in a db corruption. Fix this by calling sync_file() just before the fork. The child will still have a reference to the db, but won't try to write it on exit.
|
1.6.8.1 |
| 06-Nov-2005 |
riz | Pull up following revision(s) (requested by bouyer in ticket #5967): usr.sbin/rpc.statd/stat_proc.c: revision 1.7 When forking, we keep a reference to the status db file, and if the memory copy of the file is dirty, is will be synced when the child exists. But the parent may have done changes to the database in the meantime, resulting in a db corruption. Fix this by calling sync_file() just before the fork. The child will still have a reference to the db, but won't try to write it on exit.
|
1.6.4.1 |
| 06-Nov-2005 |
riz | Pull up following revision(s) (requested by bouyer in ticket #5930): usr.sbin/rpc.statd/stat_proc.c: revision 1.7 When forking, we keep a reference to the status db file, and if the memory copy of the file is dirty, is will be synced when the child exists. But the parent may have done changes to the database in the meantime, resulting in a db corruption. Fix this by calling sync_file() just before the fork. The child will still have a reference to the db, but won't try to write it on exit.
|
1.7.28.1 |
| 13-May-2009 |
jym | Sync with HEAD.
Third (and last) commit. See http://mail-index.netbsd.org/source-changes/2009/05/13/msg221222.html
|