Erik N Johnson wrote:
This is generally considered highly insecure. The usual caveat about
running userland apps as root.
In fact, the generally accepted practice amongst most Linux admins is:
ALWAYS issue administrative commands using sudo.
This and Everything Erik says is True. I posted in
This is generally considered highly insecure. The usual caveat about
running userland apps as root.
In fact, the generally accepted practice amongst most Linux admins is:
ALWAYS issue administrative commands using sudo. NEVER log in
remotely as root. ONLY log in as root w/ physical access, and
gt; From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
> Jack Woehr
> Sent: Tuesday, March 31, 2009 10:28 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Stopping java based applications
>
> CHAPLIN, JAMES (CTR) wrote:
>> We want anyone in the group level to
Mark Post wrote:
Oh, minor terminological pedanticism: when the set is on the group we call
it setgid to differentiate from setuid.
Hardly minor, since the behavior it enables is completely different from setuid.
True, but I was trying not to be /breathless/ about it, just hinting to
the p
>>> On 3/31/2009 at 11:48 AM, Jack Woehr wrote:
-snip-
> Oh, minor terminological pedanticism: when the set is on the group we call
> it setgid to differentiate from setuid.
Hardly minor, since the behavior it enables is completely different from setuid.
Mark Post
CHAPLIN, JAMES (CTR) wrote:
-r--rwsr--+ 1 user group 500 Jan 21 16:23 stopServer.sh
The setuid is set on group level.
It has to be setuid to root because only root can send signal
to other user's processes. So it has to be owned by root and
should be something like -r-sr-x---
Oh, minor termi
Re: how to cause a Java app to shutdown IF you have the authority to send it
a signal:
Java JVMs on *nix generally will respond to SIGINT (2) or SIGTERM(15) by
exiting "normally".
An application an register a "shutdownhook" and run some code to clean up if
necessary.
Here's a link:
http://www.ib
at
you are suggesting?
James Chaplin
Systems Programmer, MVS, zVM & zLinux
Base Technologies, Inc
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Jack Woehr
Sent: Tuesday, March 31, 2009 10:28 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Stopp
On Tuesday 31 March 2009 09:43, CHAPLIN, JAMES (CTR) wrote:
>Our programmers have been creating java based applications that they
>start and stop using simple scripts. The start script call java to start
>the program; however the stop script issues a simple kill command
>against the PID.
>
>Our pro
>> Our programmers have been creating java based applications that they
>> start and stop using simple scripts. The start script call java to start
>> the program; however the stop script issues a simple kill command
>> against the PID.
Ugh. Wrong, wrong, wrong, unless they have set up their app
CHAPLIN, JAMES (CTR) wrote:
We want anyone in the group level to be able to also issue
the kill command (in the script). Is there a way to allow users in a
group to kill each other's started processes.
You can have a script or program
* with the setuid bit set
* with the write permissio
IMO - the java app should provide a way to tell it to exit gracefully - and
the stop script would exercise that.
Scott
On Tue, Mar 31, 2009 at 7:43 AM, CHAPLIN, JAMES (CTR) <
james.chap...@associates.dhs.gov> wrote:
> Our programmers have been creating java based applications that they
> start a
12 matches
Mail list logo
