@donna-hooe
Forum Replies Created
-
AuthorReplies
-
We do the FTP move, cleanup and archive using Linux scripts set up on crontab, then we set up Cloverleaf to pole the local directory we put those files in.
I clean both up the files in the lock and revisions directories once a month.
Sometimes I save only the last files. Depends on what we have going on.
February 28, 2013 at 9:04 pm in reply to: cloverleaf 6.0 – concern about site name length limit #77962Russ,
What are the character limits for the thread names in version 6.0? I haven’t been able to get the documentation yet for 6.0.
I’ld like to see the documentation for 6.0 posted too
Both of our Linux boxes are also virtual.
Our organization has 2 Cloverleaf Linux boxes, one is local and the other is remote hosted. I have seen the problem you describe on my remote hosted box but everything works fine on the local box. We are running 5.8.4 on the remote box and 5.8.3 on the local box but we had the issue on the remote box with 5.7.3 as well.
In our case we suspect that all the firewall security is the problem, since we don’t see the problem with our local box. I have a call in about this but no one has been able to come up with an explaination or a fix. If I hear back from someone about this and we find a solution I will update you.
Our server is Linux. The issue appears to have been a bad copy of patch 3. I finally got a second copy and installed it on the server and now it works. Check the version of the software you are running on the pc’s versus the server. We had this issue a while back and there was one pc in our helpdesk that had not been updated to 5.7Rev2. This was causing it to hang. We check all pc’s we use to run the GUI’s on and once we got them all on the same version and Rev patch we were good to go.
David, Thanks for your help.
James Cobane wrote:Ryan,
One thing I’m surprised at though is that 99% of your translation is done via Tcl.
Unfortunately that is not an option. I take it from what you are saying we might be better going CL5.6 then RH5.1 then CL5.7. Is that correct? We have always done our upgrades in the past so that our users did not even notice it ever happened, not even a blip. We thoroughly test before moving to production but both our test and production systems run on the same box.
No way to test our test system with the new OS and version without effecting production. Now you see my dilemma. We also have a very strick change management process here as well. Testing can’t be skipped.
Jerry,
We currently run both test and procuction on the same box. I would have an issue testing if we just upgraded like that. We also cut over one site at a time (we have 4 in production) so that our users never even know we are upgrading.
I am thinking we will have to take the slower route going with Cloverleaf 5.6 then the Linux upgrade and finally the Cloverleaf 5.7.
Max We are on cloverleaf 5.5 with RH Linux 4 and are looking to go to Cloverleaf 5.7 too.
I take it by your response that Cloverleaf 5.5 will run on RH Linux 5 or do we have to go to Cloverleaf 5.6, then do the Linux upgrade then move to 5.7?
Thanks in advance.
September 22, 2008 at 2:04 pm in reply to: Cloverleaf 5.5 on Red Hat Enterprise Linux AS release 4 #65544Finally figured it out. Thanks,
-
AuthorReplies
