12-13-2004
OSI 9.0 Installation
Dear
After i received a demo license for OSI 9.0 from SUN , i installed the packages . but when i tried to start the osinet deamon ( /etc/rc2.d/S90osinet ) i am getting the foellowing errror
# ./S90osinet start
starting osi daemon/usr/sbin/osinetd cannot find a valid license (STACK 9.0)
unable to start OSI daemon
#
The license is correct . altough i rechecked the volidity of the license .
7 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
what is it??
I looked everywhere but cant seem to find it
also where can I get information about the difference between NFS 2 or NFS 3?? (6 Replies)
Discussion started by: TRUEST
6 Replies
2. IP Networking
after reading a paper about the OSI-model I'm not exactly sure how to look at this model.
Does data (a file) travel from the application level "down" each layer at the client
Application
V
Presentation
V
Session
V
Transport
V
Network
V
Data link
V
|
|
| (Physical)
| (3 Replies)
Discussion started by: J.P
3 Replies
3. Solaris
Hi.
I get the folloing message if i try to start the osinet deamon:
# /etc/rc2.d/S90osinet start
starting osi daemonunable to unload all the osi modules
some OSI applications may be running
unable to start OSI daemon
#
Has anyone an idea what is going wrong?
Answers to mail: (Note... (1 Reply)
Discussion started by: morenqfj
1 Replies
4. Solaris
I'm using OSI version 9.0 with solaries OS , I 'm thinking of analysing the tracing while sending information through OSI layers , I want to analyze exactly the BER data ? Any one could provide an examples , I know the command for tracing these information but i need to understand the bytes travels... (1 Reply)
Discussion started by: atiato
1 Replies
5. Debian
Is there OSI telecom application which can be installed on debian similar to Solstice Solaries OSI ?
I need to get it on debian to build cmise and communicate with Network element . (0 Replies)
Discussion started by: atiato
0 Replies
6. IP Networking
Hi friends,
I hope everyone is doing fine. I have this confusion regarding the OSI model. I have been reading a book on datacommunication and networking which discusses the OSI model in great detail. One thing that I can't figure out is the OSI daigram in this book. It shows communication between... (1 Reply)
Discussion started by: gabam
1 Replies
7. Solaris
dear all,
i am working on test server with solaris 10 , after installing OSI deamon i stopped it for a test now when i am starting again i am getting this message that i ggoled and search evrywhere and haven't any response i will be glade for any help in here mate the error was :
./osinet... (1 Reply)
Discussion started by: semaan
1 Replies
HALD(8) System Manager's Manual HALD(8)
NAME
hald - HAL daemon
SYNOPSIS
hald [options]
DESCRIPTION
hald is a daemon that maintains a database of the devices connected to the system system in real-time. The daemon connects to the D-Bus
system message bus to provide an API that applications can use to discover, monitor and invoke operations on devices. For more information
about both the big picture and specific API details, refer to the HAL spec which can be found in /usr/share/doc/hal-doc/spec/hal-spec.html
depending on the distribution.
OPTIONS
The following options are supported:
--daemon=yes|no
Specify whether to run in the foreground or the background.
--verbose=yes|no
Enable verbose debug output.
--use-syslog
Enable logging of debug output to the syslog instead of stderr. Use this option only together with --verbose.
--help Print out usage.
--version
Print the version of the daemon and exit.
BUGS AND DEBUGGING
Please send bug reports to either the distribution or the HAL mailing list, see http://lists.freedesktop.org/mailman/listinfo/hal on how to
subscribe.
First, to obtain useful debug traces you will need to have debuginfo packages installed. On a Fedora system this is in the hal-debuginfo
package and can be installed via the yum update program.
Second, shut down the existing hald daemon instance; on a Fedora system this is achieved by
/etc/init.d/haldaemon stop
After having shut down the daemon, you might want to run
pkill hald
to ensure that all the helper processe of hald are killed too. To start the HAL daemon, use
/usr/sbin/hald --daemon=no --verbose=yes
If the daemon crashes, you can start it under a debugger via
gdb /usr/sbin/hald
and then typing
run --daemon=no --verbose=yes
at the (gdb) prompt. To capture a back trace, use the bt command and attach this to the bug report.
Please also attach the output of lshal(1) in the bug report if possible (it's not possible if the hald daemon crashed). If the nature of
the bug has to do with hotplugging, attach two outputs of lshal(1) - one before the device hotplug event and one after.
SEE ALSO
udev(7), dbus-daemon(1), lshal(1), hal-set-property(1), hal-get-property(1), hal-find-by-property(1), hal-find-by-capability(1), hal-is-
caller-locked-out(1)
AUTHOR
Written by David Zeuthen <david@fubar.dk> with a lot of help from many others.
HALD(8)