Search results

This is absolutely correct. A bug would get opened against bugs@ and triaged/assigned as needed.

What happened? It's always helpful to know just what lead to the thread being marked solved and it could benefit someone searching for the same error message in the future.

I've assigned it to freebsd-virtualization@FreeBSD.org where it belongs and will hopefully get some extra attention.

Oops! Edited! Thank you talsamon.

The interactive option may be helpful. EDIT: Example: poudriere bulk -i -t -j 10amd64 shells/bash

I would have to check the OpenVPN documentation on this but I believe pushing routes as the configuration shows won't work when you do a static point to point configuration like this. If you want the client to accept routes you would need to use the client key word in your configuration. If...

The static IPs should ensure the name lookup for the NFS server's hostname works. At the moment I am out of solid ideas on what this could be.

I highlighted the words I like to see. More folks throwing in quality assistance is what we need and not forks that will stagnate. Start learning. Dig into a problem that concerns you and contribute back a quality fix one issue at a time.

The maintainer updated it in https://svnweb.FreeBSD.org/changeset/ports/400111. If everything checks out I would appreciate it if you can make the thread solved ("Thread tools" at the top right, "edit thread", add "solved").

Greetings, Well, this may likely be fixed in the latest version of FreeNAS. FreeNAS 9.1 and FreeBSD 9.1 are no longer supported and Topics about unsupported FreeBSD versions thread is applicable both from the security side as well as the side that the bug may already be fixed. Secondly, while...

The port has no maintainer so if anybody can work through the Linuxisms and get it to work I would be glad to test and commit the update. Bonus points if you assign yourself as the maintainer in the process. Fear not, the Porter's Handbook...

Did that cover what you are looking for? A pointer to the thread and "solved" tag (Thread tools at the top right, "edit thread", and add solved) would be very helpful to the next person searching for help.

Helpful hint: file /bin/sh will quickly tell you what major release and OSVERSION binaries are installed.

Can you try out the patch I submitted in 203970? Instructions: pkg delete tcpflow fetch 'https://bugs.freebsd.org/bugzilla/attachment.cgi?id=162373' -o /tmp/tcpflow-1.4.5.patch cd /usr/ports/net/tcpflow patch -E < /tmp/tcpflow-1.4.5.patch make install If that works, positive feedback in the PR...

Based off compiling on 10.1 and running on an old version, a reminder that that old version (I'm guessing 10.0-RELEASE based off the context) is likely unsupported. Please do upgrade to a supported release. https://forums.FreeBSD.org/threads/topics-about-unsupported-freebsd-versions.40469/

That sounds like a bug. Is there anything related in https://bugs.FreeBSD.org/bugzilla/? Searching for auditd should be sufficient.

Concurred, which is why I just wanted to prefix the discussion with the helpful reminder to make responsible use of the knowledge gained and not get in the way of the conversation. Please carry on.

Ok. Thanks for the information. What I was looking for is if you were running DNS software on the local machine that the DNS software is started before /etc/rc.d/mountcritremote executes. In this case, that shouldn't be an issue. However I think I'm a bit lost on one piece since the thread...

There's no FreeBSD Forum rule that covers this and this is the off topic forum. With that said please apply common sense here. I would speculate that there are few if any lawyers who happen to use the forums and the likelihood of them being licensed to practice law where you live is small...

Can you share your configuration changes from the default and simple script you used? That would be incredibly useful to someone trying to solve the same problem in the future. If you add that, I would appreciate it if you mark this as solved as well ("Thread tools" at the top, "Edit Thread"...