Re: Somewhat OT: Is Full Command Logging Possible?
Tim Daneliuk wrote at 17:48 -0600 on Dec 5, 2012: On 12/05/2012 05:44 PM, Kurt Buff wrote: On Wed, Dec 5, 2012 at 3:19 PM, Tim Daneliuk tun...@tundraware.com wrote: I am working with an institution that today provides limited privilege escalation on their servers via very specific sudo rules. The problem is that the administrators can do 'sudo su -'. snip sudo is misconfigured. man 5 sudoers and man 8 visudo Kurt I'm sorry Kurt, I'm sort of dense today, I'm not sure what you're saying. Are you suggesting that there is a way to configure sudo so that if someone does 'sudo su -' to become an admin, sudo can be made to log every command they execute thereafter? See log_input and log_output in sudoers(5) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /tmp filesystem full
Andy Wodfer wrote at 12:59 +0200 on Aug 22, 2012: Hi, I have about 500MB in my /tmp and it seems to be too small when the periodic LOCATE script runs every week. What's the best way to increase the size of /tmp ? Could I simply remove it and create a symbolic link ln -s to say /usr/tmp instead (where I have several hundred GBs free)? PS! This is on a live server and I would like to keep downtime and problems to a minimum. :-) One way is to work around your problem is to add 'TMPDIR=/path/to/bigger/filesystem' in /etc/crontab and/or 'export TMPDIR=/path/...' in /etc/periodic.conf. No downtime for that. But yes, you can make /tmp a sym link. You may have to worry about edge cases regarding booting (like if the filesystem you point to is not available early enough at boot time). In the typical case (e.g., locally mounted ufs), it should work fine. There may be very rare cases of software that gets confused by a sym link for /tmp, but certainly the stock periodic scripts should work with it. Depending on what processes have files open on /tmp, you may decide to use some down time to make the sym link. You can't use mv(1) to rename a mounted mount point. If you can umount /tmp, then you can rename it and make the sym link. But it's possible some processes have files open in /tmp preventing a normal umount (see lsof(8), fstat(1)). You would have to convince those processes to close the /tmp file descriptors. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Evolution 2.32.3 printing
Polytropon wrote at 11:45 +0200 on May 23, 2012: On Wed, 23 May 2012 10:20:18 +0200, Matthias Apitz wrote: Hi, I run Evolution 2.32.3 in FreeBSD 9-CURRENT in my office because I have to use a MS Exchange server with OWA only; When I want to print something (Ctrl-P) a dialog comes up presenting the CUPS configured printers and a field where one could type in a command line for printing; this field is pre-set to lpr I would like to have it set to lpr -Paps -o SelectColor=Grayscale -o I don't see how to configure this. I see tow ways to do it: 1. Change the settings for your default printer in the CUPS configuration web page. Make aps the default printer and add the desired options. Now lpr will default to that specific set of options. 2. Consult Evolution's documentation in regards of a config file that allows overriding the content of the printing dialog setting (such as xpdf can do). Good luck. :-) 3. Install mail/davmail (gateway from proprietary exchange formats to standard protocols) and use any mail client you want (via imap or pop). And use any calendar client you want (caldav, ical). A bit off topic unless you have an email client that you can more easily achieve your goal - so worth mentioning. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD's tftp and tftpd-hpa
Martin Cracauer wrote at 11:53 -0500 on Feb 11, 2011: FreeBSD's current tftp client doesn't work with tftpd-hpa. FreeBSD 9.0-CURRENT (XEN) #0: Fri Jan 21 15:54:41 EST 2011 ~(fbpv)1% tftp 192.168.1.1 tftp get pxeboot Got ERROR packet: Unsupported option(s) requested Error code 2048: Unsupported option(s) requested tftp Anybody got a solution for this? Otherwise I'll hack it up. I just hit this, too. The linux (hpa) version of tftpd has: /* * Return a file size (c.f. RFC2349) * For netascii mode, we don't know the size ahead of time; * so reject the option. */ So, for the archives (only two months later!), you can use 'mode octet' (aka 'mode binary') to can work around this issue. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dual (zaphod) head on Intel i810 does not work for FreeBSD V7.0 Release
Ray Newman wrote at 17:56 +1000 on Aug 29, 2008: Under FreeBSD V6.2 Release (X 6.9.0 and i810 1.4.1) with this xorg.conf, this log file is produced and the dual screen config works. . . Under FreeBSD V7.0 Release (X 1.4.0 and i810 1.6.5) with this xorg.conf which is nearly identical with the previous one, this log file is produced and the dual screen doesn't work. It seems to get the primary and secondary screens totally confused. What if you try x11-drivers/xf86-video-intel instead of x11-drivers/xf86-video-i810? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
