Hello all,
I would be happy if any one could help me with a shell script that would determine all the processes running on a Unix server and post a mail if any of the process is not running or aborted.
Thanks in advance
Regards,
pradeep kulkarni.
:mad: (13 Replies)
Hi Experts, we do have a shell script for Unix Solaris, which will kill all the process manullay, it used to work in my previous env, but now it is throwing this error.. could some one please help me to resolve it
This is how we execute the script (and this is the requirement) ... (2 Replies)
get email notification from from system when a process from XXXX user takes longer than 15 min run.Let me know the time estimation for the same.
hi ,any one please tell me , how to write a script to get email notification from system when a process from as mentioned above a xxxx user takes... (1 Reply)
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (0 Replies)
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (1 Reply)
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (6 Replies)
I am writing a script to kick off a process to gather logs on multiple nodes in parallel using "&". These processes create individual log files. Which I would like to filter and convert in CSV format after they are complete. I am facing following issues:
1. Monitor all Processes parallelly.... (5 Replies)
Team,
I have multiple batchjobs running in VM, if I do ps -ef |grep java or tomcat I am getting multiple process list.
How do I get my exact tomcat process running and that is unique? via shell script? (4 Replies)
Discussion started by: Ghanshyam Ratho
4 Replies
LEARN ABOUT DEBIAN
sndstat
7(16 December 2012) 7(16 December 2012)
NAME
sndstat - Open Sound System status device
DESCRIPTION
/dev/sndstat is a text formatted device special file that returns information about available (OSS) sound devices. This device file is
obsolete and the ossinfo(1) utility should be used instead.
Notice that the device numbering used in this file is different that the official numbering used by ossinfo(1) and some other utilities.
/dev/sndstat uses device numbers that match the "legacy" /dev/dspN, /dev/midiN and /dev/mixerN device files.
Application programs should not use /dev/sndstat to obtain information about the sound devices. The format of this file may change in the
future and /dev/sndstat may even be removed from OSS in distant future. OSS 4.0 and later has an ioctl interface for getting detailed and
reliable information about the devices.
AUDIO USAGE HISTORY
/dev/sndstat reports some history information about previously run audio applications. This section is a debugging aid for application
developers and it will be moved to the ossinfo program in the future.
For example:
History:
/dev/oss/hdaudio0/pcm0.10: pid 6326 cmd 'error_test' OUT Play events:01009:2 Rec events:01002:0
/dev/oss/hdaudio0/pcm0.10: pid 6329 cmd 'mpg123' OUT
/dev/oss/hdaudio0/pcm0.10: pid 6329 cmd 'mpg123' OUT
/dev/oss/hdaudio0/pcm0.10: pid 6329 cmd 'mpg123' OUT
Each line will show the the device name, PID and name of the application (if known) and access mode (IN and/or OUT). There may also be
additional info about buffer underruns/overruns and other recording and playback related events.
Each Play and rec events consist of 5-6 digit event code and a parameter separated by a colon. A list of defined event codes and their
explanations can be found from http://manuals.opensound.com/developer/oss_error_codes.html. Purpose of these events is to inform applica-
tion developers by potential problems in their code.
COMPATIBILITY
/dev/sndstat has been available in all OSS versions. However in OSS 4.0 and later this device file should only be used by applications
written for earlier OSS versions.
OPTIONS
None
PROGRAMMING INFORMATION
Some applications use /dev/sndstat to find the audio devices available in the system. This method is no longer recommended. Applications
should use the SNDCTL_AUDIOINFO(2) ioctl call to find the devices.
SEE ALSO
o dsp(7) - Audio device files
o mixer(7) - Mixer (control panel) device files
o midi(7) - MIDI device files
FILES
/dev/sndstat
AUTHOR
4Front Technologies
OSS Devices 7(16 December 2012)