04-13-2007
I think when you log out it kills the process since you started it "live". You should put your webserver in a startup script linked from /etc/rc3.d or whichever you want if you would like it running at all times when the server is up.
If you do start it live, use nohup to make it so the process started doesn't die when you log out.
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi guys, I'm a firsttime poster. My makefile is relinking everytime, even if nothing changes. Is there anyway to have it stop doing this?
Here the makefile:
F77C = /usr/bin/f77 -O
VERSION =9.4
VPATH = ../poten
# executables that can be built from this makefile
OH3S =... (10 Replies)
Discussion started by: bellings
10 Replies
2. Shell Programming and Scripting
Hi there.
How do I make the DB connection see the parameter variables passed to the unix script ? The code snippet below isn't working properly.
sqlplus << EOF
user1@db1/pass1
BEGIN
PACKAGE1.perform_updates($1,$2,$3);
END;
EOF
Thanks in advance,
Abrahao. (2 Replies)
Discussion started by: 435 Gavea
2 Replies
3. Linux
Whenever I quit out of reading a man page, it clears the screen.
I do not like this behavior, as I'd like to keep part of the man page on the screen while I type out a command.
How do I stop this behavior? (6 Replies)
Discussion started by: akbar
6 Replies
4. Shell Programming and Scripting
Hi,
Apologies if anyone has read my recent post on the same subject in the Linux forum, just thought actually the solution might more likely come from scripting.
Essentially, I am trying to restrict access to directories based on the user's name AND their location on a session-by-session... (3 Replies)
Discussion started by: en7smb
3 Replies
5. Solaris
I am not able to login in gnome session and java session in Sun solaris 9& 10 respectively through xmanager as a nis user, I am able to login in common desktop , but gnome session its not allowing , when I have given login credentials, its coming back to login screen, what shoul I do to allow nis... (0 Replies)
Discussion started by: durgaprasadr13
0 Replies
6. Shell Programming and Scripting
H! I have written script where it need to invoke the perl script in background, then write the pid in temp file then bring back the job to foreground. whenever the Ctrl-C or Ctrl-Z is pressed in the script has to exit and prompt should be dispalyed. but this script causing exit from shell session... (2 Replies)
Discussion started by: jramesh1
2 Replies
7. Shell Programming and Scripting
Hi ,
I am running a script on multiple servers.When I run that script on one server,I want to exit from that server and want to go to next server.PFB script:
Suppose there are 3 servers:server1,server2,server3.I am currently in server1.
for h in {2..3}
do
ssh username@server$h <<EOF
... (4 Replies)
Discussion started by: sonu141
4 Replies
8. UNIX for Dummies Questions & Answers
Hi Everyone,
I am a new unix user. I started a qlogin session in SSH terminal, then I closed the window assuming that the qlogin session will be closed automatically. But it was still running. I tried to kill the process using kill ID or kill -9 ID, but the ID I got using
ps aux | grep... (1 Reply)
Discussion started by: ttroo2003
1 Replies
9. UNIX for Dummies Questions & Answers
Hello All,
My question has to do with a Remote Desktop Session going from my Linux HOST to a Windows GUEST.
Linux OS: OpenSuSE 11.4 i586
Windows OS: Windows Server 2003
For some reason after I have run rdekstop to connect to the Windows Guest, whenever I click on the Shift key I get the... (0 Replies)
Discussion started by: mrm5102
0 Replies
LEARN ABOUT HPUX
intrbald
intrbald(1M) intrbald(1M)
NAME
intrbald - daemon for balancing interrupts
SYNOPSIS
interval |
DESCRIPTION
Balancing interrupts is a process which distributes interrupts across the available CPUs in an optimal fashion. This action is performed
by (see intctl(1M)).
Performing frequent CPU migrations between system partitions may require you to perform periodic balancing of interrupts. This is espe-
cially true with systems that use WLM (Workload Manager), iCAP (Instant Capacity), and vPars (Virtual Partitions) products. If the fre-
quency of CPU migration is high, then balancing of interrupts should be performed more frequently.
The daemon monitors the system for imbalance in interrupt distribution. If an imbalance is detected after the specified interval executes
to balance the interrupt distribution. uses the parameters from the configuration file for balancing the interrupts. For more information
about the command, see intctl(1M) and the configuration file.
The daemon is started from the general purpose sequencer script (see rc(1M)), at run level 2 and is killed at run level 1. By default, the
daemon is not enabled. The daemon configuration file must be edited and the parameter set to in order to enable running the daemon. After
setting to for the first time, you can start the daemon manually by executing the script Otherwise, the daemon will automatically start the
next time the system is restarted.
Any actions performed by the daemon are logged in and details of interrupt migrations performed will be logged in the file
Options
recognizes the following options:
Instructs the running daemon to reexamine the configuration file
If the parameter has been updated, then the running daemon uses the new value. If the parameter is set to then the running
daemon stops executing.
The daemon checks if the system requires any balancing of interrupts
after interval seconds; the valid range is 5 seconds to seconds (see limits(5)).
This value can also be specified persistently in the configuration file by setting the parameter.
The default value is 60 seconds.
Setting this value too small can cause unnecessary interrupt migrations.
Gracefully kills the running daemon.
intrbald rc Configuration File
is the configuration file.
The following parameters can be persistently specified in this configuration file:
Specifies if the daemon should be started automatically during the system bootup process by the script. The daemon will only be started
automatically if this parameter is set to
NOTE: This value is by default. Before using the daemon, needs to be changed to in the file. Then the daemon needs to be started,
either manually by running or it will be started automatically at next boot via the script.
The daemon checks if the system requires any
interrupt balancing after this interval. The interval is specified in seconds; the valid range is 5 seconds to seconds (see lim-
its(5)). The default is 60 seconds.
Setting this value too small could cause unnecessary interrupt migrations.
RETURN VALUE
Exit values are:
Successful completion.
An error condition occurred.
WARNINGS
The command can be executed only by the superuser. This command should be used only by performance analysts for performance tuning pur-
poses. If the interrupts are not redistributed properly, a possible decrease in overall system performance can occur. Some processors can
become overloaded while other processors will not be optimally utilized.
FILES
configuration file. See the section above.
script.
start symbolic link.
kill symbolic link.
daemon log file.
SEE ALSO
intctl(1M), ioscan(1M), rc(1M), limits(5).
intrbald(1M)