Hi all,
I can't believe that I can't find the answer to this one. I have a perl script
which is called by xinetd.
I want that perl script to be able to detect the remote IP address of the
caller.
I presumed that it would be an environment variable but I could be wrong. I've
found reference
On Thu, May 28, 2020 at 04:46:34PM +0100, Gary Stainburn wrote:
>
> Hi all,
>
> I can't believe that I can't find the answer to this one. I have a
> perl script which is called by xinetd.
>
> I want that perl script to be able to detect the remote IP address
> of the caller.
>
> I presumed th
> Hi all,
>
> I can't believe that I can't find the answer to this one. I have a perl
> script which is called by xinetd.
>
> I want that perl script to be able to detect the remote IP address of the
> caller.
>
> I presumed that it would be an environment variable but I could be wrong.
> I've fou
On 5/28/2020 8:55 AM, Jonathan Billings wrote:
I don't believe that xinetd tells the underlying processes anything
about IPs, since xinetd handles the network connection and as far as
the process is concerned, it's just filehandles.
Isn't the filehandle just a socket? So can't you use Perl's so
In article <202005281646.34790.gary.stainb...@ringways.co.uk>,
Gary Stainburn wrote:
> Hi all,
>
> I can't believe that I can't find the answer to this one. I have a perl
> script which is called by xinetd.
>
> I want that perl script to be able to detect the remote IP address of the
> caller
On Thursday 28 May 2020 18:12:55 Tony Mountifield wrote:
> In article <202005281646.34790.gary.stainb...@ringways.co.uk>,
> Works for me. Here are my details:
>
Thanks for this Tony. This is exactly what I had expected to happen. I
subsitiuted your server for mine and got exactly the same resul
This is CentOS-6x.
I have cloned the HDD of a CentOS-6 system. I booted a host with that drive
and received the following error:
checking filesystems
/dev/mapper/vg_voinet01-lv_root: clean, 128491/4096000 files, 1554114/16304000
blocks
/dev/sda1: clean, 47/120016 files, 80115/512000 blocks
/d
>
> I ran mke2fs to locate the backup superblocks:
>
> mke2fs -n /dev/mapper/vg_voinet01-lv_log
That will only tell you what mke2fs would do on that machine. I don't
know if it will be the same on every machine. You should probably run
dumpe2fs /dev/mapper/vg_voinet01-lv_log | grep superbl
On 5/28/20 1:33 PM, James B. Byrne via CentOS wrote:
/dev/mapper/vg_voinet01-lv_log
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2 filesystem
(and not swap or ufs or something else), then the superblock is cor
I will check with firewall-cmd.
Regarding hardware problem I have doubt as we use VMWare (but I keep in a
corner of my mind).At this moment, we have compiled kernel and have installed
it and have tried 4 restore passed.We need to do more tests and understand why
4 restores passed.
Thanks
Thomas
10 matches
Mail list logo