root umask and building ports

2013-08-04 Thread Karl Dunn
I discovered the hard way, when building ImageMagick-6.7.9.4 on 
9.1-RELEASE, that having root's umask set to 077 is a mistake.


Lots of directories and some files, in ImageMagick itself and some of the 
dependent ports, had other and group perms set to ---.  No good.  Hard to 
fix after the fact: I tracked down all the problems with four-liner 
command that used find, ls, and grep; then I fixed them by hand, more or 
less.


Made a lot of work for myself, just to get mogrify to run in a script that 
generates per-user web activity bar graphs once a week.


This is probably not a new discovery to most.  I have been using FreeBSD 
for a long time (about 15 years), but I still regard myself as a newbie.


Lesson learned.  Leave root umask set to 022.  (Maybe ports should be 
written to not depend on root's umask?)


Karl Dunn
kd...@acm.org

On Sun, 4 Aug 2013, freebsd-stable-requ...@freebsd.org wrote:


Send freebsd-stable mailing list submissions to
freebsd-stable@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
or, via email, send a message with subject or body 'help' to
freebsd-stable-requ...@freebsd.org

You can reach the person managing the list at
freebsd-stable-ow...@freebsd.org

When replying, please edit your Subject line so it is more specific
than Re: Contents of freebsd-stable digest...


Today's Topics:

  1. Re: Strange sendmail behaviour after upgrade to 9.1-BETA2
 (Pavel Timofeev)
  2. Re: ZFS: can't read MOS of pool (Andriy Gapon)
  3. Re: /usr/bin/ld: warning: creating a DT_TEXTREL in a shared
 object after freebsd-update (Fabian Wenk)
  4. Re: Problem with zfsloader on 9.2-BETA2 (Andriy Gapon)
  5. Re: Strange sendmail behaviour after upgrade to 9.1-BETA2
 (Pavel Timofeev)
  6. NFS locking between 8.3-STABLE (jan 2013) and 9.2-BETA2 --
 Firefox SQLite locking issue (John Reynolds)
  7. Re: NFS locking between 8.3-STABLE (jan 2013) and 9.2-BETA2
 -- Firefox SQLite locking issue (Rick Macklem)


--

Message: 1
Date: Sat, 3 Aug 2013 17:41:58 +0400
From: Pavel Timofeev tim...@gmail.com
To: Ruben de Groot mai...@bzerk.org
Cc: freebsd-stable@freebsd.org
Subject: Re: Strange sendmail behaviour after upgrade to 9.1-BETA2
Message-ID:
CAAoTqfu7n9j9V=H4Af2oTka=aS_UqKwkMCxE=ajm9i3gqxb...@mail.gmail.com
Content-Type: text/plain; charset=UTF-8

2013/8/2 Ruben de Groot mai...@bzerk.org:

On Wed, Jul 31, 2013 at 04:54:08PM +0400, Pavel Timofeev typed:

I've just installed new fresh 9.2-BETA2 amd64 on another machine.
Same behaviour - Sendmail asks DNS only for  record of mx server.
We don't use IPv6 in our company.

2013/7/31 Pavel Timofeev tim...@gmail.com:

I wanted to say that sendmail asks only  (IPv6) record of mx
server, but not A (IPv4).
Any ideas?

2013/7/31 Pavel Timofeev tim...@gmail.com:

Looks like my sendmail uses only IPv6 to resolve mx server dns name to
ip address.

14:59:50.793338 IP reticulum.xxx.ru.19032  hercules.xxx.ru.domain:
53417+ ? xxx.ru. (24)
   [13/98]
14:59:50.793662 IP hercules.xxx.ru.domain  reticulum.xxx.ru.19032:
53417* 0/1/0 (75)
14:59:50.793696 IP reticulum.xxx.ru.55299  hercules.xxx.ru.domain:
53418+ A? xxx.ru. (24)


Here it is definately asking an A record.


And? It's not A record of mx server.


14:59:50.794087 IP hercules.xxx.ru.domain  reticulum.xxx.ru.55299:
53418* 7/0/0 A 192.168.2.11, A 192.168.2.12, A 192.168.41.4, A
192.168.14.12, A 192.168.34.100, A 192.168.34.110, A 192.168.44.19
 (136)


And here is the reply. The quetion is more why is it repeating the same
query (below) over and over.


Yes, reply about xxx.ru, not about mx server's IP which is kalmar.xxx.ru



Ruben


14:59:50.973445 IP reticulum.xxx.ru.29244  hercules.xxx.ru.domain:
53419+ MX? xxx.ru. (24)
14:59:50.973754 IP hercules.xxx.ru.domain  reticulum.xxx.ru.29244:
53419* 1/0/1 MX kalmar.xxx.ru. 10 (63)
14:59:50.974061 IP reticulum.xxx.ru.56461  hercules.xxx.ru.domain:
53420+ ? kalmar.xxx.ru. (31)
14:59:50.974340 IP hercules.xxx.ru.domain  reticulum.xxx.ru.56461:
53420* 0/1/0 (82)
14:59:50.974570 IP reticulum.xxx.ru.28332  hercules.xxx.ru.domain:
53421+ ? kalmar.xxx.ru. (31)
14:59:50.974887 IP hercules.xxx.ru.domain  reticulum.xxx.ru.28332:
53421* 0/1/0 (82)
14:59:50.974919 IP reticulum.xxx.ru.21453  hercules.xxx.ru.domain:
53422+ ? kalmar. (24)
14:59:50.975290 IP hercules.xxx.ru.domain  reticulum.xxx.ru.21453:
53422 ServFail 0/0/0 (24)
14:59:50.975314 IP reticulum.xxx.ru.63038  hercules.xxx.ru.domain:
53422+ ? kalmar. (24)
14:59:50.975674 IP hercules.xxx.ru.domain  reticulum.xxx.ru.63038:
53422 ServFail 0/0/0 (24)
14:59:50.975749 IP reticulum.xxx.ru.38393  hercules.xxx.ru.domain:
53423+ ? kalmar.xxx.ru. (31)
14:59:50.976105 IP hercules.xxx.ru.domain  reticulum.xxx.ru.38393:
53423* 0/1/0 (82)
14:59:50.976176 IP 

Curious error messages when building ports?

2007-03-08 Thread Torfinn Ingolfsen
Hello,

I hav seen this on FreeBSD 6-stable recently.
Here is an example, from a machine running
[EMAIL PROTECTED] uname -a
FreeBSD kg-work.kg4.no 6.2-STABLE FreeBSD 6.2-STABLE #2: Sat Jan 20 17:26:43 
CET 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SS51G  i386
I cd into /usr/ports/audio/gxmms2 and issue the command 'make'.
Before it actually starts to build, I get lots of lines like these on screen:
grep: writing output: Broken pipe
grep: writing output: Broken pipe
grep: writing output: Broken pipe
grep: writing output: Broken pipe
grep: writing output: Broken pipe

Anyone know what's causing this?
-- 
Regards,
Torfinn Ingolfsen,
Norway

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Building Ports

2001-08-29 Thread Doug Hardie

I just heard a most interest tale of woe.  A new user installing 
4.3-Release wanted some ports.  I gave him specific instructions, in 
writing, on how to build those ports.  For some reason he ignored the 
step to cd to the specific port and did essentially:

cd /usr/ports
make

The system dutifully started making all the ports in alphabetical 
order for quite a few hours until he finally ran out of disk space. 
Is this feature really useful or something that is a byproduct of 
useful features?  I ask to be sure that there was a delebriate 
decision for this to happen.
-- 
-- Doug

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message