similar to: DC testing observation and a question

I've been testing my user community's IMAP clients when I try to login and then transfer a big message from the inbox into a folder in an overquota folder directory. I am using native filesystem quotaing in AIXV5.3 with UWIMAP and comparing my results with what I see with Dovecot 1.0.0. (My Dovecot built without any plugins or quota extensions) Everything matches/works except for Mac

Don't know if anyone else uses Berkeley derived filesystem quota, but IBM's AIX does. A little over a week after migrating from UWIMAP to DC (with mbox format unchanged) everything is clean except for this one problem: When users go over quota, when they login the next time, the folder list is blank. You can imagine the panicked calls to the Helpdesk. If their quotas are raised or

A experienced sysadmin who's doing some guinea-pig use of DC just ran into the following situation: 1) He brings up SeaMonkey 2) About 30 minutes later, he's in the middle of some involved messaging, mistakenly hits the redX in the top right of the SeaMonkey window, knocking himself out of SeaMonkey. 3) He immediately reinvokes SeaMonkey, all appeared to be OK Viewed some e-mail and

My production imap is currently UWIMAP with mbox.. One of the problems commonly observed is mailbox lock loss, which happens when: a) a VIP has multiple secretaries accessing a single mailbox (actually, they are professional enough to have figured the realities of conflicting access and rarely have a problem), b) somebody leaving their machine on at home and coming in and firing up their work

I've probably done something dumb, but a quick search on Google, etc has turned up nothing I recognized as useful. I just installed dovecot on an OpenBSD 3.9 box. It is working fine with secure POP3 (after changing the config file to "mbox_write_locks = fcntl"). I also selected secure IMAP as a protocol, but it is proving to be more resistant to working. I am trying to connect

Hello all, I have two test beds running the exact same version of asterisk 1.2.7.1, latest of zaptel, libpri, etc.. Test bed #1 (Solaris 9,sparc ultra 5): This one is closer to a "production" machine, in that it is connected to a sip provider thru an iax2 connection and have an incoming DID configured. I can send and receive calls. Test bed #2 (Slackware Linux 10.2, AMD XP chip):

Everytime I add or remove some samba shares, I must restart smb service to take effect. Is there anyway to reconfig it without restart?

I saw the latest update announcements on the announce list, so I ran "yum check-update" and did not see seamonkey in the list. Which I guess makes sense, since it's a name change from mozilla. However, devhelp is in the list, and "yum update devhelp" pulls in seamonkey as a dependency. This seems like a sort of backdoor way to get seamonkey onto the system. Did these

rsync 2.5.0 still has a bug where it hangs under some circumstances. The hang is beyond my abilities to track down. I'll keep trying, though, but here are details in case they're of use to anyone else: - Code configured & built on Solaris 2.5.1. - Same binary run on Solaris 2.5.1 (client) and 2.8 (server). - Using rsh transport, but also fails with ssh - Does not fail with

CentOS Errata and Security Advisory 2007:0077 https://rhn.redhat.com/errata/RHSA-2007-0077.html The following updated files have been uploaded and are currently syncing to the mirrors: x86_64: devhelp-0.10-0.7.el4.x86_64.rpm devhelp-devel-0.10-0.7.el4.x86_64.rpm seamonkey-1.0.8-0.1.el4.centos.x86_64.rpm seamonkey-chat-1.0.8-0.1.el4.centos.x86_64.rpm

CentOS Errata and Security Advisory 2007:0077 https://rhn.redhat.com/errata/RHSA-2007-0077.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: devhelp-0.10-0.7.el4.i386.rpm devhelp-devel-0.10-0.7.el4.i386.rpm seamonkey-1.0.8-0.1.el4.centos.i386.rpm seamonkey-chat-1.0.8-0.1.el4.centos.i386.rpm seamonkey-devel-1.0.8-0.1.el4.centos.i386.rpm

CentOS Errata and Security Advisory 2007:0077 https://rhn.redhat.com/errata/RHSA-2007-0077.html The following updated files have been uploaded and are currently syncing to the mirrors: s390: updates/s390/RPMS/seamonkey-1.0.8-0.1.el4.centos.s390.rpm updates/s390/RPMS/seamonkey-chat-1.0.8-0.1.el4.centos.s390.rpm updates/s390/RPMS/seamonkey-devel-1.0.8-0.1.el4.centos.s390.rpm

I've been using the SeaMonkey built-in HTML editor from the epel repo for CentOS 6.7: $ repoquery -i seamonkey Name : seamonkey Version : 2.39 Release : 1.el6 Architecture: x86_64 Size : 127340745 Packager : Fedora Project Group : Applications/Internet URL : http://www.seamonkey-project.org Repository : epel Summary : Web browser, e-mail, news,

CentOS Errata and Security Advisory 2007:0077 https://rhn.redhat.com/errata/RHSA-2007-0077.html The following updated files have been uploaded and are currently syncing to the mirrors: files: updates/ia64/RPMS/seamonkey-1.0.8-0.1.el4.centos.ia64.rpm updates/ia64/RPMS/seamonkey-chat-1.0.8-0.1.el4.centos.ia64.rpm updates/ia64/RPMS/seamonkey-devel-1.0.8-0.1.el4.centos.ia64.rpm

Has anyone had any success in rebuilding seamonkey 2.0.4 for CentOS 5 (32-bit)? I'm currently running seamonkey-2.0-1 which I rebuilt last November. Sadly, I have no idea where the SRPM originated. I found seamonkey-2.0.4-1.fc12.src.rpm and seamonkey-2.0.4-1.fc12.src.rpm, downloaded and got to 0th base: [rj at madeleine Downloads]$ rpmbuild --rebuild

On 01/27/2016 04:59 PM, Clint Dilks wrote: > What is the result of > ldd /usr/lib64/seamonkey/seamonkey-bin # ldd /usr/lib64/seamonkey/seamonkey-bin linux-vdso.so.1 => (0x00007ffe525fc000) libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003d6b400000) libdl.so.2 => /lib64/libdl.so.2 (0x0000003d6bc00000) librt.so.1 => /lib64/librt.so.1 (0x0000003d6c000000) libstdc++.so.6

On 01/27/2016 04:17 PM, John R Pierce wrote: > is seamonkey .i686 or .x86_64 ? you might need to yum install > dbus-glib.i686 Thanks. $ rpm -aq seamonkey seamonkey-2.39-1.el6.x86_64 Double-check: $ file /usr/lib64/seamonkey/seamonkey-bin /usr/lib64/seamonkey/seamonkey-bin: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18,

On 01/27/2016 02:47 PM, Clint Dilks wrote: >> /usr/local/seamonkey/seamonkey-bin: error while loading shared libraries: >> libdbus-glib-1.so.2: cannot open shared object file: No such file or >> directory >> >> > Have you tried yum provides 'libdbus-glib-1.so.2'. I get a hit with > dbus-glib Thanks. Package dbus-glib-0.86-6.el6.x86_64 already

Hello! On May 28, I had a problem with pup and seamonkey. I was doing an update via pup and reading a page via seamonkey; seamonkey froze with a plain brown screen. I waited awhile, and then did the press-the-power-button-until-it-shuts-off. However, I don't know whether it was seamonkey or pup that actually caused the freeze, but apparently pup did not do its updating job correctly.

What happened to seamonkey? I thought firefox was retired in 4 and replaced by seamonkey. Imagine my surprise when 5 came with firefox. What's a guy to do? TIA Russel -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070422/84f76e3c/attachment-0004.html>