Closing actinic from the command line

[Steve Ashdown]

Can anyone tell me if it is possible to issue a command line statement to close actinic.

I am running developer with two sites loaded and i want to run an automatic startup and update for product stock level and price purposes.

As in order to swap between sites i need to close down actinic. So for each site i wish to do the following.

1. Close actinic if it is open
2. Open actinic with with particular site and start an update

I know i can do point 2 using the following command line call:

c:\program files\actinicv7\catalog.exe /s "site1" /u

However, point 1 does not seem to be supported can anyone tell me if they have done this before and how I could go about doing this.

Regards,

[fergusw]

You could try

tskill catalog /a

from the command prompt.

This is the equivalent of killing the actinic process from the task manager.
Possibly not recommended, however it may be a suitable workaround for you?

Just a suggestion....

[wjcampbe]

Steve,

If you are on 7.0.5 then a bug has been discovered that means this version cannot be controlled from the command line.

Previous versions could be. Look for Command Lines in Help | Help Topics.

[Steve Ashdown]

I am using 7.0.5.

I can start up actinic using the command line eg. c:\program files\activinc v7\catalog.exe /s "site1" /u

However, I want to close actinic using a command line statement.

[fergusw]

"C:\Program Files\Actinic v7\Catalog.exe" /q
[preferred]

or

tskill catalog /a
[same as closing task in task manager]

[wjcampbe]

Steve,

Yes, we established in the other thread that any command line command will open Actinic, but it will not do a download nor an upload, and will not close from a command line instruction.

Nadeem confirmed this finding.

[Nadeem]

Hi there

Just wanted to add that the bug found, is if you are using Catalog, then the command line parameter will not work. However, if you are using "Business" or "Developer" then you can do the following command line

"C:\Program Files\Actinic v7\Catalog.exe" -s "Site1" /u /q
"C:\Program Files\Actinic v7\Catalog.exe" -s "Site2" /u /q

The above example would open Actinic, switch to Site1, update the site and close, then open Actinic again, switch to Site2, update and finally close

Kind Regards

[Steve Ashdown]

Fergus,

Where did u find the /q switch its not in the documentation I have !!!

Many thanks,

[Nadeem]

Hi Steve,

Where did u find the /q switch its not in the documentation I have !!!

It can be found in "Help | Help Topic" and under "Content", click on "Application Settings | Command Lines.".

Kind Regards

[Steve Ashdown]

Many thanks all !

I have what i need now.

Cheers and a good xmas,

[jxm28788]

"C:\Program Files\Actinic v7\Catalog.exe" -s "Site1" /u /q

Aaaarrrrrgggghhhh!

I just tested this and it has initiated a REFRESH not an UPDATE. This is particularly annoying as a) this is a live site, and b) it's a HUGE site an it will take frikkin ages to refresh during which time it will be offline.

But in the longer term that does also screw up the reason I was testing it in the first place - if it is working as it is supposed to...

So, is this a bug? or is /u supposed to do a refresh? either way, how can I get actinic to do an UPDATE from the command line?

[wjcampbe]

If the last upload was from the same machine, and nothing was changed that has a global effect, then a refresh is unusual. /u will normally only upload changes since the last upload.

[jxm28788]

great. it finally finished refreshing after over an hour - and I got the merge request error, and none of the scripts work.

So now I have to do a total purge and refresh so my site will be down for another hour

[pinbrook]

and I got the merge request error

delete the generated pl and pm files from both the local PC and the webserver

NOTE generated files ie xx0000001.pl etc

[jxm28788]

thanks. I'd already deleted the pl/pm files from the server side and initiated the purge and refresh - that fixed it, just took a long time.

The question is why the /u initiated the refresh in the first place? The site was already upto date, with no changes to upload. And even if there were changes then the site should have just uploaded...