On the page
http://www.se.freebsd.org/doc/en_US.ISO8859-1/books/handbook/using-localization.html
Syntax is shown as:
language_name:accounts_title:\
:charset=MIME_charset:\
:lang=locale_name:\
:tc=default:
If I look in the file on a newly installed 8.0-RELEASE it shows:
is used when there are several
alternative names for the same object -- this is not used much in
/etc/login.conf, unlike /etc/termcap. By convention, the last name in
a list of alternates like this is a comment rather than a tag for
actual use. See getcap(3) for details.
The first entry
...
Is it the colon or pipe sign that is correct?
/Leslie
The answer is clearly set forth in login.conf(5):
Records in a class capabilities database consist of a number of colon-
separated fields. The first entry for each record gives one or more
names that a record is to be known
, Matthew Seaman
m.sea...@infracaninophile.co.uk wrote:
Probably the latter. The '|' symbol is used when there are several
alternative names for the same object -- this is not used much in
/etc/login.conf, unlike /etc/termcap. By convention, the last name in
a list of alternates like
how can i put in setenv= definition a : character?
for example i would like to set enviroment variable a to b:c in login.conf
thanks
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To
On 6/6/09, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote:
how can i put in setenv= definition a : character?
for example i would like to set enviroment variable a to b:c in login.conf
It's documented in login.conf manual.
--
Paul
___
for example i would like to set enviroment variable a to b:c in login.conf
It's documented in login.conf manual.
indeed i missed that.
Note that since a colon (`:') is used to separate capability entries,
a
`\c' escape sequence must be used to embed a literal colon in the
value
MD5 seems to be compromised by potential collision attacks. So I tried
to figure out how I can use another hash for security purposes when
hashing passwords for local users on a FreeBSD 7/8 box, like root or
local box administration. Looking at man login.conf reveals only three
possible hash
Vanik abazyan wrote:
Help pls
FreeBSD 5.3 sshd _security_path: cannot stat /etc/login.conf:
1st: Please include a descriptive subject - even if it's the same line
as the body.
2nd: Do you have that file? What are the permissions? What action are
you trying to do? Are there other
Hi,
Thanks, I have subscribed to the -questions mailling list.
James
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Lowell Gilbert
Sent: 18 May 2005 20:16
To: James Tucker; [EMAIL PROTECTED]
Subject: Re: Limiting Filesizes with /etc/login.conf
it didn't seem,
from what I have read, that is possible to do much else with the quotas?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Lowell Gilbert
Sent: 19 May 2005 14:16
To: James Tucker
Subject: Re: Limiting Filesizes with /etc/login.conf
James
James Tucker wrote:
Yes, your reply does answer my question, quota'ing does seem to
be a solution but I don't want to restrict from users for possessing
multiples of 10MB files.
I have already implemented quota's to prevent them from taking
up more than their designated home dir space,
This has nothing to do with filesystems, so I redirected the message
to -questions.
[EMAIL PROTECTED] (James Tucker) writes:
I have been trying to set max file size limits for class of users on my
system. I have tried to setup a specific class for this purpose and
while it cap_mkdb's with no
Hi,
I'm seeing somewhat strange behavior in my 4.9 System:
Seems like any changes I make to /etc/login.conf get silently ignored.
Here's what I've done:
I wanted to set an environment varialbe LC_CTYPE in /etc/login.conf
like this
:setenv=MAIL=/var/mail/$,BLOCKSIZE=K,FTP_PASSIVE_MODE=YES
On Fri, Nov 21, 2003 at 12:07:22PM +0100, [EMAIL PROTECTED] wrote:
Seems like any changes I make to /etc/login.conf get silently ignored.
As I understand it, login.conf is used to set capabilities
on a per user class basis to restrict the environment of classes of
users - ie restricting the ttys
the following (as shown
below) in /etc/login.conf, will the system still decrypt the old DES and
MD5 entries, ie. nothing will break in this regard?
:passwd_format=blf:\
# change the password encryption to Blowfish instead of the default md5
Thanks,
Kris
, a suggestion to switch to
blowfish. I am down with that! If I change the following (as shown
below) in /etc/login.conf, will the system still decrypt the old DES and
MD5 entries, ie. nothing will break in this regard?
:passwd_format=blf:\
Correct, but don't forget to rebuild the capability
Zheyu Shen [EMAIL PROTECTED] writes:
this weekend when i was editing /etc/login.conf i noticed a @ behind a few of the
sample entrys, e.g.:
[...]
reading the corresponding man page i could not find out what it means or how it is
used. it seems to substitute a whole lot of limit types
dear list
this weekend when i edited /etc/login.conf i noticed a few sample entries
like:
:requirehome@:\ (line 102)
:ignoretime@:\ (line 131)
:accounted@:\ (line 158)
...
reading the corresponding manpage i could not find out what it mean or how
it is used. it seems to substitute a lot
hello list,
this weekend when i was editing /etc/login.conf i noticed a @ behind a few of the
sample entrys, e.g.:
:requirehome@:\ (line 102)
:ignoretime@:\(line 131)
:accounted@:\ (line 158)
:passwordtime@:\ (line 248
20 matches
Mail list logo
