search for: dangerus

...prefer. And now since I filed a bug and reported the crash and provided narrative and files and have seen 0 movement on the bug, I wonder why I wasted my time reporting it. If I was missing something I would hope at least a reply requesting more info or whatever would be forthcoming. Maybe Rodney Dangeruser "Don't get no respect"? ;) Well, at least "upstream". > > --keith Bill

On 2015-01-23, Warren Young <wyml at etr-usa.com> wrote: > On Jan 23, 2015, at 12:35 PM, Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: > >> I do prefer 3ware web RAID admin >> interface anything else (it more transparently prevents me from making >> fatal blunders - probably just me). > > No, not just you. tw_cli is needlessly confusing in its

On 05/08/2019 09:55, Patrik via samba wrote: > the dig is wrong as well, it adds an additional ip address, which i have > not request to use other interfaces: > root at server:/# dig p3x-dc.patrikx3.com > Patrik, I have told you what your problem is, refusing to accept that you have setup Bind9 incorrectly is no reason for opening a new thread. Just in case you missed it, or

...router-logs] path = /var/log-router read only = yes guest ok = yes writable = no browseable = yes force user = root follow symlinks = yes wide links = yes That is asking for problems, and again, wide links and follow symlinks are very dangerus to use. And especialy when you force user root. Your on debian buster. Enforce your logging to root:staff or root:adm Which is debian default on most logs, setup your logrotate for that also. And use the group(s) to allow access for the samba share. But thats what i would do. Ps, run my d...

...read only = yes > guest ok = yes > writable = no > browseable = yes > force user = root > follow symlinks = yes > wide links = yes > > That is asking for problems, and again, wide links and follow symlinks are > very dangerus to use. > And especialy when you force user root. > > Your on debian buster. > Enforce your logging to root:staff or root:adm > Which is debian default on most logs, setup your logrotate for that also. > And use the group(s) to allow access for the samba share. > > But thats...