On Thu, Sep 20, 2018 at 4:41 PM Ken M wrote:
> I am following -current and use openbox if it matters for my window
> manager.
> xscreensaver is started by openbox, anyway when I try to lock, well this
> is what
> I see:
>
> $ xscreensaver-command -lock
> xscreensaver-command: locking not
I am following -current and use openbox if it matters for my window manager.
xscreensaver is started by openbox, anyway when I try to lock, well this is what
I see:
$ xscreensaver-command -lock
xscreensaver-command: locking not enabled.
>From what I understand form the xscreensaver document that
my bad, I still don't have the real source IP in my logs (just the local ip
address of my server).
Any advice for a **real** transparent proxy ?
I think I found something working, I leave it here for others.
Any advice is still welcome.
By the way, I'm confused about the "transparent forward" directive in
relayd.conf. It doesn't seems to work at all and setting a transparent proxy is
not using this keyword.
/etc/relayd.conf :
0
C Slovenia
P SI
T Ljubljana
F irregular
O BSD User Group Slovenia
I
M b...@groups.io
U https://bsdug.wordpress.com
N *BSD
On Thu, Sep 20, 2018 at 06:54:07PM +0300, Lars Noodén wrote:
> On 9/20/18, Chris Bennett wrote:
> > I started manually to include Perl files one at a time to learn how
> > things work at home on -current. Then I copied everything in.
> > But why risk security for unused Perl?
>
> httpd(8)
On 9/20/18, Chris Bennett wrote:
> I started manually to include Perl files one at a time to learn how
> things work at home on -current. Then I copied everything in.
> But why risk security for unused Perl?
httpd(8) supports fastcgi so you can run outside the chroot and
communicate via a
I started manually to include Perl files one at a time to learn how
things work at home on -current. Then I copied everything in.
But why risk security for unused Perl?
I would like to eliminate the unused files and then use mtree to watch
and use that to inform me of any in particular that need
On 2018-09-20 09:13:42, Alexandre Ratchov wrote:
> On Wed, Sep 19, 2018 at 11:32:40PM +0200, michal.lyszc...@bofc.pl wrote:
> > Hello,
> >
> > I've stumbled upon a weird problem. Long story short, I try to open
> > fifo two times, once O_WRONLY and once O_RDONLY, both in separate
> > threads - but
On Wed, Sep 19, 2018 at 11:32:40PM +0200, michal.lyszc...@bofc.pl wrote:
> Hello,
>
> I've stumbled upon a weird problem. Long story short, I try to open
> fifo two times, once O_WRONLY and once O_RDONLY, both in separate
> threads - but on process. Unfortunately both threads are locked in
>
10 matches
Mail list logo