search for: solutuion

...for the whole keyboard, no input possibel. What's wrong with my Wine instalation? The debug output tells me about a language problem and the sound failure. I've read the help pages, but they just told me about problems with the different keyboard map files for other layouts, so there no solutuion for no working keyboards. What is wrong? -- mfg Holger Eichler

...auth users = anonymous When running rsync --daemon in one shell and rsync my-global-ip-address:: in another I receive the welcome message and the ftp module to which I should be able to log into. But when issuing this command rsync my-global-ip-address::ftp/* all I get is a hung shell. What is the solutuion to this problem? Could it be that some files are missing, or that some settings have not been set yet? This is in windows 2000. In linux I am not even able to receive the welcome message. I guess it is because the rsync daemon isn't running at all, even though I have tried to start it using rsy...

...AM, Oliver Welter wrote: > Guys, dovecot is open source - if you desire a feature that the upstream > programmer did not include, pay him a bounty to do so or send him a > patch to be included. Period. We can discuss and mightbe somebody will > fork if he is not willing to accept such a solutuion for any political > reason. > > I am really tired of reading this kind of complaints on OSS lists. ....and this is perhaps the second most predictable knee-jerk response. I am certainly capable of writing such a patch, but there is no point in expending the effort if it would not be...

On 03/01/2015 04:25 AM, Reindl Harald wrote: >> I wonder if there is an easy way to provide dovecot a flat text >> file of ipv4 #'s which should be ignored or dropped? >> >> I have accumulated 45,000+ IPs which routinely try dictionary >> and 12345678 password attempts. The file is too big to create >> firewall drops, and I don't want to compile with

...hing!) that I dislike about dovecot. > Guys, dovecot is open source - if you desire a feature that the upstream programmer did not include, pay him a bounty to do so or send him a patch to be included. Period. We can discuss and mightbe somebody will fork if he is not willing to accept such a solutuion for any political reason. I am really tired of reading this kind of complaints on OSS lists. To make this not a "troll only" posting - it might be an suitable approach to let dovecot listen on the lo interface and put a proxy software in front, that supports RBLs. Oliver -- Protect...

...r wrote: >> Guys, dovecot is open source - if you desire a feature that the upstream >> programmer did not include, pay him a bounty to do so or send him a >> patch to be included. Period. We can discuss and mightbe somebody will >> fork if he is not willing to accept such a solutuion for any political >> reason. >> >> I am really tired of reading this kind of complaints on OSS lists. > > ....and this is perhaps the second most predictable knee-jerk response. > > I am certainly capable of writing such a patch, but there is no point > in expendi...

Hi all, I've got a printserver working using cups/samba,ADS. I'm want to pass any jobs through a custom script which will do various things, including checking user quotas from a custom database (I know there are print quota solutuions out there that will fit in nicely with cups and samba, but I need to do this a different way due to some custom things we need to do) I've tried adding a line like 'print command = /path-to-script.pl`, to a test perl script which just logs some things to a file (with the intention of...

....cgi?id=90329 . I invite everybody who has an interest in this topic to take part in the discussion there. > Workarounds/solutions include: > > - disable certain optimizations -- works for now, but doesn't remove the root cause so seems generally fragile That looks like a short-term solutuion that could work (at least for x86_64 using the standard Unix ABI). And yes, it is fragile. And whatever other solution people come up with, it will still be fragile unless the caller and the callee agree. The root cause is that the Fortran LAPACK routines are called from C via an incompatible cal...

The point is that LAPACK uses characters as control arguments in multiple places and we don't write the LAPACK Fortran routines. It has long been known that general character strings was a portability issue but many (not just R people) have thought that length-one character were safe to pass as char* pointers. So "avoid" is not really an option if we want to use LAPACK functionality