yes. i uncommented the daytime tcp line, did a 'kill -HUP 239' and the
script worked.
i didn't find 'killall' on my system. and 'kill -HUP inetd' didn't work. i
had to use the pid of inetd.
Thanks. i learning am.
On Thursday, March 14, 2002, at 01:46 PM, Tim Rayner wrote:
> Incidentally, to get a service such as 'daytime' to run, you can edit the
> /etc/inetd.conf file to remove the leading remark # characters from the
> lines referring to the service of interest. There are two lines in the
> case of daytime; I don't know whether both are actually required.
> Probably not,
> on reflection. Anyway, you should then issue the command 'killall -HUP
> inetd' to restart the inetd server daemon, and you should be set.
>
> Both these activities require root/admin privileges, of course.
>
> Tim
>
> On Thursday, March 14, 2002, at 09:09 pm, Iago wrote:
>
>> Just because something's in services, doesn't mean it's running.
>> Services indicates "names" for port numbers, e.g., "13 is the daytime
>> port".
>>
>> Observe:
>>
>> iago@localhost:~% grep daytime /etc/services
>> daytime 13/tcp
>> daytime 13/udp
>>
>> iago@localhost:~% telnet localhost 13
>> Trying 127.0.0.1...
>> telnet: Unable to connect to remote host: Connection refused
>>
>> Can't connect to port 13 ... therefore, perl shouldn't be able to
>> either.
>>
>> On Thu, 14 Mar 2002, bob ackerman wrote:
>>
>>> perlipc doc has sample for doing a socket:
>>>
>>> use IO::Socket;
>>> $remote = IO::Socket::INET->new(
>>> Proto => "tcp",
>>> PeerAddr => "localhost",
>>> PeerPort => "daytime(13)",
>>> )
>>> or die "cannot connect to daytime port at
>>> localhost";
>>> while ( <$remote> ) { print }
>>>
>>> but it dies for me.
>>> i see 'daytime' in /etc/services at port 13.
>>> osx 10.1.3
>>> perl 5.6.1
>>
>> --
>> Fred Hicks <[EMAIL PROTECTED]>
>
