search for: hosty

It's not. In fact it's explicitly telling you that it's *not* forwarding. On 22 December 2015 at 15:55, Florent B <florent at coppint.com> wrote: > Hi, > > I have a lot of messages like this in my Tinc 1.1-git log : > > Sending packet from host5 (MYSELF port 655) to host4 (192.168.0.4 port > 655) via host4 (192.168.0.4 port 655) (UDP) > > Is it expected ?

Gang, ???? I run several KVM host machines.? Due to updates, maintenance, and unexpected reboots sometime host machines are restarted.? I can easily envision a scenario where HostX needs some critical packages updated or is acting up.? I migrate guest0, guest1, guest2 etc. from HostX to HostY.? Then, in either a planned (i.e. scheduled maintenance) or unplanned (i.e. unplanned reboot) event reboots HostX. Unfortunately guest0, guest1 and guest2 are all set to autostart on HostX but they're currently running on HostY when HostX boots.... etc etc etc ??? Is anyone using effective pa...

I am using procmail with deliver as recommended on the wiki to send mail snagged by SpamAssassin straight to a spam folder. It seemed to be working fine, but now I'm finding messages like this: Sep 17 12:13:47 hosty deliver(whoey): write() failed with mbox file /var/mail/whoey: File too large I don't think this is a setrlimit problem -- the host operating system is OpenBSD 4.0. My dovecot version is 1.0.13. Is there a maximum size used by deliver? Or is this a procmail problem? It looks like the message i...

...the error: "The security descriptor structure is invalid." I think this is because Samba is translating all the unix users to samba-server-local accounts, instead of mapping them to their matching domain accounts; i.e. my domain name is "DOMAINX", my samba server name is "HOSTY", when I mount the samba share on a windows box in the domain, right click and examine properties, I see "HOSTY\username" for all the permissions instead of seeing "DOMAINX\username". Is there any way to get this to work the way I want? --Ross

Hello all, I've run into an issue while migrating a client's Samba PDC from Debian 3.x to OpenSuSE 10.3, have been beating my head against it for over a week, and am now turning to the mailing list for help. We're running Samba 3.0.26a-3-1478-SUSE-SL10.3 authenticating against OpenLDAP 2.3.37. Integration of Samba and OpenLDAP works, and importing the 2000+ existing user accounts