-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 8/29/20 20:28, Mark Thomas wrote:
> On 28/08/2020 20:54, Christopher Schultz wrote:
>> Calder,
>>
>> On 8/27/20 18:23, calder wrote:
>>> On Thu, Aug 27, 2020, 16:16 Christopher Schultz <
>>> ch...@christopherschultz.net> wrote:
>>
>>> [ sni
On 28/08/2020 20:54, Christopher Schultz wrote:
> Calder,
>
> On 8/27/20 18:23, calder wrote:
>> On Thu, Aug 27, 2020, 16:16 Christopher Schultz <
>> ch...@christopherschultz.net> wrote:
>
>> [ snip ]
>
>> If you want to *kill* the application and it won't shut down on
>> its
>>> own, SIGKILL is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Calder,
On 8/27/20 18:23, calder wrote:
> On Thu, Aug 27, 2020, 16:16 Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
> [ snip ]
>
> If you want to *kill* the application and it won't shut down on
> its
>> own, SIGKILL is the answer.
On Thu, Aug 27, 2020, 16:16 Christopher Schultz <
ch...@christopherschultz.net> wrote:
[ snip ]
If you want to *kill* the application and it won't shut down on its
> own, SIGKILL is the answer. But that's not a great way to shut down an
> application /in general/ because the application might wan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Roger,
On 8/27/20 14:43, Roger Marquis wrote:
> Mark Thomas wrote:
>> Those are all application issues. The application should shut
>> itself down cleanly. Tomcat is complaining because it hasn't.
>
> I don't know Mark, most Java/Tomcat engineers ex
On 27/08/2020 19:43, Roger Marquis wrote:
> Mark Thomas wrote:
>> Those are all application issues. The application should shut itself
>> down cleanly. Tomcat is complaining because it hasn't.
>
> I don't know Mark, most Java/Tomcat engineers expect an application to
> shutdown when it's os/contai
Mark Thomas wrote:
Those are all application issues. The application should shut itself
down cleanly. Tomcat is complaining because it hasn't.
I don't know Mark, most Java/Tomcat engineers expect an application to
shutdown when it's os/container/shell/parent shuts-down. Can you help
us underst
On 25/08/2020 16:40, ratatouille wrote:
> Mark Thomas schrieb am 25.08.20 um 11:31:59 Uhr:
>
>> On 25/08/2020 11:07, ratatouille wrote:
>
>>> I am running openmeetings on a CentOS 8 server and start it with startup.sh
>>> in the bin-folder.
>>>
>>> The problem is when I execute shutdown.sh the p
The only time I ran into this is when I had conflict on the shutdown
port or multiple instances which had a port conflict on the shutdown
port. Other than that, I don't know. Possible permissions issues?
Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
AWS Certified Clo
Mark Thomas schrieb am 25.08.20 um 11:31:59 Uhr:
> On 25/08/2020 11:07, ratatouille wrote:
> > I am running openmeetings on a CentOS 8 server and start it with startup.sh
> > in the bin-folder.
> >
> > The problem is when I execute shutdown.sh the process still exists after.
> > I have to kill
On 25/08/2020 11:07, ratatouille wrote:
> Hello!
>
> I am running openmeetings on a CentOS 8 server and start it with startup.sh
> in the bin-folder.
>
> The problem is when I execute shutdown.sh the process still exists after.
> I have to kill it manually.
>
> #
> -
Hello!
I am running openmeetings on a CentOS 8 server and start it with startup.sh
in the bin-folder.
The problem is when I execute shutdown.sh the process still exists after.
I have to kill it manually.
# -
# Stop scrip
12 matches
Mail list logo
