Sponsored Content
Full Discussion: MSend Details
Top Forums Shell Programming and Scripting MSend Details Post 302330362 by balajiora on Wednesday 1st of July 2009 03:35:37 AM
Old 07-01-2009
MSend Details

Hi,

Can anyone please share me the details of MSEND Command. Where can I get complete information.

Waiting for reply. Thanks in Advance

Regards
BS
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How does one get HW details?

I need to do a full system inventory & pull details for: CPU Mem HDD (Size, config, partitions) Is there a single command to get this, or separate for each? Thanks, Gareth. (3 Replies)
Discussion started by: garethh
3 Replies

2. Red Hat

How to find the os and h/w details

Hi Need to know the version(suse/redhat) and processor info(x86/itanium/amd etc). I tried uname -a but cannot understand what is what... Linux myworkhost 2.4.21-4.ELsmp #1 SMP Fri Oct 3 17:52:56 EDT 2003 i686 i686 i386 GNU/Linux I dont have the root password, I can only ssh and have to... (3 Replies)
Discussion started by: amiri2000
3 Replies

3. UNIX for Dummies Questions & Answers

Details on available disk

Hi everybody.. I am looking for an alternative command to 'format' since this is allowed only to the root user. How do I do to get the same information as command format does here below ? AVAILABLE DISK SELECTIONS: 0. c0t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> ... (4 Replies)
Discussion started by: Riddick61
4 Replies

4. Solaris

Configuration details

hi can you please tell me how to get the configuration details from unix server. Rajesh. (6 Replies)
Discussion started by: pmrajesh21
6 Replies

5. HP-UX

HP-UX Server Details

OS: HP-UX I need the following details from HP-UX server. I don't have root login, so most of the commands require root privilege 1. No of cpu in the server 2. Total Memory, Free & Used 3. Space used and free space Any help would be highly appreciated (6 Replies)
Discussion started by: manijash
6 Replies

6. Shell Programming and Scripting

Collecting details

Hi all, I am having lots of oracle servers. I want to collect some health check details from all the server and report to one single centralized server. What would be best solution for this? OS: AIX Thanks Gopal (1 Reply)
Discussion started by: ilugopal
1 Replies

7. Shell Programming and Scripting

getting Details of pf -ef

Hi All, I have a Linux server where many script run on daily basis through crontab. I could see some entries on my name but I am not able to get the details. >>ps -ef | grep an001 >>root 9905 1742 0 Apr17 ? 00:00:00 sshd: an001 >>an001 9907 9905 0 Apr17 ? ... (3 Replies)
Discussion started by: infyanurag
3 Replies

8. UNIX for Dummies Questions & Answers

at -l doesnt give details of the scheduled job. How to get the details?

I have scheduled couple of shell scripts to run using 'at' command. The o/p of at -l is: $ at -l 1320904800.a Thu Nov 10 01:00:00 2011 1320894000.a Wed Nov 9 22:00:00 2011 1320876000.a Wed Nov 9 17:00:00 2011 $ uname -a SunOS dc2prcrptetl2 5.9 Generic_122300-54 sun4u sparc... (2 Replies)
Discussion started by: superparticle
2 Replies

9. Solaris

Mem Details

<A href="mailto:root@sssdpmds01$"> root@sssdpmds01$ prstat -a PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP 13831 ogw 2613M 2108M cpu12 0 0 277:43:27 3.9% java/1201 4312 ogw 2641M 2092M sleep 59 0 562:45:51 2.1% java/1235 4469 ogw ... (2 Replies)
Discussion started by: jojo123
2 Replies

10. UNIX for Beginners Questions & Answers

Audit details

Hi All , I'm a fresher and don't have much knowledge on scripting. I want to extract log details like count of rows inserted , job start time and end time from Datastage log and want to insert into table. Can you please me in this (2 Replies)
Discussion started by: Srikavya_manda
2 Replies
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 237 SYSTEMD-NOTIFY(1)
All times are GMT -4. The time now is 10:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy