Sponsored Content
The Lounge What is on Your Mind? What are you listening to right now? Post 302085506 by Eronysis on Thursday 17th of August 2006 04:21:50 PM
Old 08-17-2006
Sugar's fille under easy listening Smilie
 

9 More Discussions You Might Find Interesting

1. IP Networking

port not listening..

Hi.. I am using HPux11.0 i want to know if server not listening to a tcp port what should we do to resolve the problem.... in /etc/services tcp port 7108/tcp is mentioned for some perticular application.. while starting that application error is coming could not establish listening address... (1 Reply)
Discussion started by: Prafulla
1 Replies

2. What is on Your Mind?

So... What are you listening to?

Hi guys, lets make this more interesting... I'm sure you listen to something when your working on a project or something... I know, I do, helps with concentration. Track: ±¯¸èÖ®Íõ (King of sad songs) Artist: -îǧ‹Ã Miriam Yeung Lovely forum BTW! :D (33 Replies)
Discussion started by: hype.it
33 Replies

3. UNIX for Dummies Questions & Answers

What prot is a process listening on?

Hi, Bit of a newbie question . . . How can I detrimine what TCP port a particular process is listening on? TIA. (2 Replies)
Discussion started by: Le Badger
2 Replies

4. SuSE

Apache2 No listening Sockets available

I installed Apache2 and Gadmin-Httpd on Suse after installation I got a error message no listening sockets available when start apache. Please advise, I check lot of forums but unable to find solution (4 Replies)
Discussion started by: real-chess
4 Replies

5. Red Hat

No process ID for listening ports

How can I have ports that are listening without processes being associated with them? root@ldv002 # netstat -ltnup Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0... (2 Replies)
Discussion started by: Padow
2 Replies

6. Ubuntu

Listening for textbox clicks

Hi everyone. Apologies if I am posting in the wrong area. I would like to find out a bit about how ubuntu/linux handles text boxes. In particular I would like to develop an application that launches another application (on screen keyboard) when any text box is clicked. The goal is to get... (4 Replies)
Discussion started by: Huss
4 Replies

7. AIX

Process running but not listening

Hello guys I am experiencing a very strange behavior on one of our AIX servers. We have an application with several processes that listen on several port numbers. Sometimes we receive complains that people cannot connect to the server on a specific port that is used by one the application... (6 Replies)
Discussion started by: abohmeed
6 Replies

8. Ubuntu

PID of listening ports

I ran 'sudo netstat -ntpl' and got the following without PID tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:38977 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:34253 ... (3 Replies)
Discussion started by: tt77
3 Replies

9. Shell Programming and Scripting

Is my Socket Free or Listening

Hi, bash-3.2$ uname -a Linux mymac 2.6.18-409.el5 #1 SMP Fri Feb 12 06:37:28 EST 2016 x86_64 x86_64 x86_64 GNU/Linux bash-3.2$ telnet 10.12.228.40 13900 Trying 10.12.228.40... telnet: connect to address 10.12.228.40: Connection refused bash-3.2$ telnet 10.12.228.40 23900 Trying... (2 Replies)
Discussion started by: mohtashims
2 Replies
MooseX::Has::Sugar(3pm) 				User Contributed Perl Documentation				   MooseX::Has::Sugar(3pm)

NAME
MooseX::Has::Sugar - Sugar Syntax for moose 'has' fields VERSION
version 0.05070420 SYNOPSIS
Moose "has" syntax is generally fine, but sometimes one gets bothered with the constant typing of string quotes for things. The MooseX::Types module exists and in many ways reduces the need for constant string creation. Primary Benefits at a Glance Reduced Typing in "has" declarations. The constant need to type "=>" and '' is fine for one-off cases, but the instant you have more than about 4 attributes it starts to get annoying. More compact declarations. Reduces much of the redundant typing in most cases, which makes your life easier, and makes it take up less visual space, which makes it faster to read. No String Worries Strings are often problematic, due to white-space etc. Noted that if you do happen to mess them up, Moose should at least warn you that you've done something daft. Using this alleviates that worry. Before this Module. Classical Moose has foo => ( isa => 'Str', is => 'ro', required => 1, ); has bar => ( isa => 'Str', is => 'rw' lazy_build => 1, ); Lazy Evil way to do it: PLEASE DO NOT DO THIS has qw( foo isa Str is ro required 1 ); has qw( bar isa Str is rw lazy_build 1 ); With this module ( and with MooseX::Types ) use MooseX::Types::Moose qw( Str ); use MooseX::Has::Sugar; has foo => ( isa => Str, ro, required, ); has bar => ( isa => Str, rw, lazy_build, ); Or even use MooseX::Types::Moose qw( Str ); use MooseX::Has::Sugar; has foo => ( isa => Str, ro, required, ); has bar => ( isa => Str, rw, lazy_build, ); Alternative Forms Basic "is" Expansion Only ( using ::Sugar::Minimal instead ) use MooseX::Types::Moose qw( Str ); use MooseX::Has::Sugar::Minimal; has foo => ( isa => Str, is => ro, required => 1, ); has bar => ( isa => Str, is => rw, lazy_build => 1, ); Attribute Expansions with Basic Expansions ( Combining parts of this and ::Sugar::Minimal ) use MooseX::Types::Moose qw( Str ); use MooseX::Has::Sugar::Minimal; use MooseX::Has::Sugar qw( :attrs ); has foo => ( isa => Str, is => ro, required, ); has bar => ( isa => Str, is => rw, lazy_build, ); EXPORT GROUPS
:default Since 0.0300, this exports all our syntax, the same as ":attrs :isattrs". Primarily because I found you generally want all the sugar, not just part of it. This also gets rid of that nasty exclusion logic. :isattrs This exports "ro", "rw" and "bare" as lists, so they behave as stand-alone attrs like "lazy" does. has foo => ( required, isa => 'Str', ro, ); NOTE: This option is incompatible with ::Sugar::Minimal : "CONFLICTS" :attrs This exports "lazy" , "lazy_build" and "required", "coerce", "weak_ref" and "auto_deref" as subs that assume positive. has foo => ( required, isa => 'Str', ); NOTE: This option is incompatible with MooseX::Types and Moose's Type Constraints Module : "CONFLICTS" :is DEPRECATED. See ::Sugar::Minimal for the same functionality :allattrs DEPRECATED, just use ":default" or do use MooseX::Has::Sugar; EXPORTED FUNCTIONS
bare returns "('is','bare')" ro returns "('is','ro')" rw returns "('is','rw')" required returns "('required',1)" lazy returns "('lazy',1)" lazy_build returns "('lazy_build',1)" weak_ref returns "('weak_ref',1)" coerce returns "('coerce',1)" WARNING: Conflict with MooseX::Types and Moose::Util::TypeConstraints, see "CONFLICTS". auto_deref returns "('auto_deref',1)" CONFLICTS
MooseX::Has::Sugar::Minimal MooseX::Has::Sugar::Saccharin This module is not intended to be used in conjunction with ::Sugar::Minimal or ::Sugar::Saccharin We export many of the same symbols and its just not very sensible. MooseX::Types Moose::Util::TypeConstraints due to exporting the "coerce" symbol, using us in the same scope as a call to use MooseX::Types .... or use Moose::Util::TypeConstraints will result in a symbol collision. We recommend using and creating proper type libraries instead, ( which will absolve you entirely of the need to use MooseX::Types and MooseX::Has::Sugar(::*)? in the same scope ) AUTHOR
Kent Fredric <kentnl at cpan.org> COPYRIGHT AND LICENSE
This software is copyright (c) 2012 by Kent Fredric. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. perl v5.14.2 2012-02-12 MooseX::Has::Sugar(3pm)
All times are GMT -4. The time now is 03:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy