search for: base_dir

Hi all, I''d like to specify a base_directory and a list of directories (as variables that may be pulled via hiera later) that will be created under that base directory. base_dir = "/home/base" bars = ["a", "b", "c"] bars will be used to create the folders under base and also part of the infor...

I checked out LLVM and configured like this: ./configure --prefix=/home/regehr --enable-optimized then built and installed it. Then, checked out the frontend, configured like this: ../configure --prefix=/home/regehr --enable-languages=c,c++ \ --enable-llvm=/home/regehr/z/llvm but when I try to build I get configure: error: You must specify valid path to your LLVM tree with

Hello, today I run the command "doveadm auth cache flush" for the first time. # doveadm auth cache flush doveadm(root): Error: userdb lookup: connect(/var/run/dovecotauth-master) failed: No such file or directory 0 cache entries flushed # base_dir was the only item contain 'run' and it did not end with a / So I tried to set base_dir to /var/run/dovecot/ and could now rerun "doveadm auth cache flush" without problems. I compile dovecot from source and found --with-rundir=/var/run/dovecot as an option to configure. I chang...

.../src/master/master-settings.c: #define SSL_PARAMETERS_PERM_PATH PKG_STATEDIR"/"SSL_PARAMETERS_FILENAME This can lead to problems when you're running multiple instances on one machine. Apart from that, it would be very useful if wasn't hard- coded like that. Maybe it could be in base_dir or have a configuration option of its own? -- Leo Baltus, internetbeheerder /\ NPO ICT Internet Services /NPO/\ Sumatralaan 45, 1217 GP Hilversum, Filmcentrum, west \ /\/ beheer at omroep.nl, 035-6773555 \/

Hi I first let base_dir = with it's default value of /var/dovecot. I changed my mind and now I have doveconf -n # 2.1.17: /etc/dovecot/dovecot.conf # OS: OpenBSD 5.4 amd64 ffs base_dir = /var/run/dovecot/ After a few days, imap clients couldn't login. Here the problem Dec 04 17:03:16 imap-login: Fatal: Corrupt...

...riable:\n\nexport LIBGUESTFS_BACKEND=direct\n\nand then rerun the virt-v2v command.") ) diff --git a/v2v/input_ova.ml b/v2v/input_ova.ml index cd26160..f2dc28b 100644 --- a/v2v/input_ova.ml +++ b/v2v/input_ova.ml @@ -26,7 +26,7 @@ open Utils class input_ova ova = let tmpdir = - let base_dir = (new Guestfs.guestfs ())#get_cachedir () in + let base_dir = (open_guestfs ())#get_cachedir () in let t = Mkdtemp.temp_dir ~base_dir "ova." "" in rmdir_on_exit t; t in diff --git a/v2v/output_glance.ml b/v2v/output_glance.ml index e775229..ddcd771 100644 ---...

...tory PKG_STATEDIR (typically /var/lib/dovecot) is hard-coded as the location of things like the ssl-parameters.dat file and the replicator database. Replace all these uses of PKG_STATEDIR with a state_dir setting which defaults to PKG_STATEDIR but can be overridden in dovecot.conf, in the same way base_dir can be used to override PKG_RUNDIR. Signed-off-by: <chris at arachsys.com> --- src/config/Makefile.am | 1 - src/doveadm/doveadm-instance.c | 10 ++++------ src/doveadm/doveadm-mount.c | 3 +-- src/doveadm/doveadm-setting...

I can also confirm this, on my own mail server since upgrading to beta1. Dovecot always makes the base_dir world-writable on startup. ----- Forwarded message from Oleg Safiullin <form@pdp-11.org.ru> ----- Date: Fri, 20 Jan 2006 07:09:17 +0600 From: Oleg Safiullin <form@pdp-11.org.ru> To: brad@openbsd.org Subject: dovecot 1.0beta1 Hi. After update dovecot to 1.0beta1 some strange thing ha...

...r. These servers will also have a shared NFS backend. I have read on the site that I will need to configure director since I am using NFS. I have read through all of the documentation on director but still need a little guidance to get things up and running. One of the questions I have is about the base_dir on the Multiple Invocations section of the wiki. It states that I will need to change the bas_dir to the new run directory, not sure what needs to happen here, can anyone help me out?

I am having problems with dovecot regarding base_dir: I have :: base_dir = /opt/dovecot2/var/run/ For some reason, I have to set permissions to(chmod -R 1777 /opt/dovecot2/var/) for dovecot to run properly, but when I start dovecot, I see this: [root at gw] /opt/dovecot2/etc/dovecot# less /var/log/dovecot/dovecot.log Oct 21 16:15:27 master: Warnin...

