Sponsored Content
Operating Systems Solaris Java application getting killed automatically in Solaris Post 302201611 by synchro on Monday 2nd of June 2008 04:43:06 PM
Old 06-02-2008
How are you firing up the process calling it? it could be something as simple as you need to nohup the process and stick it into the background. This would prevent the process from dying when you logged out.

and no, running as a non-privileged user is a good idea. only use the root user when you have to. Depending on what your app does, you should be able to run everything as a non-privileged user at all times.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Application getting killed after one day ??? Help !!!!

Hai , I am working on a system with unix and solaris 5.8 loaded. The problem is when I leave an application open for more than one day .. it gets killed .. and my one day work goes waste and I have to start all over again .. ??? Is there any way I can find out the maximum number of... (6 Replies)
Discussion started by: ajphaj
6 Replies

2. Shell Programming and Scripting

Doubt with How to run an application automatically?

Dear sir, I want to know if i shut-down my system and while starting it next time automatically one application starts running, Is there any way? I an using Suse linux OS. PLz Help me! (4 Replies)
Discussion started by: salil2012
4 Replies

3. UNIX and Linux Applications

sun java application server 8.2

i had a confusion on the installed directory of my application server a. if I create a domain w/o putting in directory, the domain automatically goes to /var/appserver/domains directory. I need it to be under /opt/SUNWappserver/domains.. If I will include this in domain creation, may logs are... (0 Replies)
Discussion started by: lhareigh890
0 Replies

4. Programming

First Java Application

Hello all, This is my first java application since college (years ago..) What it basically needs to do, is verify that it can connect to a server, and once it is connected, run a series of AIX commands to verify that certain processes are running, and if they aren't running, it needs to start... (1 Reply)
Discussion started by: jeffs42885
1 Replies

5. Programming

Java application dying randomly

Hi, (First post, please be gental!) I have a java app that I am running on unix (centos) But it keeps dying randomly. The times seem random from anything between 3 hours and 3 days. I have a cronjob running to restart it when ever it dies but I would rather this happened less often. ... (2 Replies)
Discussion started by: sm9ai
2 Replies

6. Solaris

Java Application slowness with Xmanager

Hi! I have a m3000 server with solaris 10. Clients connecting to server using Xmanager. But when they open a Java based application its very slow and some times hanging. But when I tried with VNC it works fine. Is this a BUG in Xmanager? Or Is there any method to solve this? Thanks, Charith (3 Replies)
Discussion started by: charith.upendra
3 Replies
SETUID(2)						     Linux Programmer's Manual							 SETUID(2)

NAME
setuid - set user identity SYNOPSIS
#include <sys/types.h> #include <unistd.h> int setuid(uid_t uid); DESCRIPTION
setuid() sets the effective user ID of the calling process. If the effective UID of the caller is root, the real UID and saved set-user-ID are also set. Under Linux, setuid() is implemented like the POSIX version with the _POSIX_SAVED_IDS feature. This allows a set-user-ID (other than root) program to drop all of its user privileges, do some un-privileged work, and then reengage the original effective user ID in a secure man- ner. If the user is root or the program is set-user-ID-root, special care must be taken. The setuid() function checks the effective user ID of the caller and if it is the superuser, all process-related user ID's are set to uid. After this has occurred, it is impossible for the program to regain root privileges. Thus, a set-user-ID-root program wishing to temporarily drop root privileges, assume the identity of an unprivileged user, and then regain root privileges afterwards cannot use setuid(). You can accomplish this with seteuid(2). RETURN VALUE
On success, zero is returned. On error, -1 is returned, and errno is set appropriately. ERRORS
EAGAIN The uid does not match the current uid and uid brings process over its RLIMIT_NPROC resource limit. EPERM The user is not privileged (Linux: does not have the CAP_SETUID capability) and uid does not match the real UID or saved set-user-ID of the calling process. CONFORMING TO
SVr4, POSIX.1-2001. Not quite compatible with the 4.4BSD call, which sets all of the real, saved, and effective user IDs. NOTES
Linux Notes Linux has the concept of file system user ID, normally equal to the effective user ID. The setuid() call also sets the file system user ID of the calling process. See setfsuid(2). If uid is different from the old effective uid, the process will be forbidden from leaving core dumps. SEE ALSO
getuid(2), seteuid(2), setfsuid(2), setreuid(2), capabilities(7), credentials(7) COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2010-02-21 SETUID(2)
All times are GMT -4. The time now is 09:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy