yes i considered the wait , but since duration is more here, so is it worth using this here ?
If you just started the process asynchronously, you could wait for it. In this case, however, it looks like you started it using nohup. Most implementations of nohup that I've seen spawn a process to run the specified utility, report if the child was not successfully started, and then exit. This means that the child process created is an orphan that can't be waited for by the shell that called nohup.
If you're sitting at a terminal doing other things while waiting for the child to complete, one frequent way to manually track the process of a nohup'ed process is to use:
how to know the information of the waiting process
how to calculate the time of the process that it has taken to execute
i want to make a program that Should be able to keep a log of the processes expired(The log should contain the starting time, expiry time, time slices used, total execution... (2 Replies)
Hello Experts!!
My CPU is waiting a lot (around 33%) on I/O. I would like to find out what process(s) are waiting on the i/o. Below is my real time output of vmstat and sar.
Thanks for you help !!!!
Regards
Citrus
OS: AIX - 5L
: /u2/oracle >oslevel
5.3.0.0
: /u2/oracle... (9 Replies)
Hi,
I am calling a program that greps and returns 72536 bytes of data on STDOUT, say about 7000 lines of data on STDOUT.
I use pipe from the program am calling the above program. Naturally, I execute the above program (through execl() ) throught the child process and try to read the... (4 Replies)
Received the Timed out message consistently when I tried to jumpstart an M5000 with:
boot jsnet:speed=1000,duplex=full - install
Made the error go away by adding link-clock parameter:
boot jsnet:speed=1000,duplex=full,link-clock=master - install
"link-clock=master" disables... (1 Reply)
Dear All,
The sqlplus 'Accept' command is not waiting for user input when I include the command within a shell script.
Note: The 'Accept' command is working fine if I execute it in a SQLPLUS Prompt.
Please fins the below sample script which i tried.
SCRIPT:
--------
#!... (4 Replies)
I'm not sure if this is the right place to post this issue...but here goes...
I am converting a set of windows jobs from Control-M to AutoSys r11.3. The same command line is being executed in both systems. The Control-M job runs to compltion in about 1.5 hours, waiting for the entire batch... (3 Replies)
Let's say I start process A.sh, then start process B.sh. I call both of them in my C.sh
How can I make sure that B starts its execution only after A.sh finishes.
I have to do this in loop.Execution time of A.sh may vary everytime.
It is a parameterized script. (17 Replies)
Hello,
I am in need of running an executable provided by a vendor that basically syncs files to a db. This tool can only be run against one folder at a time and it cannot have more than one instance running at a time. However, I need to run this tool against multiple folders. Each run of the... (5 Replies)
I have to put together telnet instructions for 100s of hosts for verifying basic connectivity and get output in a neat format.
Problem- If a telnet is hung with message "Trying .... <hostname" due to firewall or routing issue the commands waits for a very long time before it times out and my... (2 Replies)
Here is my test code
process = sp.Popen( + ,
bufsize=1,
universal_newlines=True,
stdout=sp.PIPE, stderr=sp.STDOUT,
cwd=src_home)
output, _ =... (2 Replies)
Discussion started by: ezee
2 Replies
LEARN ABOUT MINIX
systemd-notify
SYSTEMD-NOTIFY(1) systemd-notify SYSTEMD-NOTIFY(1)NAME
systemd-notify - Notify service manager about start-up completion and other daemon status changes
SYNOPSIS
systemd-notify [OPTIONS...] [VARIABLE=VALUE...]
DESCRIPTION
systemd-notify may be called by daemon scripts to notify the init system about status changes. It can be used to send arbitrary
information, encoded in an environment-block-like list of strings. Most importantly, it can be used for start-up completion notification.
This is mostly just a wrapper around sd_notify() and makes this functionality available to shell scripts. For details see sd_notify(3).
The command line may carry a list of environment variables to send as part of the status update.
Note that systemd will refuse reception of status updates from this command unless NotifyAccess= is set for the service unit this command
is called from.
Note that sd_notify() notifications may be attributed to units correctly only if either the sending process is still around at the time PID
1 processes the message, or if the sending process is explicitly runtime-tracked by the service manager. The latter is the case if the
service manager originally forked off the process, i.e. on all processes that match NotifyAccess=main or NotifyAccess=exec. Conversely, if
an auxiliary process of the unit sends an sd_notify() message and immediately exits, the service manager might not be able to properly
attribute the message to the unit, and thus will ignore it, even if NotifyAccess=all is set for it.
systemd-notify will first attempt to invoke sd_notify() pretending to have the PID of the invoking process. This will only succeed when
invoked with sufficient privileges. On failure, it will then fall back to invoking it under its own PID. This behaviour is useful in order
that when the tool is invoked from a shell script the shell process -- and not the systemd-notify process -- appears as sender of the
message, which in turn is helpful if the shell process is the main process of a service, due to the limitations of NotifyAccess=all
described above.
OPTIONS
The following options are understood:
--ready
Inform the init system about service start-up completion. This is equivalent to systemd-notify READY=1. For details about the semantics
of this option see sd_notify(3).
--pid=
Inform the init system about the main PID of the daemon. Takes a PID as argument. If the argument is omitted, the PID of the process
that invoked systemd-notify is used. This is equivalent to systemd-notify MAINPID=$PID. For details about the semantics of this option
see sd_notify(3).
--uid=USER
Set the user ID to send the notification from. Takes a UNIX user name or numeric UID. When specified the notification message will be
sent with the specified UID as sender, in place of the user the command was invoked as. This option requires sufficient privileges in
order to be able manipulate the user identity of the process.
--status=
Send a free-form status string for the daemon to the init systemd. This option takes the status string as argument. This is equivalent
to systemd-notify STATUS=.... For details about the semantics of this option see sd_notify(3).
--booted
Returns 0 if the system was booted up with systemd, non-zero otherwise. If this option is passed, no message is sent. This option is
hence unrelated to the other options. For details about the semantics of this option, see sd_booted(3). An alternate way to check for
this state is to call systemctl(1) with the is-system-running command. It will return "offline" if the system was not booted with
systemd.
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
EXAMPLE
Example 1. Start-up Notification and Status Updates
A simple shell daemon that sends start-up notifications after having set up its communication channel. During runtime it sends further
status updates to the init system:
#!/bin/bash
mkfifo /tmp/waldo
systemd-notify --ready --status="Waiting for data..."
while : ; do
read a < /tmp/waldo
systemd-notify --status="Processing $a"
# Do something with $a ...
systemd-notify --status="Waiting for data..."
done
SEE ALSO systemd(1), systemctl(1), systemd.unit(5), sd_notify(3), sd_booted(3)systemd 237SYSTEMD-NOTIFY(1)