similar to: libexecdir and localstatedir problem

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm using Dovecot 1.2.9. I configured it like this: % ./configure --prefix=/opt/rt --libdir=/opt/rt/lib \ --libexecdir=/opt/rt/lib [other args...] It compiled fine, but failed to install, because it tries to install a directory called <libdir>/dovecot/imap, and a file called <libexecdir>/dovecat/imap, which obviously

[See my comments below.] ----- Forwarded message from an x11-ssh-askpass customer ----- Date: Fri, 30 Mar 2001 16:34:28 -0800 Subject: x11-ssh-askpass 1.2.0 To: jmknoble at jmknoble.cx I just installed x11-ssh-askpass 1.2.0 on some systems, and ran into a couple of minor problems: OpenSSH 2.5.2p2 by default is looking for ssh-askpass in /usr/local/libexec, not /usr/local/libexec/openssh. It

On Saturday 19 March 2016 14:42:32 Andrew Bartlett wrote: > On Wed, 2016-03-16 at 20:33 +0000, Miguel Medalha wrote: > > > When building Samba 4.4.0rc and then doing an install to > > > /usr/local/samba, a directory "libexec" is being created which then > > > contains a "samba" directory with a single "smbspool_krb5_wrapper" > >

>>> When building Samba 4.4.0rc and then doing an install to >>> /usr/local/samba, a directory "libexec" is being created which then >>> contains a "samba" directory with a single "smbspool_krb5_wrapper" >>> file inside (/usr/local/samba/libexec/samba/ >>> smbspool_krb5_wrapper). This is not very clean, is it? >>>

Hello, I'm a bit afraid of users, the might slow down the server because of search requests to the imap-server on very large mailboxes. Even with a performant index, this could cause a lot of cpu and i/o-load. Is it possible to include the login-name in the imap process, so that a "ps ax" doesn't just give "imap", but e.g. "imap test at example.com"?

http://bugzilla.netfilter.org/show_bug.cgi?id=776 Summary: pkglibexecdir prevents building on debian unstable Product: ulogd Version: SVN (please provide timestamp) Platform: x86_64 OS/Version: Debian GNU/Linux Status: NEW Severity: normal Priority: P5 Component: ulogd AssignedTo: netfilter-buglog

Hello, today I accidentally created a subfolder "Trash" instead of INBOX.Trash. No error was given, the creation lead to the folder ".Trash". If I know this folder, I can also select it. But a "list * * " doesn't show the Trash folder. How could I ever find this folder by the imap-procotol if I don't know it's name? Is this the correct behaviour? Or

On Wed, 2016-03-16 at 20:33 +0000, Miguel Medalha wrote: > > When building Samba 4.4.0rc and then doing an install to > > /usr/local/samba, a directory "libexec" is being created which then > > contains a "samba" directory with a single "smbspool_krb5_wrapper" > > file inside (/usr/local/samba/libexec/samba/ > > smbspool_krb5_wrapper).

On Sat, 2016-03-19 at 12:41 +0100, Andreas Schneider wrote: > On Saturday 19 March 2016 14:42:32 Andrew Bartlett wrote: > > On Wed, 2016-03-16 at 20:33 +0000, Miguel Medalha wrote: > > > > When building Samba 4.4.0rc and then doing an install to > > > > /usr/local/samba, a directory "libexec" is being created which > > > > then > > >

https://bugzilla.mindrot.org/show_bug.cgi?id=3745 Bug ID: 3745 Summary: sshd does not read sshd-auth in the libexecdir directory Product: Portable OpenSSH Version: -current Hardware: amd64 OS: Linux Status: NEW Severity: critical Priority: P5 Component: sshd

On 20/03/16 18:57, Miguel Medalha wrote: > >>>> When building Samba 4.4.0rc and then doing an install to >>>> /usr/local/samba, a directory "libexec" is being created which then >>>> contains a "samba" directory with a single "smbspool_krb5_wrapper" >>>> file inside (/usr/local/samba/libexec/samba/ >>>>

On Sun, 2016-03-20 at 18:57 +0000, Miguel Medalha wrote: > >  > Thank you for writing the patch. > > Maybe I am being picky or (most probably) ignoring some valid > motive,  > but why does "smbspool_krb5_wrapper" need a "libexec" directory just > for  > itself? Was there something wrong with keeping this file in  > "/usr/local/samba/bin"

> I'm sorry, I missed the release with ths one. :-) That's okay, I did it during ./configure. > If you file a bug, it will make this a little harder to forget, and we > can get this sorted for the next release (not sure if we will move > binaries around during the release series). Ok. I will try to do that. On a related note, does sysvol really need to be in

> If you need a rationale, it could be not to put in the path things that > the admin or user should not directly execute. Yes, put in that way it makes perfect sense. Anyway, thanks for your patch. The thing is cleaner now.

Hi, When I run puppet agent --test --environment 42A, I have the following warning : Warning: Local environment: "42A" doesn''t match server specified node environment "production", switching agent to "production". ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and

I am trying to get a custom fact to sync. The fact is in a module. It will sync if I run puppet with "--pluginsync" but not otherwise. I have "pluginsync=true" in my puppet.conf. Shouldn''t the command line option and puppet.conf option have the same results? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group.

Hello All, I''m using the "Branch Testing" approach documented at https://reductivelabs.com/trac/puppet/wiki/BranchTesting and am seeing an issue with certificates. On all clients, I can run puppetd --masterport=8141 successfully but see the following error when I run against the default (8140) port: err: Could not retrieve configuration: Certificates were not trusted:

Hey guys, Relatively new to Puppet and I''m trying to setup tagmail to send all emails to me: at one point I''ll filter that down to errors and whatnot (based on tags) but for now I just want to get it working. Master Puppet server is setup with Passengers, all works well: /etc/puppet/puppet.conf [main] # The Puppet log directory. # The default value is

Hello All, I don''t seem to be able to get reports to display on the foreman interface. I copied extras/puppet/foreman/files/foreman-report.rb to / usr/lib/ruby/site_ruby/1.8/puppet/reportsforeman.rb, instead of /usr/ lib/ruby/1.8/puppet/reports/foreman.rb. Config: Centos5.4, Apache/ Passenger, Puppet 0.25.4. The reports are coming from the clients, because I can see them in

Hey guys, hope you don't mind this forward email, because I have been reading the 'flashpluginwrapper problem.' subject. The bug is in the linux_base, but nobody seem to check on this in the freebsd-ports. Looks like Brandon D. Valentine might needs to create a PR to get the better attention and keep the track. Cheers, Mezz >Summary: > >This began as a problem report