Re: I nuked script.pm. Now postgres don't want to talk to me

in reply to I nuked strict.pm. Now postgres don't want to talk to me

Permission denied sounds like you messed up the permissions of strict.pm (should be -rw-r--r-- = 0644) or of one of the directories leading there (should be drwxr-xr-x = 0755).

How old is your last verifed backup? ;-)

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

Comment on Re: I nuked script.pm. Now postgres don't want to talk to me Select or Download Code

Replies are listed 'Best First'.
Re^2: I nuked script.pm. Now postgres don't want to talk to me by pvaldes (Chaplain) on Apr 12, 2017 at 15:29 UTC
Yes and could be worse. I found a file named strict.pm in /usr/lib/x86_64-linux-gnu/perl-base/ but not in the other directory. It seems that perl is looking in the wrong place. Maybe I had lost some links? Apt remove perl && apt install --reinstall perl didn't worked. Lets keep breaking things... Updated name of the module strict	[reply]

In Section Seekers of Perl Wisdom