|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
Processes, Services, Daemon's and Subsystems
Post 41899 by Perderabo on Thursday 16th of October 2003 05:37:21 PM
10-16-2003
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I am new to the world of Unix, I need some help in doing a small project at work.
Can anyone point out any good references for the below functions?
Objective
---------
To write a daemon that will run in the central server to
1) access our process(I will find this out), log down... (1 Reply)
Discussion started by: seongyin
1 Replies
2. UNIX for Advanced & Expert Users
Is there a way to monitor certain processes and if they hang too long to kill them, but certain scripts which are expected to take a long time to let them go?
Thank you
Richard (4 Replies)
Discussion started by: ukndoit
4 Replies
3. AIX
Hi,
As part of our maintenance schedule, we reboot our systems every few months to test HACMP and etc... etc....
It looked like everything was normal but when we tried to bring up HACMP, we didn't see anything in the /etc/hacmp.out and we didn't see any processes associated with HACMP running.... (0 Replies)
Discussion started by: xender69
0 Replies
4. Solaris
Hi
Is there an easy way to identify and group currently running processes into OS processes and APP processes. Not all applications are installed as packages.
Any free tools or scripts to do this?
Many thanks. (2 Replies)
Discussion started by: wilsonee
2 Replies
5. Ubuntu
Hello,
I am debugging a program which works as daemon. It sigfaults, unfortunately I'm unable to generate core dump file. Here is what I am doing:
tsurko@bastila:~$ ulimit -c unlimited
tsurko@bastila:~$ ulimit -c
unlimited
tsurko@bastila:~$ cat /etc/sysctl.conf | grep 'core_pattern'... (1 Reply)
Discussion started by: tsurko
1 Replies
6. Shell Programming and Scripting
I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time.
Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies
7. Red Hat
I had a doubt if any services need to be restarted if port no in /etc/services in an RHEL setup is changed. For eg, the port no of 443 for SSL may need to be changed.
I hope my query is clear whether any services need to be restarted if port no in /etc/services is changed.
Please revert with... (10 Replies)
Discussion started by: RHCE
10 Replies
8. Solaris
I normally use "chkconfig" to configure start up services in a particular run level.....
But i don't know how to do it in solaris 10.... please help me !!! (2 Replies)
Discussion started by: vamshigvk475
2 Replies
9. Shell Programming and Scripting
Hi,
I just started working on a script. After my research, i found a command which can help me:
AIM: To build a script which starts the services (Services 1) on server 1 automatically whenever its down. And it has a dependency on other service (Service 2) on Server 2.
So my script has to... (4 Replies)
Discussion started by: draghun9
4 Replies
10. Linux
Hi,
Is there any way to run chkconfig --list and to display all daemon processes in PRIORITY order, not in alphabetic order?
Thank you. (4 Replies)
Discussion started by: hce
4 Replies
LEARN ABOUT V7
accept
accept(1M) System Administration Commands accept(1M) NAME
accept, reject - accept or reject print requests SYNOPSIS
accept destination... reject [-r reason] destination... DESCRIPTION
accept allows the queueing of print requests for the named destinations. reject prevents queueing of print requests for the named destinations. Use lpstat -a to check if destinations are accepting or rejecting print requests. accept and reject must be run on the print server; they have no meaning to a client system. OPTIONS
The following options are supported for reject: -r reason Assigns a reason for rejection of print requests for destination. Enclose reason in quotes if it contains blanks. reason is reported by lpstat -a. By default, reason is unknown reason for existing destinations, and new printer for destinations added to the system but not yet accepting requests. OPERANDS
The following operands are supported. destination The name of the destination accepting or rejecting print requests. Destination specifies the name of a printer or class of printers (see lpadmin(1M)). Specify destination using atomic name. See printers.conf(4) for information regarding the naming conventions for atomic names. EXIT STATUS
The following exit values are returned: 0 Successful completion. non-zero An error occurred. FILES
/var/spool/lp/* LP print queue. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWpcu | +-----------------------------+-----------------------------+ |CSI |Enabled (see NOTES) | +-----------------------------+-----------------------------+ SEE ALSO
enable(1), lp(1), lpstat(1), lpadmin(1M), lpsched(1M), printers.conf(4), attributes(5) NOTES
accept and reject affect only queueing on the print server's spooling system. Requests made from a client system remain queued in the client system's queueing mechanism until they are cancelled or accepted by the print server's spooling system. accept is CSI-enabled except for the destination name. SunOS 5.10 8 Feb 1999 accept(1M)