Thread View: alt.os.linux.slackware
4 messages
4 total messages
Started by Dieu Phan
Sun, 11 Jan 2004 02:14
err. at root account when typing #man [command]
Author: Dieu Phan
Date: Sun, 11 Jan 2004 02:14
Date: Sun, 11 Jan 2004 02:14
46 lines
3332 bytes
3332 bytes
Hello everyone,
My slackBox has an err. on root account as following:
If I am typing for eg.
'#man kill' then its output exposed as:
KILL(1) Linux Programmer�<80><99>s Manual KILL(1)
NAME
kill �<88><92> terminate a process
SYNOPSIS
kill [ �<88><92�<88><92>s signal | �<88><92�<88><92>p ] [ �<88><92�<88>
<92>a ] [ �<88><92�<88><92>�<88><92�<88><92> ] pid ...
kill �<80><90�<80><90>l [ signal ]
DESCRIPTION
The command kill sends the specified signal to the speci
fied process or process group. If no signal is specified,
the TERM signal is sent. The TERM signal will kill pro
cesses which do not catch this signal. For other pro
cesses, it may be necessary to use the KILL (9) signal,
since this signal cannot be caught.
Most modern shells have a builtin kill function, with a
usage rather similar to that of the command described
here. The �<80><98>�<80><90>a�<80><99> and �<80><98>�<80><90>p�<80><99> o
ptions, and the possibility to
specify pids by command name is a local extension.
lines 1-23
etc...
//END
Notes:
1. The err. only happens on root account
2. it occurs with some commands only such as 'kill', 'pppd' and so on
Almost of commands are appearing normal
3. normal users do not have err. like that
4. My locale: LANG=en_US.ISO8859-1. However, b4 i changed locale to
en_AU.UTF-8 default of LANG=C. After I switched to UTF-8 and back to
LANG=C, problem happens. Even tho' I changed back to default, or
en_US.ISO8859-1.
has Anyone experienced w/ this kind of err. pls help me. I am very
appreciated.
kind regards
--
:: Dieu Phan :: Slackware drives me to slack, where? ::
:: Slackware Linux-9.1/kernel-2.6.1/AMD XP1800+ ::
Re: err. at root account when typing #man [command]
Author: Ross Axe
Date: Sun, 11 Jan 2004 06:30
Date: Sun, 11 Jan 2004 06:30
50 lines
3517 bytes
3517 bytes
Dieu Phan wrote: > Hello everyone, > My slackBox has an err. on root account as following: > If I am typing for eg. > '#man kill' then its output exposed as: > KILL(1) Linux Programmer�<80><99>s Manual KILL(1) > > NAME > kill �<88><92> terminate a process > > SYNOPSIS > kill [ �<88><92�<88><92>s signal | �<88><92�<88><92>p ] [ �<88><92�<88> > <92>a ] [ �<88><92�<88><92>�<88><92�<88><92> ] pid ... > kill �<80><90�<80><90>l [ signal ] > > DESCRIPTION > The command kill sends the specified signal to the speci > fied process or process group. If no signal is specified, > the TERM signal is sent. The TERM signal will kill pro > cesses which do not catch this signal. For other pro > cesses, it may be necessary to use the KILL (9) signal, > since this signal cannot be caught. > > Most modern shells have a builtin kill function, with a > usage rather similar to that of the command described > here. The �<80><98>�<80><90>a�<80><99> and �<80><98>�<80><90>p�<80><99> o > ptions, and the possibility to > specify pids by command name is a local extension. > lines 1-23 > etc... > //END > Notes: > 1. The err. only happens on root account > 2. it occurs with some commands only such as 'kill', 'pppd' and so on > Almost of commands are appearing normal > 3. normal users do not have err. like that > 4. My locale: LANG=en_US.ISO8859-1. However, b4 i changed locale to > en_AU.UTF-8 default of LANG=C. After I switched to UTF-8 and back to > LANG=C, problem happens. Even tho' I changed back to default, or > en_US.ISO8859-1. > has Anyone experienced w/ this kind of err. pls help me. I am very > appreciated. > kind regards > HINT: Only root has access to /var/man/cat*/ HTH Ross
Re: err. at root account when typing #man [command]
Author: Dieu Phan
Date: Mon, 12 Jan 2004 02:37
Date: Mon, 12 Jan 2004 02:37
64 lines
4233 bytes
4233 bytes
On Sun, 11 Jan 2004 06:30:57 +0000, Ross Axe wrote: > Dieu Phan wrote: >> Hello everyone, >> My slackBox has an err. on root account as following: >> If I am typing for eg. >> '#man kill' then its output exposed as: >> KILL(1) Linux Programmer�<80><99>s Manual KILL(1) >> >> NAME >> kill �<88><92> terminate a process >> >> SYNOPSIS >> kill [ �<88><92�<88><92>s signal | �<88><92�<88><92>p ] [ �<88><92�<88> >> <92>a ] [ �<88><92�<88><92>�<88><92�<88><92> ] pid ... >> kill �<80><90�<80><90>l [ signal ] >> >> DESCRIPTION >> The command kill sends the specified signal to the speci >> fied process or process group. If no signal is specified, >> the TERM signal is sent. The TERM signal will kill pro >> cesses which do not catch this signal. For other pro >> cesses, it may be necessary to use the KILL (9) signal, >> since this signal cannot be caught. >> >> Most modern shells have a builtin kill function, with a >> usage rather similar to that of the command described >> here. The �<80><98>�<80><90>a�<80><99> and �<80><98>�<80><90>p�<80><99> o >> ptions, and the possibility to >> specify pids by command name is a local extension. >> lines 1-23 >> etc... >> //END >> Notes: >> 1. The err. only happens on root account >> 2. it occurs with some commands only such as 'kill', 'pppd' and so on >> Almost of commands are appearing normal >> 3. normal users do not have err. like that >> 4. My locale: LANG=en_US.ISO8859-1. However, b4 i changed locale to >> en_AU.UTF-8 default of LANG=C. After I switched to UTF-8 and back to >> LANG=C, problem happens. Even tho' I changed back to default, or >> en_US.ISO8859-1. >> has Anyone experienced w/ this kind of err. pls help me. I am very >> appreciated. >> kind regards >> > > HINT: Only root has access to /var/man/cat*/ > > HTH > > Ross Dear Ross, Could you give me more hints about how to fix that kind of problem. I #find / -name kill and saw it in /car/man/cat1 b4, and knew mode 700 in /var/man/cat* but still wondering why in the same cat1 dir. [some commands] appear output normally when #man , some are not? Do i need to edit /usr/lib/man.conf? where can I put LESSCHARSET=latin1 in root environment? thanks and kind regards -- :: Dieu Phan :: Slackware drives me to slack, where? :: :: Slackware Linux-9.1/kernel-2.6.1/AMD XP1800+ ::
Re: err. at root account when typing #man [command]
Author: Dieu Phan
Date: Mon, 12 Jan 2004 06:28
Date: Mon, 12 Jan 2004 06:28
57 lines
3782 bytes
3782 bytes
Ross Axe wrote: > Dieu Phan wrote: > >> Hello everyone, >> My slackBox has an err. on root account as following: >> If I am typing for eg. >> '#man kill' then its output exposed as: >> KILL(1) Linux Programmer�<80><99>s Manual KILL(1) >> >> NAME >> kill �<88><92> terminate a process >> >> SYNOPSIS >> kill [ �<88><92�<88><92>s signal | �<88><92�<88><92>p ] [ >> �<88><92�<88> >> <92>a ] [ �<88><92�<88><92>�<88><92�<88><92> ] pid ... >> kill �<80><90�<80><90>l [ signal ] >> >> DESCRIPTION >> The command kill sends the specified signal to the speci >> fied process or process group. If no signal is specified, >> the TERM signal is sent. The TERM signal will kill pro >> cesses which do not catch this signal. For other pro >> cesses, it may be necessary to use the KILL (9) signal, >> since this signal cannot be caught. >> >> Most modern shells have a builtin kill function, with a >> usage rather similar to that of the command described >> here. The �<80><98>�<80><90>a�<80><99> and >> �<80><98>�<80><90>p�<80><99> o >> ptions, and the possibility to >> specify pids by command name is a local extension. >> lines 1-23 etc... >> //END >> Notes: >> 1. The err. only happens on root account >> 2. it occurs with some commands only such as 'kill', 'pppd' and so on >> Almost of commands are appearing normal >> 3. normal users do not have err. like that >> 4. My locale: LANG=en_US.ISO8859-1. However, b4 i changed locale to >> en_AU.UTF-8 default of LANG=C. After I switched to UTF-8 and back to >> LANG=C, problem happens. Even tho' I changed back to default, or >> en_US.ISO8859-1. >> has Anyone experienced w/ this kind of err. pls help me. I am very >> appreciated. >> kind regards >> > > HINT: Only root has access to /var/man/cat*/ > > HTH > > Ross > Thanks Ross I got that.. well they are formatted and stored in cat*, all I do is to use option man -c kill to overwrite the old one. thanks
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads