summaryrefslogtreecommitdiffstats
path: root/libexec
Commit message (Collapse)AuthorAgeFilesLines
* Description from Dan:mdodd2005-02-044-13/+93
| | | | | | | | | | | | | | | Another handy libmap patch. Lets you do stuff like this: LD_LIBMAP="libpthread.so.1=libthr.so.1" mythreadedapp If you already have a program-specific override in libmap.conf, note that you must use a program-specific override in LD_LIBMAP: LD_LIBMAP="[mythreadedapp],libpthread.so.1=libthr.so.1" mythreadedapp PR: bin/74471 Submitted by: Dan Nelson <dnelson AT allantgroup.com> MFC after: 2 weeks
* style(9)mdodd2005-02-041-4/+3
|
* Let bsd.prog.mk set SRCS and MAN to their default values.ru2005-01-284-4/+0
|
* Respect the `logging' flag.yar2005-01-191-1/+1
| | | | | Pointed out by: Nick Leuta MFC after: 3 days
* Improve handling SIGURG and OOB commands on the control channel.yar2005-01-191-134/+269
| | | | | | | | | | | | | | | | | | | | | | | | The major change is to process STAT sent as an OOB command w/o breaking the current data transfer. As a side effect, this gives better error checking in the code performing data transfers. A lesser, but in no way cosmetic, change is using the flag `recvurg' in the only signal-safe way that has been blessed by SUSv3. The other flag, `transflag,' becomes private to the SIGURG machinery, serves debugging purposes only, and may be dropped in the future. The `byte_count' global variable is now accounting bytes actually transferred over the network. This can give status messages looking strange, like "X of Y bytes transferred," where X > Y, but that has more sense than trying to compensate for combinations of data formats on the server and client when transferring ASCII type data. BTW, getting the size of a file in advance is unreliable for a number of reasons in the first place. See question 18.8 of the Infrequently Asked Questions in comp.lang.c for details. PR: bin/52072 Tested by: Nick Leuta (earlier versions), a stress-testing tool (final) MFC after: 1 month
* Sort sections.ru2005-01-1814-94/+94
|
* 64-bit clean + WARNS=6:delphij2005-01-142-5/+4
| | | | | | | | | | | | | | | | | - Convert the (char *) cast+cast backs magic to memcpy(3). Without this, the resulting code is potentially risky with higher optimization levels. - Avoid same name when calling local variables, as well as global symbols. This reduces confusion for both human and compiler. - Add necessary casts, consts - Use new style function defination. - Minor style.Makefile(5) tweak - Bump WARNS?= from 0 to 6 ** for the aout code: changes are intentionally limited to ease maintaince.
* Restore these files to make ldconfig(8) happy.trhodes2005-01-114-0/+504
|
* Remove a.out runtime linker. It doesn't build and was removed from thetrhodes2005-01-1113-4456/+0
| | | | | | | | | | build over two years ago by peter. The binary a.out version of ld.so can be obtained from misc/compat22 or src/lib/compat/compat22. Discussed on: -arch Voted yes: jhb, ru, linimon, delphij
* Replace err(3) calls when in daemon mode by syslog(3), too.yar2005-01-101-4/+8
| | | | | | | A daemon has no stderr to send its complains to. Pointed out by: Nick Leuta MFC after: 1 week
* NOPAM -> NO_PAMru2004-12-212-2/+2
|
* NOINET6 -> NO_INET6ru2004-12-211-1/+1
|
* NOCRYPT -> NO_CRYPTru2004-12-211-1/+1
|
* NODOCCOMPRESS -> NO_DOCCOMPRESSru2004-12-211-1/+1
| | | | | | | | NOINFO -> NO_INFO NOINFOCOMPRESS -> NO_INFOCOMPRESS NOLINT -> NO_LINT NOPIC -> NO_PIC NOPROFILE -> NO_PROFILE
* Start the dreaded NOFOO -> NO_FOO conversion.ru2004-12-213-3/+3
| | | | OK'ed by: core
* Do a small style(9) fix before I'm hacking the code itself.yar2004-12-161-1/+0
|
* free(3) is void already.yar2004-12-161-1/+1
|
* Never emit a message to stderr: use syslog instead.yar2004-12-121-9/+15
| | | | | | | | | | When in inetd mode, this prevents bogus messages from appearing on the control channel. When running as a daemon, we shouldn't write to the terminal we used to have at all. PR: bin/74823 MFC after: 1 week
* Implement a dummy atomic_cmpset_32(). It should be safe to use it in rtld ascognet2004-11-231-0/+11
| | | | the signals are masked anyway.
* When looking for a virtual host to handle the connection,yar2004-11-221-2/+3
| | | | | | stop the search on the first match for efficiency. Submitted by: Nick Leuta
* Calling pam_chauthtok() isn't really needed sinceyar2004-11-221-7/+3
| | | | | | an FTP user has no chance to change password anyway. Submitted by: Nick Leuta
* Don't log the chroot dir on every command since it's constant for a session.yar2004-11-221-9/+8
| | | | | | | Log it once at the beginning of the session instead. OTOH, log wd each time for the sake of better auditing and consistent log format. Proposed by: Nick Leuta <skynick -at- mail.sc.ru>
* Always log remote IP.yar2004-11-221-13/+9
| | | | PR: bin/59773
* Treat host name buffers consistently.yar2004-11-221-12/+23
|
* Make chrootdir global and use it in log messagesyar2004-11-181-9/+4
| | | | | | regarding restricted users. MFC after: 2 weeks
* Nitpicking on style(9) and whitespace.yar2004-11-181-13/+13
| | | | Tested with: md5(1)
* Use __FBSDID.yar2004-11-184-8/+12
|
* Don't say, "file: permission denied," if the operationyar2004-11-181-1/+1
| | | | is disabled entirely.
* Use uniform punctuation, capitalization, and language styleyar2004-11-182-45/+44
| | | | | in server messages wherever this doesn't contradict to a particular message format.
* Apply __printflike() to the appendf() prototype so the compileryar2004-11-181-1/+1
| | | | can detect format errors.
* Fix perror_reply() vs. reply() usage.yar2004-11-182-3/+3
|
* '\n' needs not to appear in reply() strings.yar2004-11-181-3/+3
|
* Log pathname arguments to ftp commands as the user specified them;yar2004-11-181-33/+55
| | | | | | | | | | | add the working directory pathname to the log message if any of such arguments isn't absolute. This has advantage over the old way of logging that an admin can see what users are actually trying to do, and where. The old code was also not too robust when it came to a chrooted session and an absolute pathname. Pointed out by: Nick Leuta MFC after: 2 weeks
* Use S_ISDIR() macro instead of a hand-rolled test.yar2004-11-181-1/+1
|
* getcwd() won't leave a error string in the buffer, unlike getwd().yar2004-11-181-1/+1
|
* Use POSIX functions instead of legacy ones:yar2004-11-171-2/+2
| | | | | getwd() -> getcwd() wait3() -> waitpid()
* Kill more unneeded casts found.yar2004-11-172-4/+4
| | | | Noticed by: Nick Leuta <skynick -at- mail.sc.ru> (some of them)
* Remove 80386 support from the ELF run time linker.jhb2004-11-162-163/+0
|
* Don't invent ways of capitalization orthogonal to the English grammar.yar2004-11-151-2/+2
|
* RFC 959 states that the following codes should be usedyar2004-11-151-3/+5
| | | | | | | | | | for status replies on file system objects: 212 Directory status. 213 File status. Reported by: Oleg Koreshkov <okor -at- zone.salut.ru> MFC after: 1 week
* So do it like we do in usr.bin/tip/tip/Makefile. ;)ru2004-11-141-0/+2
|
* Revert previous commit. As ru explains:schweikh2004-11-141-1/+1
| | | | | | | | | | | In the old world (as the surrounding comment in makefile says), there was the /usr/libexec/ld-elf.so.1 binary which is now a symlink to /libexec/ld-elf.so.1. To symlink, we need to make sure that the _target_ (and the target is /usr/libexec/ld-elf.so.1) doesn't have "schg" flag set. A real solution is to protect the chflags call only if target exists, like we do in usr.bin/tip/tip/Makefile. Requested by: ru
* Avoid an (ignored) error by invoking chflags on the link target, not theschweikh2004-11-141-1/+1
| | | | | | | | symlink. PR: kern/73016 Submitted by: John E. Hein <jhein@timing.com> MFC after: 1 week
* Add knob NO_NIS (fka NO_YP_LIBC) and make world compileable when set.bz2004-11-131-2/+7
| | | | | | | | | | | If turned on no NIS support and related programs will be built. Lost parts rediscovered by: Danny Braniss <danny at cs.huji.ac.il> PR: bin/68303 No objections: des, gshapiro, nectar Reviewed by: ru Approved by: rwatson (mentor) MFC after: 2 weeks
* Using off_t to pass a block size is obvious overkill.yar2004-11-131-2/+2
| | | | | | | The size_t type is better suited for that, particularly because the "blksize" argument is to be passed to malloc() and read(). On 64-bit archs it's more to a style issue, but the good style of coding in C is also important.
* Kill ancient casts to integral types left from the K&R era.yar2004-11-133-9/+9
| | | | They're unneeded and sometimes erroneous now.
* Remove these unused files before any other archs include the same bogusjhb2004-11-126-1057/+0
| | | | file.
* The 32 bit compatability ld-elf32.so.1 cannot use i386_set_ldt() whenpeter2004-11-061-0/+6
| | | | | running on an amd64 kernel. Use the recently exposed direct %fs/%gs set routines instead for the TLS setup of 32 bit binaries.
* Introduce the PRECIOUSPROG knob in bsd.prog.mk, similarru2004-11-032-2/+4
| | | | | | | | to PRECIOUSLIB from bsd.lib.mk. The side effect of this is making installing the world under jail(8) possible by using another knob, NOFSCHG. Reviewed by: oliver
* Fix logxfer() by using realpath(3) instead of playing with getwd(3).yar2004-11-031-4/+8
| | | | | | | | Previously logxfer() used to record bogus pathnames to the log in some cases, namely, when cwd was / or "name" was absolute. Noticed by: Nick Leuta MFC after: 2 weeks
OpenPOWER on IntegriCloud