Vim: Caught deadly signal HUP
Thiagu Janakiraman
I'm getting the below error in our Dev environment whenever I open a file using vim/vi editor.
Vim: Caught deadly signal HUP
Vim: Finished.
Hangup
Can you please help me to fix this issue?
Thanks & Best Regards,
Thiagu
Christian Brabandt
On Di, 28 Jun 2016, Thiagu Janakiraman wrote:
> Hi,
>
> I'm getting the below error in our Dev environment whenever I open a file using vim/vi editor.
>
> Vim: Caught deadly signal HUP
>
> Vim: Finished.
> Hangup
>
> Can you please help me to fix this issue?
Second, you could try with the -u NONE -N -i NONE switch
to rule out plugins or settings. Third mention your system
Best,
Christian
--
Es ist mir völlig egal, was es wird. Hauptsache, er ist gesund.
-- Mehmet Scholl (als werdender Vater)
Thiagu Janakiraman
Thanks for responding to my query. Appreciate it.
Please find the details that you asked for.
1. VIM Version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 24 2016 02:35:54)
Included patches: 1-1952
2. Tried with these options (-u NONE -N -i NONE switch). Not sure if I'm doing it right. But still getting the signal HUP error. Basically, the system was working fine and not sure why we are receiving this SIGHUP error.
$ vi -u NONE -N -i NONE test.pl
Vim: Caught deadly signal HUP
Vim: Finished.
Hangup
$
3. Please find our system version.
$ uname -a
Linux hostname.xxx.com 2.6.18-407.el5 #1 SMP Wed Nov 11 08:12:41 EST 2015 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.11 (Tikanga)
Thanks for your help on this.
Thanks & Best Regards,
Thiagu
Thiagu Janakiraman
Thanks for responding to my query. Appreciate it.
Please find the details that you asked for.
1. VIM Version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 24 2016 02:35:54)
Included patches: 1-1952
2. Tried with these options (-u NONE -N -i NONE switch). Not sure if I'm doing it right. But still getting the signal HUP error. Basically, the system was working fine and not sure why we are receiving this SIGHUP error.
$ vi -u NONE -N -i NONE test.pl
Vim: Caught deadly signal HUP
Vim: Finished.
Hangup
$
3. Please find our system version.
$ uname -a
Linux hostname.xxx.com 2.6.18-407.el5 #1 SMP Wed Nov 11 08:12:41 EST 2015 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.11 (Tikanga)
Thanks for your help on this.
Thanks & Best Regards,
Thiagu
Tony Mechelynck
[...]
>
> $ uname -a
> Linux hostname.xxx.com 2.6.18-407.el5 #1 SMP Wed Nov 11 08:12:41 EST 2015 x86_64 x86_64 x86_64 GNU/Linux
>
>
> $ cat /etc/redhat-release
> Red Hat Enterprise Linux Server release 5.11 (Tikanga)
According to https://en.wikipedia.org/wiki/Red_Hat_Enterprise_Linux ,
RHEL 5.11 was released 2014-09-16 and RHEL 5 Extended Lifecycle
support will EOL 2020-11-30 together with RHEL 6 Production 3 phase
(only security and important fixes, hardly any support for new
drivers). Extended Lifecycle is listed as "N/A" for RHEL 6 and later.
The same source says that RHEL 6 has come and gone and that the
current full-support "stable" release is RHEL 7.2 released on
2015-11-19 with kernel 3.10.0-327. It wil have full support until Q4
2019, half-full (Production 2) support until Q4 2020 and will EOL on
2024-06-30.
This to put users of other Linux distributions in perspective, since
there is usually no correlation whatsoever between release numbers of
different Linux distributions outside of kernel versions (and even
that is shaky considering Red Hat's "kernel feature backporting"
policy); for instance, my own current distro is openSUSE Leap 42.1
with kernel 4.1.24-19; it is the latest openSUSE "stable" release
(released 2015-11-04, next release expected begin November 2016, 42.1
EOL expected Q2 2017), the previous one was called 13.2, just to show
how crazy Linux distro version numbering can sometimes be.
Best regards,
Tony.