[
http://jira.dspace.org/jira/browse/DS-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue updated DS-516:
---------------------------
Assignee: Stuart Lewis
>From discussion in Developers Meeting on 14 April 2010:
[17:16] <tdonohue> DSRUN does not start Service Manager -
http://jira.dspace.org/jira/browse/DS-516
[17:17] <mdiggory> thats a big one
[17:17] <mdiggory> we need to finish this out and either remove the shell
scripts or adjust them. mostly this just needs commiting
[17:18] <tdonohue> right. sounds like removing the shell scripts may be best
[17:18] <tdonohue> should we remove in 1.6.1, or just mark obsolete in 1.6.1
(and officially remove in 1.7)? any thoughts?
[17:19] <PeterDietz> its confusing to see them there, especially since all
functionality is also done by ./dspace
[17:19] <mdiggory> need to be fixed or go away, I've even got devs scratching
their heads about why their shell scripts arn't working
[17:20] <mdiggory> problem is that for some, they may have created their own
new ones or have code dependent on the dsrun script
[17:21] <mdiggory> suggest twofold attack
[17:21] <mdiggory> 1.) make sure dsrun calls "dspace dsrun"
[17:21] <mdiggory> 2.) remove all the rest of the scripts
[17:21] <mdiggory> but dsrun and dspace
[17:21] <stuartlewis> Deprecate in 161, and remove in 1.7? +1
[17:22] <mdiggory> as long as the rest of the scripts "work" in 1.6.1
[17:22] <stuartlewis> Assign to me if you want, and I'll get them removed. I've
also written a patch that allows the equivalent of dsrun via the launcher:
[dspace]/bin/dspace dsrun {class}
[17:22] <stuartlewis> Gotta run. Bye.
[17:22] <tdonohue> ok, assign DS-516 to stuartlewis ....
> DSRUN does not start Service Manager
> ------------------------------------
>
> Key: DS-516
> URL: http://jira.dspace.org/jira/browse/DS-516
> Project: DSpace 1.x
> Issue Type: Bug
> Components: DSpace API
> Affects Versions: 1.6.0
> Reporter: Mark Diggory
> Assignee: Stuart Lewis
> Fix For: 1.6.1
>
> Attachments: dsrun.patch
>
>
> I'll also comment you'll want to use the "dspace" CLI script to launch
> executions rather than "dsrun" as the DSpace services framework need to be
> started properly before updates happen to services.
> Comment to the developers... We rather missed this in our architecture of the
> new execution environment. We may want to consider removing dsrun or
> enabling a Main wrapper around it similar to the "dspace" shell runner so
> that the Spring/Services framework is properly started. An alternative would
> be to make "dspace" more flexible to support passing Classnames directly to
> it in the same manner as "dsrun".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
