search for: persimmons

aideen@persimmon.co.uk wrote: > > Hi, > > We've got some Java projects that are being developed on both Unix and > NT and we're struggling with JBuilder 2.0 and its "File has been > externally updated, reload buffers?" messages. Has anyone found a fix? > Is it a bug in JBuilder? i.e should I save my hair and not spend any > more time investigating/trying

...AP(testm2): access() failed with mbox file /var/mail/testm2: No such file or directory Jul 31 16:32:32 newnewton dovecot: IMAP(testm2): stat() failed with mbox file /var/mail/testm2: No such file or directory Jul 31 16:32:32 newnewton dovecot: IMAP(testm2): Connection closed ---------------- My persimmons on /var/mail (which is a symlink to /var/spool/mail) : drwxrwxr-x 2 root mail 4096 Jul 31 16:32 mail I have tried adding the mail group as mail_privileged_group, the output of dovecot -n : -------------------- # 1.0.7: /etc/dovecot.conf login_dir: /var/run/dovecot/login login_executable(default)...

Almost any distro will do, since 2.6 kenels are bleeding edge you might have to spend more time getting everything working, and in most cases you are best served by determining which distro your hardware manufacturer supports, Dell typically supports only redhat, HP supports suse on many boxes. While there are workarounds, having the hardware manufacturer deal with driver issues is a bonus.

Hi, We've recently upgraded to samba-1.9.18p10 and I'm a bit worried about using oplocks on shares that contain CVS repositories. Files are edited on NT and updates checked into cvs using the NT CVS client talking to a Unix CVS server. Is it safe to use oplocks in this case? If not - should I separate the CVS subtree into a completely separate share (or sub-share?) or is it possible

Hi, We've got some Java projects that are being developed on both Unix and NT and we're struggling with JBuilder 2.0 and its "File has been externally updated, reload buffers?" messages. Has anyone found a fix? Is it a bug in JBuilder? i.e should I save my hair and not spend any more time investigating/trying to fix this problem? More info: Our NT machines access files from