Re: clamav-server configuration

2022-09-12 Thread Lenore Horner
Thanks Steve. The problem turned out to be that I had run open -a Automator ~/Library/Services/ClamavScanIt.workflow && osascript -e 'quit app "Automator"' from someplace other than my home directory. The copy command worked, but the workflow didn't. I think port commands do the same thing

Re: clamav-server configuration

2022-09-10 Thread Eckard Brauer
just for being complete, you could even leave the ~ in "cd ~", as in Unix shells (cd is usually a shell builtin) the cd command without any argument changes to the user's home directory, e.g. # cd ~ is equivalent to simply # cd > Thanks I’m the author. > > It appears that this is unrelated

Re: clamav-server configuration

2022-09-10 Thread Steven Smith
Thanks I’m the author. It appears that this is unrelated to the port and that there’s some issue with your home directory or account setup. In Unix, the path ‘~’ is a synonym refers to your home directory, typically ‘/Users/MyUserName’, and you definitely should be able to copy stuff there.

Re: clamav-server configuration

2022-09-09 Thread Ryan Schmidt
On Aug 28, 2022, at 10:22, Lenore Horner wrote: > The file /Users/MyUserName/ does not exist. Please file a bug report in the issue tracker so that the port's maintainer can look into the problem.

clamav-server configuration

2022-08-28 Thread Lenore Horner
Clamav-server has a really nice set of notes at the end about how to set it up. Thank you to the folks who set that up. I was following those instructions and got to the part > Clamav Scan-On-Demand is performed with the command: > > /opt/local/bin/ClamavScanIt.sh file1