allow _proxy variables in sudoers
When you are in a place that requires proxy configs to reach the internet, it would be very nice if you could then use pkg_add. So, add ftp_proxy and http_proxy to the default env_keep variable. OK? Index: usr.bin/sudo/sudoers === RCS file: /cvs/openbsd/src/usr.bin/sudo/sudoers,v retrieving revision 1.25 diff -u -p -r1.25 sudoers --- usr.bin/sudo/sudoers26 Oct 2009 19:28:26 - 1.25 +++ usr.bin/sudo/sudoers15 Jan 2012 14:13:48 - @@ -20,7 +20,7 @@ Defaults env_keep +=DESTDIR DISTDIR EDI Defaults env_keep +=MAKECONF MULTI_PACKAGES NOMAN OKAY_FILES OWNER PKG_CACHE Defaults env_keep +=PKG_DBDIR PKG_DESTDIR PKG_PATH PKG_TMPDIR PORTSDIR Defaults env_keep +=RELEASEDIR SHARED_ONLY SSH_AUTH_SOCK SUBPACKAGE VISUAL -Defaults env_keep +=WRKOBJDIR +Defaults env_keep +=WRKOBJDIR ftp_proxy http_proxy # Uncomment to disable the lecture the first time you run sudo #Defaults !lecture -- Conscious is when you are aware of something and conscience is when you wish you weren't.
Re: allow _proxy variables in sudoers
I need this @ work. On Sun, Jan 15, 2012 at 6:15 PM, Peter Hessler phess...@theapt.org wrote: When you are in a place that requires proxy configs to reach the internet, it would be very nice if you could then use pkg_add. So, add ftp_proxy and http_proxy to the default env_keep variable. OK? Index: usr.bin/sudo/sudoers === RCS file: /cvs/openbsd/src/usr.bin/sudo/sudoers,v retrieving revision 1.25 diff -u -p -r1.25 sudoers --- usr.bin/sudo/sudoers26 Oct 2009 19:28:26 - 1.25 +++ usr.bin/sudo/sudoers15 Jan 2012 14:13:48 - @@ -20,7 +20,7 @@ Defaults env_keep +=DESTDIR DISTDIR EDI Defaults env_keep +=MAKECONF MULTI_PACKAGES NOMAN OKAY_FILES OWNER PKG_CACHE Defaults env_keep +=PKG_DBDIR PKG_DESTDIR PKG_PATH PKG_TMPDIR PORTSDIR Defaults env_keep +=RELEASEDIR SHARED_ONLY SSH_AUTH_SOCK SUBPACKAGE VISUAL -Defaults env_keep +=WRKOBJDIR +Defaults env_keep +=WRKOBJDIR ftp_proxy http_proxy # Uncomment to disable the lecture the first time you run sudo #Defaults !lecture -- Conscious is when you are aware of something and conscience is when you wish you weren't. -- Brightest day, Blackest night, No bug shall escape my sight, And those who worship evil's mind, be wary of my powers, puffy lantern's light !
Re: SiS 5513 rev 0x015597/5598 freeze diff
On Sat, Jan 14, 2012 at 06:41:31PM +0400, Loganaden Velvindron wrote: Yep, Chris Cappuccio. He says that there are still issues with the SiS code. Instead of defaulting to SiS 5597/5598, perhaps it would have been better not to attach as it would have made the problem more obvious. I've committed this now. Unknown SiS devices could still be attached with udma disabled if we were sure the 5597/5598 case is only used in machines with 5597_HB and and another else. For now I've opted not to do this, it seems they are out of the chipset business. Their webpage doesn't mention them in the products section, so we can only hope.
athn(4) device timeout
Hi Tech, I have been advised by cthuluh and others on #openbsd@freenode to post issue with my hardware reset for athn(4) in here. It is not clear why it happens to me. Also, I wanted to point out that it doesn't affect my connection to the router in any way if any at all. The issue I have is as stated in ath(4) is: ath%d: device timeout A frame dispatched to the hardware for transmission did not complete in time. The driver will reset the hardware and continue. This should not happen. And here's the grep'ed log: Jan 14 15:14:50 puffybox /bsd: athn0: device timeout Jan 14 20:26:58 puffybox /bsd: athn0: device timeout And here's the full dmesg: OpenBSD 5.0 (GENERIC.MP) #59: Wed Aug 17 10:19:44 MDT 2011 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP RTC BIOS diagnostic error 80clock_battery cpu0: Intel(R) Atom(TM) CPU N455 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE real mem = 1060954112 (1011MB) avail mem = 1033527296 (985MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 03/24/11, BIOS32 rev. 0 @ 0xef735, SMBIOS rev. 2.6 @ 0xe5840 (33 entries) bios0: vendor INSYDE version V1.00 date 03/24/2011 bios0: Acer AOD257 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC MCFG SLIC BOOT SSDT SSDT SSDT WDAT acpi0: wakeup devices P32_(S4) UHC1(S3) UHC2(S3) UHC3(S3) UHC4(S3) ECHI(S3) EXP1(S4) EXP2(S3) EXP3(S3) EXP4(S3) AZAL(S4) MODM(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 166MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Atom(TM) CPU N455 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 4 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 4 (P32_) acpiprt2 at acpi0: bus 1 (EXP1) acpiprt3 at acpi0: bus 2 (EXP2) acpiprt4 at acpi0: bus 3 (EXP3) acpiprt5 at acpi0: bus -1 (EXP4) acpiec0 at acpi0 acpicpu0 at acpi0: C2, C1, PSS acpicpu1 at acpi0: C2, C1, PSS acpitz0 at acpi0: critical temperature is 96 degC acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: LID_ acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT1 model AL10A31 serial 4478 type LION oem SANYO acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: DD02 bios0: ROM list: 0xc/0xda00! 0xcda00/0x1000 cpu0: Enhanced SpeedStep 1663 MHz: speeds: 1666, 1333, 1000 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel Pineview DMI rev 0x00 vga1 at pci0 dev 2 function 0 Intel Pineview Video rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0x4000, size 0x1000 inteldrm0 at vga1: apic 4 int 16 drm0 at inteldrm0 Intel Pineview Video rev 0x00 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: msi azalia0: codecs: Realtek ALC269 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: apic 4 int 16 pci1 at ppb0 bus 1 re0 at pci1 dev 0 function 0 Realtek 8101E rev 0x05: RTL8105E (0x4080), apic 4 int 16, address e8:9a:8f:09:b8:f7 ukphy0 at re0 phy 7: Generic IEEE 802.3u media interface, rev. 2: OUI 0x000732, model 0x0008 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: apic 4 int 17 pci2 at ppb1 bus 2 athn0 at pci2 dev 0 function 0 Atheros AR9285 rev 0x01: apic 4 int 17 athn0: AR9285 rev 2 (1T1R), ROM rev 14, address ec:55:f9:ac:d6:32 ppb2 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x02: apic 4 int 18 pci3 at ppb2 bus 3 Realtek RTS5209 Card Reader rev 0x01 at pci3 dev 0 function 0 not configured uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x02: apic 4 int 16 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x02: apic 4 int 17 uhci2 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x02: apic 4 int 19 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x02: apic 4 int 16 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb3 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0xe2 pci4 at ppb3 bus 4 pcib0 at pci0 dev 31 function 0 Intel Tigerpoint LPC rev 0x02 ahci0 at pci0 dev 31 function 2 Intel 82801GR AHCI rev 0x02: msi, AHCI 1.1 scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 0 lun 0: ATA, Hitachi HTS54502, PB2O SCSI3 0/direct fixed naa.5000cca66cd2a09e sd0: 238475MB, 512 bytes/sector, 488397168
Small pkill enhancement
Some months ago there was an email about adding a 'i' option
to pgrep/pkill, one suggestion from that discussion was giving
pkill the ability to say if nothing had been killed.
http://marc.info/?l=openbsd-techm=130789344027691w=2
I must say, I liked this idea. But only got time recently
to have a look. Anyway FreeBSD has the code. Here it is
imported into OpenBSD's pgrep/pkill. The diff does
slightly more than just inform you of no kills, but I
like that aspect as well.
Comments/oks?
-lum
Index: pkill.1
===
RCS file: /cvs/src/usr.bin/pkill/pkill.1,v
retrieving revision 1.16
diff -u -p -r1.16 pkill.1
--- pkill.1 29 Sep 2010 07:44:56 - 1.16
+++ pkill.1 15 Jan 2012 18:03:00 -
@@ -48,7 +48,7 @@
.Op Ar pattern ...
.Nm pkill
.Op Fl Ar signal
-.Op Fl fnovx
+.Op Fl flnovx
.Op Fl G Ar gid
.Op Fl g Ar pgrp
.Op Fl P Ar ppid
@@ -100,9 +100,9 @@ process.
If used in conjunction with
.Fl f ,
print the process ID and the full argument list for each matching process.
-This option can only be used with the
-.Nm pgrep
-command.
+For
+.Nm pkill ,
+display the kill command used for each process killed.
.It Fl n
Match only the most recently created (newest) process, if any.
Cannot be used in conjunction with
Index: pkill.c
===
RCS file: /cvs/src/usr.bin/pkill/pkill.c,v
retrieving revision 1.19
diff -u -p -r1.19 pkill.c
--- pkill.c 10 Apr 2011 03:20:59 - 1.19
+++ pkill.c 15 Jan 2012 18:03:00 -
@@ -112,6 +112,7 @@ main(int argc, char **argv)
char buf[_POSIX2_LINE_MAX], *mstr, **pargv, *p, *q;
int i, j, ch, bestidx, rv, criteria;
int (*action)(struct kinfo_proc *, int);
+ int did_action;
struct kinfo_proc *kp;
struct list *li;
u_int32_t bestsec, bestusec;
@@ -176,8 +177,6 @@ main(int argc, char **argv)
criteria = 1;
break;
case 'l':
- if (!pgrep)
- usage();
longfmt = 1;
break;
case 'n':
@@ -392,11 +391,16 @@ main(int argc, char **argv)
/*
* Take the appropriate action for each matched process, if any.
*/
+ did_action = 0;
rv = STATUS_NOMATCH;
for (i = 0, j = 0, kp = plist; i nproc; i++, kp++) {
if ((kp-p_flag P_SYSTEM) != 0 || kp-p_pid == mypid)
continue;
if (selected[i]) {
+ if (longfmt !pgrep) {
+ did_action = 1;
+ printf(kill -%d %d\n, signum, (int)kp-p_pid);
+ }
if (inverse)
continue;
} else if (!inverse)
@@ -407,6 +411,9 @@ main(int argc, char **argv)
else if (rv != STATUS_ERROR)
rv = STATUS_MATCH;
}
+if (!did_action !pgrep longfmt)
+fprintf(stderr,
+No matching processes belonging to you were found\n);
if (pgrep j)
putchar('\n');
@@ -421,7 +428,7 @@ usage(void)
if (pgrep)
ustr = [-flnovx] [-d delim];
else
- ustr = [-signal] [-fnovx];
+ ustr = [-signal] [-flnovx];
fprintf(stderr, usage: %s %s [-G gid] [-g pgrp] [-P ppid] [-s sid]
[-t tty]\n\t[-U uid] [-u euid] [pattern ...]\n, __progname, ustr);
Re: Small pkill enhancement
Hi
I think that error message is misleading if you are running pkill as
root.
How about instead of only printing if it did nothing, -l makes it always
print %d processes signalled?
On Sun, Jan 15, 2012 at 06:26:39PM +, Mark Lumsden wrote:
Some months ago there was an email about adding a 'i' option
to pgrep/pkill, one suggestion from that discussion was giving
pkill the ability to say if nothing had been killed.
http://marc.info/?l=openbsd-techm=130789344027691w=2
I must say, I liked this idea. But only got time recently
to have a look. Anyway FreeBSD has the code. Here it is
imported into OpenBSD's pgrep/pkill. The diff does
slightly more than just inform you of no kills, but I
like that aspect as well.
Comments/oks?
-lum
Index: pkill.1
===
RCS file: /cvs/src/usr.bin/pkill/pkill.1,v
retrieving revision 1.16
diff -u -p -r1.16 pkill.1
--- pkill.1 29 Sep 2010 07:44:56 - 1.16
+++ pkill.1 15 Jan 2012 18:03:00 -
@@ -48,7 +48,7 @@
.Op Ar pattern ...
.Nm pkill
.Op Fl Ar signal
-.Op Fl fnovx
+.Op Fl flnovx
.Op Fl G Ar gid
.Op Fl g Ar pgrp
.Op Fl P Ar ppid
@@ -100,9 +100,9 @@ process.
If used in conjunction with
.Fl f ,
print the process ID and the full argument list for each matching process.
-This option can only be used with the
-.Nm pgrep
-command.
+For
+.Nm pkill ,
+display the kill command used for each process killed.
.It Fl n
Match only the most recently created (newest) process, if any.
Cannot be used in conjunction with
Index: pkill.c
===
RCS file: /cvs/src/usr.bin/pkill/pkill.c,v
retrieving revision 1.19
diff -u -p -r1.19 pkill.c
--- pkill.c 10 Apr 2011 03:20:59 - 1.19
+++ pkill.c 15 Jan 2012 18:03:00 -
@@ -112,6 +112,7 @@ main(int argc, char **argv)
char buf[_POSIX2_LINE_MAX], *mstr, **pargv, *p, *q;
int i, j, ch, bestidx, rv, criteria;
int (*action)(struct kinfo_proc *, int);
+ int did_action;
struct kinfo_proc *kp;
struct list *li;
u_int32_t bestsec, bestusec;
@@ -176,8 +177,6 @@ main(int argc, char **argv)
criteria = 1;
break;
case 'l':
- if (!pgrep)
- usage();
longfmt = 1;
break;
case 'n':
@@ -392,11 +391,16 @@ main(int argc, char **argv)
/*
* Take the appropriate action for each matched process, if any.
*/
+ did_action = 0;
rv = STATUS_NOMATCH;
for (i = 0, j = 0, kp = plist; i nproc; i++, kp++) {
if ((kp-p_flag P_SYSTEM) != 0 || kp-p_pid == mypid)
continue;
if (selected[i]) {
+ if (longfmt !pgrep) {
+ did_action = 1;
+ printf(kill -%d %d\n, signum, (int)kp-p_pid);
+ }
if (inverse)
continue;
} else if (!inverse)
@@ -407,6 +411,9 @@ main(int argc, char **argv)
else if (rv != STATUS_ERROR)
rv = STATUS_MATCH;
}
+if (!did_action !pgrep longfmt)
+fprintf(stderr,
+No matching processes belonging to you were found\n);
if (pgrep j)
putchar('\n');
@@ -421,7 +428,7 @@ usage(void)
if (pgrep)
ustr = [-flnovx] [-d delim];
else
- ustr = [-signal] [-fnovx];
+ ustr = [-signal] [-flnovx];
fprintf(stderr, usage: %s %s [-G gid] [-g pgrp] [-P ppid] [-s sid]
[-t tty]\n\t[-U uid] [-u euid] [pattern ...]\n, __progname, ustr);
Re: libXi: SIGBUS in ParseClassInfo on sparc64
On Fri, Jan 13, 2012 at 03:03:09PM +0100, David Coppa wrote:
Hi!
I've noticed that on sparc64 we got the same SIGBUS described here:
http://comments.gmane.org/gmane.comp.freedesktop.xorg/44722
This happens frequently and it's annoying as it renders GTK2
applications unusable on sparc64, since our gtk+2 is being
built using --with-xinput.
---8---
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as sparc64-unknown-openbsd5.0...(no debugging
symbols found)
(gdb) run
Starting program: /usr/local/bin/gtk-demo
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Program received signal SIGBUS, Bus error.
0x00020bd628ac in ParseClassInfo (any=0xfffcf068,
Any=0xfffcf058, num_classes=1) at
/usr/xenocara/lib/libXi/src/XListDev.c:104
104 K-class = KeyClass;
(gdb) bt
#0 0x00020bd628ac in ParseClassInfo (any=0xfffcf068,
Any=0xfffcf058, num_classes=1) at
/usr/xenocara/lib/libXi/src/XListDev.c:104
#1 0x00020bd63024 in XListInputDevices (dpy=0x20ca5edb0,
ndevices=0xfffcf18c) at /usr/xenocara/lib/libXi/src/XListDev.c:227
#2 0x000209b7c518 in gdk_drag_action_get_type () from
/usr/local/lib/libgdk-x11-2.0.so.2400.0
#3 0x000209b53c74 in gdk_drag_action_get_type () from
/usr/local/lib/libgdk-x11-2.0.so.2400.0
#4 0x000209b1c58c in gdk_display_open_default_libgtk_only () from
/usr/local/lib/libgdk-x11-2.0.so.2400.0
#5 0x0002008603e4 in gtk_init_check () from
/usr/local/lib/libgtk-x11-2.0.so.2400.0
#6 0x00020086041c in gtk_init () from
/usr/local/lib/libgtk-x11-2.0.so.2400.0
#7 0x00122e5c in main ()
(gdb) bt full
#0 0x00020bd628ac in ParseClassInfo (any=0xfffcf068,
Any=0xfffcf058, num_classes=1) at
/usr/xenocara/lib/libXi/src/XListDev.c:104
K = 0x20785ad44
k = 0x20c994860
j = 0
k = 3
#1 0x00020bd63024 in XListInputDevices (dpy=0x20ca5edb0,
ndevices=0xfffcf18c) at /usr/xenocara/lib/libXi/src/XListDev.c:227
size = 695
req = (xListInputDevicesReq *) 0x202248000
rep = {repType = 1 '\001', RepType = 2 '\002', sequenceNumber = 105,
length = 87, ndevices = 6 '\006', pad1 = 0 '\0', pad2 = 0 '\0', pad3 = 0
'\0',
pad01 = 0, pad02 = 0, pad03 = 0, pad04 = 0, pad05 = 0}
list = (xDeviceInfo *) 0x20c994808
slist = (xDeviceInfo *) 0x20c994800
sclist = (XDeviceInfo *) 0x20785ac00
clist = (XDeviceInfo *) 0x20785ac28
any = 0x20c994860
sav_any = 0x20c994830
Any = 0x20785ad44
nptr = 0x20c99495b
Nptr = 0xfffcf18c
i = 1
rlen = 348
info = (XExtDisplayInfo *) 0x20a1b7100
---8---
So, I've cherrypicked the patch at:
http://patchwork.freedesktop.org/patch/2272/
...And applied it to SizeClassInfo() too as suggested (it won't hurt)
This fixes the issue for me.
Comments or suggestions?
You should ping Peter to ask him why this is still not committed
upstreams.
It looks to me like this changes the on-wire procol, but I'm not sure
and I haven't found time to check for real during the weekend.
Index: src/XListDev.c
===
RCS file: /cvs/xenocara/lib/libXi/src/XListDev.c,v
retrieving revision 1.3
diff -u -p -r1.3 XListDev.c
--- src/XListDev.c11 Nov 2010 10:49:22 - 1.3
+++ src/XListDev.c13 Jan 2012 13:07:33 -
@@ -58,6 +58,17 @@ SOFTWARE.
#include X11/extensions/extutil.h
#include XIint.h
+/* Calculate length field to a multiples of sizeof(XID). XIDs are typedefs
+ * to ulong and thus may be 8 bytes on some platforms. This can trigger a
+ * SIGBUS if a class ends up not being 8-aligned (e.g. after XAxisInfo).
+ */
+static int pad_to_xid(int base_size)
+{
+int padsize = sizeof(XID);
+
+return ((base_size + padsize - 1)/padsize) * padsize;
+}
+
static int
SizeClassInfo(xAnyClassPtr *any, int num_classes)
{
@@ -66,18 +77,18 @@ SizeClassInfo(xAnyClassPtr *any, int num
for (j = 0; j num_classes; j++) {
switch ((*any)-class) {
case KeyClass:
-size += sizeof(XKeyInfo);
+size += pad_to_xid(sizeof(XKeyInfo));
break;
case ButtonClass:
-size += sizeof(XButtonInfo);
+size += pad_to_xid(sizeof(XButtonInfo));
break;
case ValuatorClass:
{
xValuatorInfoPtr v;
v = (xValuatorInfoPtr) *any;
-size +=
Fw: Documento.
Anexo: Documento-Planilha.doc (149,1 KB) Segue em anexo conforme solicitado o relatorio. Tenha um bom dia!
Re: Small pkill enhancement
Not to jhijack the thread but to show another -- more generic way -- of dealing with apps that fail silently: This changes the prompt $ to red incase the $? return value of the previous process returned non-zero. red=$(printf '\e[31m') export PS1='\[\e[0;36m\]\w\[\e[01m\]\[\e[30m\]$([ $? -eq 0 ]||printf $red)\$\[\e[0m\] ' # Han
Re: Small pkill enhancement
On 15 January 2012 at 19:02 Nicholas Marriott nicholas.marri...@gmail.com wrote: Hi I think that error message is misleading if you are running pkill as root. Yes, I agree. How about instead of only printing if it did nothing, -l makes it always print %d processes signalled? Currently, the diff from Freebsd prints a line for each process that is signalled: # pkill -l top kill -15 20908 kill -15 9439 I like the fact you can see which pids were affected. If none are affected, I can change the message to: No matching processes were found. mark
Re: allow _proxy variables in sudoers
you forgot https_proxy and no_proxy... however, im against this change since it allows a user to redirect a program they need privileges to use to an arbitrary proxy they specify, something there is no good mitigation against. dlg On 16/01/2012, at 12:15 AM, Peter Hessler wrote: When you are in a place that requires proxy configs to reach the internet, it would be very nice if you could then use pkg_add. So, add ftp_proxy and http_proxy to the default env_keep variable. OK? Index: usr.bin/sudo/sudoers === RCS file: /cvs/openbsd/src/usr.bin/sudo/sudoers,v retrieving revision 1.25 diff -u -p -r1.25 sudoers --- usr.bin/sudo/sudoers 26 Oct 2009 19:28:26 - 1.25 +++ usr.bin/sudo/sudoers 15 Jan 2012 14:13:48 - @@ -20,7 +20,7 @@ Defaults env_keep +=DESTDIR DISTDIR EDI Defaults env_keep +=MAKECONF MULTI_PACKAGES NOMAN OKAY_FILES OWNER PKG_CACHE Defaults env_keep +=PKG_DBDIR PKG_DESTDIR PKG_PATH PKG_TMPDIR PORTSDIR Defaults env_keep +=RELEASEDIR SHARED_ONLY SSH_AUTH_SOCK SUBPACKAGE VISUAL -Defaults env_keep +=WRKOBJDIR +Defaults env_keep +=WRKOBJDIR ftp_proxy http_proxy # Uncomment to disable the lecture the first time you run sudo #Defaults !lecture -- Conscious is when you are aware of something and conscience is when you wish you weren't.
devis traduction technique
Si vous ne visualisez pas correctement lbe-mail, cliquez ici http://img.mp23.ch/visu-E2591E9A-B23F-4D42-BE0A-950A978494CE-89320241-1 15551-16012012.html Bonjour, Je me permets de vous C)crire afin de vous proposer nos services de traduction. Disposez-vous dC)jC d'une agence partenaire? Notre agence, crC)C)e en 2001, peut intC)gralement prendre en charge vos projets multilingues ou bien ceux de vos clients et dispose dC)sormais d'un pC4le interprC)tariat. Quelques rC)fC)rences dans le domaine technique: Saint Gobain, Valeo, Groupe Moniteur, HC Engineering, Ragasco, Poujoulat SA, Gardner Denver (USA), Toyota, dbTechnologies, Panimatic, Redatech (Suisse), Recyl, Phoenix Mecano... Je suis C votre disposition pour toutes vos demandes d'informations et de devis, Bien cordialement AurC)lien SUPOT - DC)veloppement A.Text Work http://img.mp23.ch/clients/mailpro9131/techgen_AS.jpg Si vous ne dC)sirez plus recevoir notre lettre d'information, cliquez ici http://img.mp23.ch/89320241/111065/uns-108468-fr-16012012.html http://t1.mp23.ch/pic-115551-89320241-16012012.jpg
Re: Small pkill enhancement
On Mon, Jan 16, 2012 at 04:50:32AM +, Mark Lumsden wrote: On 15 January 2012 at 19:02 Nicholas Marriott nicholas.marri...@gmail.com wrote: Hi I think that error message is misleading if you are running pkill as root. Yes, I agree. How about instead of only printing if it did nothing, -l makes it always print %d processes signalled? Currently, the diff from Freebsd prints a line for each process that is signalled: # pkill -l top kill -15 20908 kill -15 9439 I like the fact you can see which pids were affected. I think I'd like it more if it printed the -l output in the same format as pgrep, rather than pretending it is running kill(1), but it isn't too important. If none are affected, I can change the message to: No matching processes were found. Actually, I don't see a need for a no processes message at all, surely just no kill 1234 output is enough to mean nothing? pgrep doesn't print anything when it finds nothing. mark
