Re: pw(8): $ (dollar sign) in username

2002-12-27 Thread Ryan Thompson
Craig Rodrigues wrote to Ryan Thompson: > On Fri, Dec 27, 2002 at 11:35:45AM -0600, Ryan Thompson wrote: > > > Problem is, smb requires a '$' at the end of the username, which > > our pw(8) doesn't allow. > > The same patch which you proposed was suggested

pw(8): $ (dollar sign) in username

2002-12-27 Thread Ryan Thompson
quot;"; + char const *notch = gecos ? ":!@" : ",\t:+&#%^()!@~*?<>=|\\/\""; while (name[l]) { if (strchr(notch, name[l]) != NULL || name[l] < ' ' || name[l] == 127 || - Ryan -- Ryan Thompson <[EMAIL PROTECTED]> SaskNow Technologies -

Re: Who broke "ls" in FreeBSD? and why?

2000-10-31 Thread Ryan Thompson
behaviour is as correct as the behaviour of any other UNIX variant that I am aware of. The problem is not with ls. See my response to your next post (I'll have to type it, first ;-) Hope this helps, - Ryan -- Ryan Thompson <[EMAIL PROTECTED]> Network Administrator, Accounts

Re: Who broke "ls" in FreeBSD? and why?

2000-10-31 Thread Ryan Thompson
hat IS the case, then the -doc people have a change to commit :-) Search permission is required to map pathnames to inodes. That's a requirement of the kernel (and, consequently, of kernel calls) for normal users. > Cheers, > -- JMA > ** Jose M. Alcaide // [EMAIL PROTECTE

Re: Logging users out

2000-10-30 Thread Ryan Thompson
er's session (like processes that they started on a different terminal) b) kill - `ps -axo user,pid | grep user | awk '{print $2}'` Kills every process owned by ``user''. Sending SIGKILL does so in a non-catchable way. c) /sbin/halt is pretty much guaranteed to

Re: Filesystem holes

2000-10-29 Thread Ryan Thompson
Leif Neland wrote to Ryan Thompson and Matt Dillon: > > What will happen, if somebody (possibly you, as mahordomo says), tries to > make a backup of that file. Make sure to use a program that can cope ;-) > Will the copy also be with holes, or would that file suddenly use all 96G

Re: Filesystem holes

2000-10-29 Thread Ryan Thompson
Matt Dillon wrote to Ryan Thompson: > :Hi, Matt! Thanks for the replies. I'll try and keep you interested ;-) > : > :Hmm... Perhaps you're still missing my original point? I'm talking about > :a file with 96GB in addressable bytes (well, probably a bunch of files

Re: Filesystem holes

2000-10-29 Thread Ryan Thompson
Ryan Thompson wrote to Matt Dillon: > Matt Dillon wrote to Ryan Thompson: > > > :> :> storage is rather inefficient for our table of about 2,850,000 members > > :> :> (~2.1 GB total storage). There are 64M possible hash values in our > > :> :> curr

Re: Filesystem holes

2000-10-29 Thread Ryan Thompson
Matt Dillon wrote to Ryan Thompson: > :> :> storage is rather inefficient for our table of about 2,850,000 members > :> :> (~2.1 GB total storage). There are 64M possible hash values in our > :> :> current implementation, and our record size is variable, but could

Re: Filesystem holes

2000-10-29 Thread Ryan Thompson
Matt Dillon wrote to Ryan Thompson and [EMAIL PROTECTED]: > :> Hi all... > :> > :> One the tasks that I have undertaken lately is to improve the efficiency > :> of a couple of storage facilities we use internally, here. Basically, > :> they are moderate-size table

Filesystem holes

2000-10-28 Thread Ryan Thompson
hing the filesystem? :-) - Ryan -- Ryan Thompson <[EMAIL PROTECTED]> Network Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "

Re: Building customized kernel without root passwd

2000-02-29 Thread Ryan Thompson
ssions to build and boot from their own kernel and/or suite of utilities (be it from a floppy or the local drive), assume they have free reign over the entire system, and any network resources root normally has access to. -- Ryan Thompson <[EMAIL PROTECTED]> Systems Administrator, Accounts

Re: Annoying nfsrcv hangs

2000-02-27 Thread Ryan Thompson
Matthew Dillon wrote to Ryan Thompson: > :ps al on my system shows multiple nfsrcv hangs on processes such as df, ls > :and umount. Without any other characteristic problems, the nfs server > : [...] > > I assume the hangs are on the client? Not surprising if its a 3.2 &

Annoying nfsrcv hangs

2000-02-26 Thread Ryan Thompson
I haven't had any longevity problems up until now.. Has anything been built into -CURRENT to address these hangs? It has plagued many in the past, and continues to do so. Yours truly, - Frustrated :-) -- Ryan Thompson <[EMAIL PROTECTED]> Systems Administrator, Account

Re: modem program... Help

2000-02-24 Thread Ryan Thompson
never attempt to parse messages like that. Instead, you should detect carrier in the hardware. -- Ryan Thompson <[EMAIL PROTECTED]> Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK

Re: your mail

2000-01-13 Thread Ryan Thompson
forms. This -hackers list is meant for the more technical array of questions and their responses. "More technical" generally means questions pertaining to the source code of the operating system itself. -- Ryan Thompson <[EMAIL PROTECTED]> 50% Owner, Technical and Accounts Ph

Re: Default minfree performance restrictions?

1999-12-22 Thread Ryan Thompson
Hi, Mark, Thanks for the reply. On Thu, 23 Dec 1999, Mark Newton wrote: > On Wed, Dec 22, 1999 at 07:25:39PM -0600, Ryan Thompson wrote: > > The idea has merit, but you might need to increase the size of your > cylinder groups to compensate if you lower the MINFREE threshhold whi

Re: Default minfree performance restrictions?

1999-12-22 Thread Ryan Thompson
e just gone for the holidays. Seriously, though, folks, does my idea make any sense at all? Thanks, - Ryan On Mon, 20 Dec 1999, Ryan Thompson wrote: > Hello all, > > After creating some larger slices than I'm used to, I finally felt the > full force of a default 8% minfree

Default minfree performance restrictions?

1999-12-20 Thread Ryan Thompson
implementation to allow for the extra parameter for each filesystem... And would definitely qualify as an "invasive" change. Food for thought, though :-) Any insights? I suppose I could just go ahead and try it, but, before I end up doing a reinstall (cd /usr/src && make blowupworl