Sponsored Content
Special Forums IP Networking DT messaging could not be started Post 36534 by RTM on Friday 30th of May 2003 01:56:27 PM
Old 05-30-2003
The same problem reported on Tek-Tips with some possible solutions.
 

8 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. UNIX for Dummies Questions & Answers

The Desktop Messaging System Could Not Be Started HP-UX

Hi People! I've just got a HP-UX system dumped on me. I've started it, followed all the install/setup questions, and everything was going ok, right upto when going into the desktop enviroment I got the message "The Desktop Messaging System Could Not Be Started". Now I've checked the... (8 Replies)
Discussion started by: cpiuk
8 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. Solaris

Solaris 10 CDE problem - The DT messaging system could not be started

A Google search with: +Solaris +"The DT messaging system could not be started" returns 138 hits. All of the relevant possible solutions are in this document. My apologies for such a long document but I thought I would try to minimize the resolution attempts that I've already tried. System... (1 Reply)
Discussion started by: rpollard001
1 Replies

6. 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

7. Shell Programming and Scripting

Alternative network messaging?

Hello people, which options do I have to send messages over a network from one station to another without using standard network messaging commands like write, talk und message? Thanks. (26 Replies)
Discussion started by: 123_abc
26 Replies

8. 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
REPORTER-UPLOAD(1)						 LIBREPORT MANUAL						REPORTER-UPLOAD(1)

NAME
reporter-upload - Uploads compressed tarball of problem directory. SYNOPSIS
reporter-upload [-c CONFFILE]... [-d DIR] [-u URL] DESCRIPTION
The tool is used to create a compressed tarball of the problem directory and upload it to a URL. Supported protocols include FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP and FILE. Configuration file Configuration file contains entries in a format "Option = Value". The options are: URL The URL where tarball should be uploaded. Integration with ABRT events reporter-upload can be used as a reporter, to allow users to upload compressed tarballs of problem directories to a configured URL. This usage can be configured in /etc/libreport/report_event.conf: EVENT=report_Upload reporter-upload It can be also used on the post-create event to upload it automatically. EVENT=post-create reporter-upload OPTIONS
-d DIR Path to problem directory. -c CONFFILE Path to configuration file. When used in ABRT event system, the file contains site-wide configuration. Users can change the values via environment variables. -u URL The URL where tarball should be uploaded. URL should have form protocol://[user[:pass]@]host/dir/[file.tar.gz] where protocol can be http(s), ftp, scp, or file. File protocol can't have user and host parts: file.tar.gz[1]. If URL ends with a slash, the archive name will be generated and appended to URL; otherwise, URL will be used as full file name. ENVIRONMENT VARIABLES
Environment variables take precedence over values provided in the configuration file. Upload_URL The URL where should be the tarball uploaded. AUTHORS
o ABRT team NOTES
1. file.tar.gz file:///dir/ LIBREPORT 2.1.11 06/18/2014 REPORTER-UPLOAD(1)
All times are GMT -4. The time now is 08:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy