Sponsored Content
Top Forums Shell Programming and Scripting Alternative network messaging? Post 302720887 by 123_abc on Wednesday 24th of October 2012 06:36:25 PM
Old 10-24-2012
I would like to implement a push service, but I havent't found any example for that on the internet yet. The step from "kill" command to push service is too large for me.
 

6 More Discussions You Might Find Interesting

1. Programming

Instant Messaging App Help

I was hoping someone could assist me on a text-based instant messaging client(using UDP) I am working on. I have the network communication basics already in place but, specifically, needed some further help on the "messaging other users" and "getting a user list" functions. The server code that... (0 Replies)
Discussion started by: AusTex
0 Replies

2. IP Networking

DT messaging could not be started

this id the message i get with a suggestions to check those files: /etc/src.sh /etc/hosts /usr/adm/inetd.sec i have little knowledge of hoe to edit those files/ i went to the etc library and didn't found src.sh file. what should i do? also didn't find the inetd.sec file In the host... (3 Replies)
Discussion started by: amirp
3 Replies

3. UNIX and Linux Applications

how do i enable messaging

hi guyz i work as a system administrator for some organization(am a newbie). one of the solaris machines is loaded with the messenger server...all configured by a former administrator. my task was to create user accounts for the mail and calendar services and as i checked its not working .....i... (0 Replies)
Discussion started by: henokia4j
0 Replies

4. Programming

problems while using messaging queues....

hi I am using posix functions such as mq_open, mq_close and including the mqueue.h. but its giving a linking error,"undefined reference to mq_open and mq_close". it it that we have to link some library or so while compiling... plzzz help Thanxs Mohit (0 Replies)
Discussion started by: mohit3884
0 Replies

5. UNIX for Advanced & Expert Users

The DT messaging system could not be started

Hello All, I am getting " The DT messaging system could not be started" message when wants to login as root on a box running on tru64 5.1A. /etc/hosts is ok. when i see in .dt/errorlog it shows message server could not be started. Thanks for help. Awadhesh (2 Replies)
Discussion started by: Awadhesh
2 Replies

6. Shell Programming and Scripting

The DT messaging system could not be started.

Good Morning, Users can no longer log into SunBlade 2500 Solaris 9 system (though root still can). Here's what I'm getting and what I've done. I'm most suspicious of the full drive since that pops up twice and I did see one looks full. What's a good way to reduce what's on it?- or.. what else... (2 Replies)
Discussion started by: Stellaman1977
2 Replies
Mono(Mono 1.0)															    Mono(Mono 1.0)

NAME
mono-service, mono-service2 - Mono ServiceProcess host SYNOPSIS
mono-service [options] program.exe DESCRIPTION
The mono-service is a host to run services built with the ServiceProcess assembly. Use mono-service to run services that use the 1.0 assemblies and use mono-service2 to run services that use the 2.0 assemblies. Services can be paused by sending the SIGUSR1 signal to the process, and execution can be resumed by sending the SIGUSR2 signal. The ser- vice can be cleanly shutdown by sending the SIGTERM signal to the process. Mono programs started with mono-service run with the MONO_DISABLE_SHM variable set. This means that certain Mono features that depend on it are not available to services. The following options can be used to control the service: -d:DIRECTORY Use this option to specify the working directory for the service. The default is the current directory. -l:LOCKFILE Specifies the file to use for locking, the default is a filename constructed in /tmp based on the name of the program that hosts the service. -m:MESSAGE Name to show in the syslog. -n:NAME Use this to specify the service to be launched (if the program contains more than one service). The default is to run the first defined service. --debug Use this option to prevent mono-service from redirecting stdin and stdout and prevent the program to be sent to the background. Equivalent to --no-daemon --no-daemon Use this option to prevent mono-service from redirecting stdin and stdout and prevent the program to be sent to the background. Equivalent to --debug. CONTROL
You can control the service by sending signals to the process, you can use the following commands: Pausing service: kill -USR1 `cat <lock file>` Resuming service: kill -USR2 `cat <lock file>` Stopping the service: kill `cat <lock file>` EXAMPLES
Start the MyService.exe assembly, with a lock in /root/service-lock: mono-service -l:/root/service-lock MyService.exe DEBUGGING
Messages produced by the service are logged on syslog. MAILING LISTS
Visit http://lists.ximian.com/mailman/listinfo/mono-list for details. WEB SITE
Visit: http://www.mono-project.com for details SEE ALSO
mono(1) N:System.ServiceProcess Mono(Mono 1.0)
All times are GMT -4. The time now is 11:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy