Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Dsmcad\s+listening\s+port\s*$/: 5 ]

Total 5 documents matching your query.

1. [ADSM-L] Dsmcad listening port (score: 1)
Author: Henrik Ahlgren <pablo AT SEESTIETO DOT COM>
Date: Fri, 18 Dec 2015 11:29:06 +0200
Can someone explain why the Client Acceptor Daemon (dsmcad) opens a random port ("ANS3000I TCP/IP communications available on port XXXXX") when: - SCHEDMODE is set to POLLING - MANAGEDSERVICES is set
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2015-12/msg00071.html (10,556 bytes)

2. Re: [ADSM-L] Dsmcad listening port (score: 1)
Author: Efim <aefim771 AT GMAIL DOT COM>
Date: Fri, 18 Dec 2015 12:40:46 +0300
HI, CAD opens random port because the option WEBPORT has default value "0 0" and CAD randomly assign a free TCPport (the first parameter for CAD, the second for WEB client). I think its impossible to
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2015-12/msg00072.html (10,906 bytes)

3. Re: [ADSM-L] Dsmcad listening port (score: 1)
Author: Henrik Ahlgren <pablo AT SEESTIETO DOT COM>
Date: Fri, 18 Dec 2015 17:47:43 +0200
Am I the only one that finds this design totally unacceptable? If you're not using the webclient functionality and are only using schedmode polling, I don't see any reason why dsmcad (often running a
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2015-12/msg00076.html (11,145 bytes)

4. Re: [ADSM-L] Dsmcad listening port (score: 1)
Author: Mike De Gasperis <mike.degasperis AT WOWWAY DOT COM>
Date: Fri, 18 Dec 2015 11:00:46 -0500
You don't need to run the dsmcad technically speaking. You can just run a dsmc sched daemon or service.
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2015-12/msg00078.html (12,386 bytes)

5. Re: [ADSM-L] Dsmcad listening port (score: 1)
Author: Henrik Ahlgren <pablo AT SEESTIETO DOT COM>
Date: Fri, 18 Dec 2015 18:23:04 +0200
Running the scheduler on-demand frees up the memory used by backup jobs when it is no longer needed. Often the amount of memory used is non-trivial. And long-running schedulers leak memory, at least
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2015-12/msg00079.html (11,221 bytes)


This search system is powered by Namazu