...%s" (quote filename) (quote new_filename) in diff --git a/v2v/input_vmx.ml b/v2v/input_vmx.ml index f1d143e97..7a7647e53 100644 --- a/v2v/input_vmx.ml +++ b/v2v/input_vmx.ml @@ -389,8 +389,7 @@ and find_nics vmx = class input_vmx input_password input_transport arg = let tmpdir = - let base_dir = (open_guestfs ())#get_cachedir () in - let t = Mkdtemp.temp_dir ~base_dir "vmx." in + let t = Mkdtemp.temp_dir "vmx." in rmdir_on_exit t; t in object diff --git a/v2v/nbdkit.ml b/v2v/nbdkit.ml index 65317f9b9..06b240b54 100644 --- a/v2v/nbdkit.ml +++ b/v2v/nbd...

...ry where we place the socket and PID file. *) + (* Create a temporary directory where we place the socket and PID file. + * Use the libguestfs socket directory, so it is more likely the full path + * of the UNIX sockets will fit in the (limited) socket pathname. + *) let tmpdir = - let base_dir = (open_guestfs ())#get_cachedir () in + let base_dir = (open_guestfs ())#get_sockdir () in let t = Mkdtemp.temp_dir ~base_dir "v2vnbdkit." in (* tmpdir must be readable (but not writable) by "other" so that * qemu can open the sockets. -- 2.25.1

Hi, I would like to disallow dovecot to read its base_dir (mode 0310). This is currently not possible, because settings_verify() in src/master/master-settings.c will "fix" the directory mode to 0750. The following patch for 1.0rc15 ignores the read bit (0444) when checking the directory permissions. Max -------------- next part --------------...

Evening all, I'm running into an issue with lmtp trying to store user mail in 'base_dir' ( same as this ( http://www.dovecot.org/list/dovecot/2011-January/056736.html )) however I'm just using PAM for auth. I've tried with chroot, without chroot and 'chroot'ing lmtp directly in ' service lmtp { } ' which just lead to lots more errors. I've not inc...

...then rerun the virt-v2v command.") > ) > diff --git a/v2v/input_ova.ml b/v2v/input_ova.ml > index cd26160..f2dc28b 100644 > --- a/v2v/input_ova.ml > +++ b/v2v/input_ova.ml > @@ -26,7 +26,7 @@ open Utils > > class input_ova ova = > let tmpdir = > - let base_dir = (new Guestfs.guestfs ())#get_cachedir () in > + let base_dir = (open_guestfs ())#get_cachedir () in > let t = Mkdtemp.temp_dir ~base_dir "ova." "" in > rmdir_on_exit t; > t in > diff --git a/v2v/output_glance.ml b/v2v/output_glance.ml > inde...

...ust for your Information: I replaced all real data with placeholders, like the IP Address of my Server with MY_IP. Also i removed some absolutely non relevant lines from the configuration output (like settings for logging) This is my localhost config-output: # 1.1.2: /opt/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot protocols: pop3 imap listen(default): 127.0.0.1:143 listen(imap): 127.0.0.1:143 listen(pop3): 127.0.0.1:110 ssl_disable: yes login_dir: /var/run/dovecot/login login_executable(default): /opt/dovecot/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot/libexec/dovecot/im...

...ordkap dovecot: lda: Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) failed: Connection refused May 6 18:37:59 nordkap dovecot: lda: Fatal: Internal error occurred. Refer to server log for more information. >> For me it looks odd because the auth-userdb is defined as << base_dir = /usr/local/var/run/dovecot/ service auth { unix_listener auth-userdb { mode = 0777 user = vmail group = vmail } .... >> The rights on the file should be correct according to the config above << ls -al /usr/local/var/run/dovecot/auth-userdb srwxrwxrwx 1 vmail vma...

...wn below, even if I adjust the right line to add " && chmod 644", the actual resulting file still remains at 0600 ?!? #!/bin/bash # Usage: imapsieve_copy <email> <spam|ham> MSG_USER="$1" MSG_TYPE="$2" RUN_UUID=$(cat /proc/sys/kernel/random/uuid) BASE_DIR="/foo/bar" TARGET_DIR="${BASE_DIR}/${MSG_TYPE}" TARGET_FILE="${TARGET_DIR}/${RUN_UUID}" cat > "${TARGET_FILE}" < /dev/stdin && pigz -9 "${TARGET_FILE}"

I run dovecot 1.2.6, before last update I had 1.2.2. on Debian Lenny. I noticed that my config directory /etc/dovecot is filled up with hundreds of old auth-worker.12345 sockets. I guess they should have been cleaned up, is there a misconfiguration? When I remember right, this did not happen with dovecot 1.1.

...d configuration in /etc/dovecot.conf I've put the default dovecot.conf in place and still get the same thing. I've tried removing the /var/run/dovecot folder and letting it re-create it with no success. It creates the /var/run/dovecot folder but that is all. I've tried setting the base_dir to /tmp/dovecot to test and get the exact same error. I'm at a loss as are many other people so am hoping someone here might be able to help!