similar to: Weird boot loader

Hi, all, I know about the "foot shooting" prevention in geom(4) when trying to update the MBR of a mounted disk. I have a system with ad4 and ad6 mirrored and fdisk partitions residing on the mirror to be booted alterningly: hd30# gmirror status Name Status Components mirror/m0 COMPLETE ad4 ad6 hd30# mount /dev/mirror/m0s1a on / (ufs, local, read-only)

Hi, I'm having trouble rationalizing the behaviour described below. Is this a security-issue (bug) or a feature? - An unprivileged user 'bztest' with read-only access to /dev/ar0: %id uid=1004(bztest) gid=1004(test) groups=1004(test), 5(operator) %ls -l /dev/ar0 crw-r----- 1 root operator 4, 21 Nov 23 17:34 /dev/ar0 - Now, the device ar0 has the standard mbr installed: %cmp

I am syncing two Dovecot sites using the dsync function. I would like to be able to run some sort of periodic health check to confirm that dsync is (or is not) running properly between the two sites, and alert me if dsync is failing or lagging excessively. Does anyone know of a tool to do this? (If possible, something I can set up to run periodically in Nagios?) Thanks for any suggestions.

Hi, I wonder if the following (apparent) inconsistency is a bug or feature. Since scalars are simply vectors of length one I would think that a and a:a produce the same result. For example, > identical(4.01,4.01:4.01) [1] TRUE However, identical(4,4:4) [1] FALSE and > identical(4.0,4.0:4.0) [1] FALSE A closer look reveals that the colon operator produces objects

On September 5, Tom wrote: > In Shorewall 4.2, you can leave the ''loc:'' out of the DNAT- rule. I tried that just now (shorewall-perl 4.2.1), and I got an error: Checking... WARNING: Destination zone (172.29.0.29) ignored : /etc/shorewall/rules (line 38) ERROR: Unknown Host (0.0.0.0/0) : /etc/shorewall/rules (line 38) where 172.29.0.29 is the destination address on

I can't get replication to work in Dovecot 2.2.1. I'm getting the following error on the machine where I'm initiating the replication: richatwork dovecot: doveadm: Error: dsync-remote(richatwork): Error: dsync(local): Remote dsync doesn't use compatible protocol Both the local and remote servers are running identical versions of Dovecot (2.2.1), so I don't understand why I

Bringing up an old topic on a small technicality. In the help documentation on seq. Value: The result is of 'mode' '"integer"' if 'from' is (numerically equal to an) integer and 'by' is not specified. The arguement in seq specifying length also creates "double" which is not obvious in the wording, as "by" is not specified

Bringing up an old topic on a small technicality. In the help documentation on seq. Value: The result is of 'mode' '"integer"' if 'from' is (numerically equal to an) integer and 'by' is not specified. The arguement in seq specifying length also creates "double" which is not obvious in the wording, as "by" is not specified

I've got Dovecot 2.2r5 (Ubuntu package version 2:2.2.0~rc5-0~auto+1 from the "testing-auto/dovecot-2.2" repository on xi.rename-it.nl) running on a brand-new Ubuntu 12.04.2 server. I'm trying to configure Dovecot (using the "mdbox" mailbox format) to allow folders to contain both messages and sub-folders. However, it's not working consistently. I need to have

Hi, I just converted all my hard disk filesystems from ext2 to ext3. This worked perfectly fine for all non-root fs, but I am having trouble converting the root fs, too. Here's what I did: 1. rebuilt my kernel (2.4.20, x86) with ext3 support linked in statically - no module. 2. Added a journal file to my root fs using 'tune2fs -j'. 3. Added 'rootfstype=ext3' to the

I'm considering converting a Cyrus system (managing my family's e-mail) to Dovecot. I'm trying Dovecot 1.1.15 on an Ubuntu 9.04 (2.6.28-11-server) system. My production server is currently running Cyrus 2.3.14. Since I have a huge number of folders and subfolders, I need to use LAYOUT=fs. However, it's not working consistently. I tried setting up a test account in Thunderbird

I would like to customize our store-bought, bootable FreeBSD CD so that it does a non-interactive (or minimally interactive ;-) install. The interim solution we've devised has our lab execution techs booting from a CD and then using the Sysinstall "Load config file" menu option to load an "install.cfg" file from a floppy. We'd like to eliminate this step by

OK. I'll try it, but it really puzzles me how the battery could have gone bad for just 15 months. The online power is pretty stable, so the battery hasn't gone through many charge/discharge cycles... Regards, -- Georgi On 11.1.2020 at 14:24, Manuel Wolfshant wrote: > > indicates that the UPS thought that battery was close to depleted and decided to shutdown. I suggest to fully

While on the topic of Rd macro arguments, it seems that if a multiline argument is supplied, the lines after the first are silently ignored: f <- tempfile() mac6 <- "\\newcommand{\\mac6}{mac6: #1}" cat(mac6, "\\mac6{2*3 2+2 sin(pi) }\n", file = f) rd <- tools::parse_Rd(f) > rd mac6: 2*3 --- Georgi Boshnakov -----Original Message----- From: Tomas Kalibera

I''m currently using Shorewall 3.4.1 to manage a firewall for my LAN at home. It works very well, and I''m definitely pleased, but . . . . I now have a situation where I need to enforce access restrictions on a specific computer during specific times of day -- e.g., a particular computer might have no Internet access at all between 10 PM and 6 AM. Is there any way to do such a

Bug or feature? I get the following error from parse_Rd() when a user Rd macro (including system ones) is invoked with empty argument {}, eg \mymacro{}: Error in tools::parse_Rd(fn) : Value of SET_STRING_ELT() must be a 'CHARSXP' not a 'NULL' A full example is further below with the system macro \CRANpkg{}. In this example it doesn't make sense to use empty argument but

Exactly what I need. I am so glad that you read the forum. Thanks a lot. ----- Original Message ----- From: "Robert Watson" <rwatson@FreeBSD.org> To: "Georgi Hristov" <hristov@iocc.com> Sent: Thursday, June 26, 2003 10:44 AM Subject: Re: SysLog Manipulation | On Thu, 26 Jun 2003, Georgi Hristov wrote: | | > About what time did you merge it ... I may have

http://bugzilla.mindrot.org/show_bug.cgi?id=1288 Summary: ssh-add on Cygwin -- can't access ssh-agent socket Product: Portable OpenSSH Version: v4.5p1 Platform: ix86 OS/Version: Cygwin on NT/2k Status: NEW Severity: major Priority: P2 Component: ssh-add AssignedTo: bitbucket at mindrot.org

I'm running Dovecot 2.2.1 on an Ubuntu 12.04.2 server, with half a dozen accounts for various family members. I want to set up replication involving at least three Ubuntu servers, with different users replicated on different sets of servers. For example, I might have mail for "user1" replicated on "server1", "server2", and "server3"... while mail for

> ... reports that the fortran names of all the registered fortran functions are ?undocumented objects?... Those symbols should not be exported. In quantreg v5.33, NAMESPACE has 'exportPattern(".")'. Maybe it is a good time to remove that and export explicitly the symbols that are meant for export. Georgi Boshnakov ------------------------------ Message: 6 Date: Fri, 28