I am working on my Sun work station with Solaris 9.
In a project of mine, I have a CRL server, which writes a disk file
called thecrl.crl every minute. This file has the next update time
For the same project, I also have a CRL client, which simply reads the
thecrl.crl file across the network, checks its next update time,
sleeps for that amount of time, and then reads that file again.
I am having problems with this.
It seems the CRL server runs well. It does not get killed by the
But the CRL client gets killed by the operating system a few, usually
3, minutes after it is launched. I could see by ps -ef | grep 'CRL'
I launched the client using nohup, but I can't find any info in the
nohup.out file, which is empty. My applicaton is written in Java, I
can find no exception info in the nohup.out file.
I am wondering if there is a reader-writer problem in this case, since
both the client and server will be accessing the thecrl.crl file.
In order to avoid the reader-writer problem, I let my client sleep
until 20 seconds after the server has written the thecrl.crl file.
But this does not seem to help.
What do you guys think?
If you guys confirm that there is a reader-writer problem involved
here, I may have to use a semaphore to take care of their fight,