Using wildcards in csf.pignore

Post Reply
MervRenton
Junior Member
Posts: 3
Joined: 30 Oct 2016, 10:16

Using wildcards in csf.pignore

Post by MervRenton »

Our CS&F works well but we are getting "Excessive resource usage" warnings that I can't see how to stop using csf.pignore.
And I can't see a solution in the forums.

Our developer uses the Visual Studio Code remote extension and the executable link varies for each hosting account e.g:
Executable: /home/murrayheatingand/.vscode-server/bin/7f6ab5485bbc008386c4386d08766667e155244e/node
Executable: /home/rsnethostingnet/.vscode-server/bin/7f6ab5485bbc008386c4386d08766667e155244e/node
Executable: /home/virginianurseryc/.vscode-server/bin/83bd43bc519d15e50c4272c6cf5c1479df196a4d/node
and so on ...

I tried adding a line to csf.pignore
exe:/home/*/.vscode-server/bin/83bd43bc519d15e50c4272c6cf5c1479df196a4d/node
but it still complains.

How do I wildcard this ignore please?

Thanks,

Merv
Sergio
Junior Member
Posts: 1685
Joined: 12 Dec 2006, 14:56

Re: Using wildcards in csf.pignore

Post by Sergio »

Merv, you should do what the instructions says in pignore, it shows:
Or, perl regular expression matching (regex):
#
# pexe:/full/path/to/file as a perl regex[*]
#
# [*]You must remember to escape characters correctly when using regex's, e.g.:
# pexe:/home/.*/public_html/cgi-bin/script\.cgi
So according to this, you could add a line like this one:
pexe:/home/.*/\.vscode-server/bin/.*/node

Sergio
Post Reply