d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

msgs -p (and maybe other flags, too) gives misleading error messages,

Browse Source 
especially on a new install, where /var/msgs/bounds doesn't exist.  I
        moved my bounds file out of the way to create this before and after
        on a quick 'n' dirty hack, which is probably the 23rd best way to do it,
        but it works:

PR:		6963
Submitted by:	Matthew Fuller <fullermd@mortis.futuresouth.com>
This commit is contained in:
Jordan K. Hubbard 1998-07-07 12:02:59 +00:00
parent 1d86f959b6
commit 0b1778905f
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
usr.bin/msgs/msgs.c
View File

@ -42,7 +42,7 @@ static const char copyright[] =
static char sccsid[] = "@(#)msgs.c 8.2 (Berkeley) 4/28/95";
#endif
static const char rcsid[] =
"$Id$";
"$Id: msgs.c,v 1.9 1997/07/29 06:47:18 charnier Exp $";
#endif /* not lint */
/*
@ -169,6 +169,7 @@ int argc; char *argv[];
int rcback = 0; /* amount to back off of rcfirst */
int firstmsg = 0, nextmsg = 0, lastmsg = 0;
int blast = 0;
struct stat buf; /* stat to check access of bounds */
FILE *bounds;
#ifdef UNBUFFERED
@ -244,6 +245,11 @@ int argc; char *argv[];
* determine current message bounds
*/
snprintf(fname, sizeof(fname), "%s/%s", _PATH_MSGS, BOUNDS);
if (stat(fname, &buf) < 0)
{
perror(fname);
exit(1);
}
bounds = fopen(fname, "r");
if (bounds != NULL) {