Sponsored Content
Full Discussion: Help: for XDMCP
Operating Systems Solaris Help: for XDMCP Post 302105181 by andryk on Wednesday 31st of January 2007 06:33:41 AM
Old 01-31-2007
First of, check the daemon if its running if not start it
Code:
ps -ef |grep dtlogin
/etc/rc2.d/S99dtlogin start # start it if no dtlogin process if running

You might try to use the direct method instead of the broadcast one as sometimes it works sometimes not like sparcguy said Smilie
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

XDMCP setup

How do you verify your XDMCP setup on Sun Solaris? I am trying to establish a connection, but no XDMCP servers were found. (1 Reply)
Discussion started by: heinb
1 Replies

2. IP Networking

xdmcp and netstat

On my linux box, i run netstat -l and i see xdmcp in the list but it doesn't have LISTEN as its state, see what it shows below, I'm wondering if this might explain why i can't see it in my exceed broadcast listing of servers broadcasting on our net? My unix boxes don't show this at all. Proto ... (1 Reply)
Discussion started by: kymberm
1 Replies

3. Solaris

xdmcp on Solaris 10 x86

I recently downloaded and installed Solaris 10 on an Intel PC. I want to connect to it via XDMCP from another client. I found you can enable xdmcp as follows: Launch -> Applications -> Utilities -> Administration -> Login Screen Setup Then selected the XDMCP tab and click the box that... (1 Reply)
Discussion started by: lyonsd
1 Replies

4. HP-UX

xdmcp on HP-UX

Anybody know how to set up xdmcp on HPUX (11.0 +)? Thanks. (1 Reply)
Discussion started by: lyonsd
1 Replies

5. HP-UX

xdmcp config

hi everybody, can anyone please tell me what are things for verify to have an xdmcp connexion ton HPUX 10.20 host best regards (0 Replies)
Discussion started by: hmaiida
0 Replies

6. UNIX for Dummies Questions & Answers

XDMCP no password

Hello all, Does anyone know or have configure their system to allow no password during an XDMCP session. I' m running Redhat whit gdm manager. Thanks! (0 Replies)
Discussion started by: larryase
0 Replies

7. SCO

xdmcp dies in sco600

We have just installed a sco 600 server. Xdmcp comes up in the chooser but if you don't log in within a few minutes it disappears and you have to log in and then out on the console before you can see it in the chooser. Xdmcp is suppossed to be setup for continuous logins automatically. We... (0 Replies)
Discussion started by: khafner
0 Replies

8. AIX

How to enable XDMCP?

Hello everyone, I installed AIX the other day (several times!) but I can't get XDMCP to work. I remember from when I installed it the last time it worked out of the box. So why doesn't it work now? This is the error message I get: XDMCP fatal error: Session failed Session 2 failed for... (3 Replies)
Discussion started by: Kotzkroete
3 Replies

9. Solaris

XDMCP Error

Hi Friends, I am not able to login through X browser from Windows Machine to Sun Fire V890 server. Solaris 10 is installed on this machine. Please suggest me what changes need to be done in Solaris Server. Thanks in Advance (2 Replies)
Discussion started by: durgaprasadr13
2 Replies
IO::Async::Timer::Countdown(3pm)			User Contributed Perl Documentation			  IO::Async::Timer::Countdown(3pm)

NAME
"IO::Async::Timer::Countdown" - event callback after a fixed delay SYNOPSIS
use IO::Async::Timer::Countdown; use IO::Async::Loop; my $loop = IO::Async::Loop->new; my $timer = IO::Async::Timer::Countdown->new( delay => 10, on_expire => sub { print "Sorry, your time's up "; $loop->stop; }, ); $timer->start; $loop->add( $timer ); $loop->run; DESCRIPTION
This subclass of IO::Async::Timer implements one-shot fixed delays. The object implements a countdown timer, which invokes its callback after the given period from when it was started. After it has expired the Timer may be started again, when it will wait the same period then invoke the callback again. A timer that is currently running may be stopped or reset. For a "Timer" object that repeatedly runs a callback at regular intervals, see instead IO::Async::Timer::Periodic. For a "Timer" that invokes its callback at a fixed time in the future, see IO::Async::Timer::Absolute. EVENTS
The following events are invoked, either using subclass methods or CODE references in parameters: on_expire Invoked when the timer expires. PARAMETERS
The following named parameters may be passed to "new" or "configure": on_expire => CODE CODE reference for the "on_expire" event. delay => NUM The delay in seconds after starting the timer until it expires. Cannot be changed if the timer is running. A timer with a zero delay expires "immediately". remove_on_expire => BOOL Optional. If true, remove this timer object from its parent notifier or containing loop when it expires. Defaults to false. Once constructed, the timer object will need to be added to the "Loop" before it will work. It will also need to be started by the "start" method. METHODS
$expired = $timer->is_expired Returns true if the Timer has already expired. $timer->reset If the timer is running, restart the countdown period from now. If the timer is not running, this method has no effect. EXAMPLES
Watchdog Timer Because the "reset" method restarts a running countdown timer back to its full period, it can be used to implement a watchdog timer. This is a timer which will not expire provided the method is called at least as often as it is configured. If the method fails to be called, the timer will eventually expire and run its callback. For example, to expire an accepted connection after 30 seconds of inactivity: ... on_accept => sub { my ( $newclient ) = @_; my $watchdog = IO::Async::Timer::Countdown->new( delay => 30, on_expire => sub { my $self = shift; my $stream = $self->parent; $stream->close; }, ); my $stream = IO::Async::Stream->new( handle => $newclient, on_read => sub { my ( $self, $buffref, $eof ) = @_; $watchdog->reset; ... }, on_closed => sub { $watchdog->stop; }, ) ); $stream->add_child( $watchdog ); $watchdog->start; $loop->add( $watchdog ); } Rather than setting up a lexical variable to store the Stream so that the Timer's "on_expire" closure can call "close" on it, the parent/child relationship between the two Notifier objects is used. At the time the Timer "on_expire" closure is invoked, it will have been added as a child notifier of the Stream; this means the Timer's "parent" method will return the Stream Notifier. This enables it to call "close" without needing to capture a lexical variable, which would create a cyclic reference. Fixed-Delay Repeating Timer The "on_expire" event fires a fixed delay after the "start" method has begun the countdown. The "start" method can be invoked again at some point during the "on_expire" handling code, to create a timer that invokes its code regularly a fixed delay after the previous invocation has finished. This creates an arrangement similar to an IO::Async::Timer::Periodic, except that it will wait until the previous invocation has indicated it is finished, before starting the countdown for the next call. my $timer = IO::Async::Timer::Countdown->new( delay => 60, on_expire => sub { my $self = shift; start_some_operation( on_complete => sub { $self->start }, ); }, ); $timer->start; $loop->add( $timer ); This example invokes the "start_some_operation" function 60 seconds after the previous iteration has indicated it has finished. AUTHOR
Paul Evans <leonerd@leonerd.org.uk> perl v5.14.2 2012-10-24 IO::Async::Timer::Countdown(3pm)
All times are GMT -4. The time now is 09:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy