nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Changes in CGI Files

seshusatya

hi ,

I have doubt regarding CGI files.

If I make changes in CGI files which are user defined files,
in order to reflect my changes Do I need to restart my TS server?

or the changes will take effect after saving CGI file.

thanks in advance,

regards,
seshu

Find more posts tagged with

Comments

kaalraa

No... when ever you put on the CGI file with in the iw-bin or the directory where your apache would look into... the CGI file would work.

No need to restart the TS server.

hi ,
I have doubt regarding CGI files.
If I make changes in CGI files which are user defined files,
in order to reflect my changes Do I need to restart my TS server?
or the changes will take effect after saving CGI file.
thanks in advance,
regards,
seshu

Adam Stoller

You only need to restart the invokation of the CGI script.
I.e. if you're in a workflow cgitask and you have the script running - and you decide to change something in the CGI script itself - you need to quit the cgitask (close its window) and then go back to the workflow task interface and re-start the cgitask in order to see the changes you made.

The only reason you might need to restart something more central would be if you were using something like speedycgi which *might* cache the script code (don't know - haven't used it myself. Don't think this would be the case but it *might* be)

If you don't know if you're using speedycgi - chances are very good that you aren't - so you don't need to worry about it.

kaalraa

if you're in a workflow cgitask and you have the script running - and you decide to change something in the CGI script itself - you need to quit the cgitask (close its window) and then go back to the workflow task interface and re-start the cgitask in order to see the changes you made.

In this case, the cgi file must be submitted before starting the task again.

Adam Stoller

In this case, the cgi file must be submitted before starting the task again.

The cgi file only needs to be submitted if it is being version controlled (a good thing to do, but not a requirement). Regardless, it would have to be put in place over the old copy of the cgi file. Some systems will not let you overwrite a script that is "being used", other systems will let you appear to overwrite it but maintain a cached copy of the script in memory such that existing runs of the script will continue to work but new invocations will use the new script.

kaalraa

Thanks Adam.... for making me understand. I was also trying to say the same thing... i just meant that if it is to be incoked from a cgitask then it is a must to submit else can be preview by just uploading as well.

BUT in both the cases, it needs to be revoked. I hope i understand all as what you were trying to make me understood.

The cgi file only needs to be submitted if it is being version controlled (a good thing to do, but not a requirement). Regardless, it would have to be put in place over the old copy of the cgi file. Some systems will not let you overwrite a script that is "being used", other systems will let you appear to overwrite it but maintain a cached copy of the script in memory such that existing runs of the script will continue to work but new invocations will use the new script.

ravio

Thanks ... i just meant that if it is to be incoked from a cgitask then it is a must to submit else can be preview by just uploading as well.

BUT in both the cases, it needs to be revoked. I hope i understand all as what you were trying to make me understood.

If there is a file which you are versioning within TeamSite

And this file is the CGI in question, then whenever you *Submit * your changed file, it will create a new version for that file.

If you are not versioning the file, then submitting is not a relevant thing for it to be picked up by the system.
This is basically what Adam has said...and of course some other finer points that are relevant to the new CGI to be picked up by the system

kaalraa

Has Adam hired you as his arbitrator?

If there is a file which you are versioning within TeamSite

And this file is the CGI in question, then whenever you *Submit * your changed file, it will create a new version for that file.

If you are not versioning the file, then submitting is not a relevant thing for it to be picked up by the system.
This is basically what Adam has said...and of course some other finer points that are relevant to the new CGI to be picked up by the system

ravio

Has Adam hired you as his arbitrator?

[font="]
No, but I can be your interpreter and you don't have to pay for it, its free service

[/font]