Date: Wed, 29 Dec 1999 14:19:13 -0800 From: "Duke Normandin" <01031149@3web.net> To: "freebsd-questions" <freebsd-questions@FreeBSD.ORG> Subject: Re: kill -HUP 1 Message-ID: <001401bf524b$11231580$6a9dc5d1@webserver>
next in thread | raw e-mail | index | archive | help
-----Original Message----- From: aunty <aunty@comcen.com.au> To: Duke Normandin <01031149@3web.net> Cc: freebsd-questions <freebsd-questions@FreeBSD.ORG> Date: Wednesday, December 29, 1999 2:40 AM Subject: Re: kill -HUP 1 >On Tue, Dec 28, 1999 at 10:24:50PM -0800, Duke Normandin wrote: >> I can't seem to get kill -HUP 1 to work.....nothing happens - no error >> messages, nothing. > >That's perfectly correct! Unix complains if something is wrong, and >leaves you peacefully in the dark in case of success. You had succcess. >If you had been editing /etc/ttys and had also remembered to make the >devices, you'd magically have your extra virtual consoles (or whatever) >after such a reassuring (?) silence following that command. > >> I can't figure out what I'm doing wrong. > >The second most important thing is to avoid making any assumptions. >The most important thing is not to assume you've made a mistake, and >in fact that was the only thing you did wrong. Then it got worse :-) > >> So I have been doing: >> >> kill 1 -l > >Ugh... (what you typed exactly is more apparent from the description below) > >> It logs out of csh and asks me for the complete path to my shell or >> return for sh. I press "return"...I get a sh prompt, then I do "exit". >> Then and only then is the system re-initialized. I have no idea what I'm >> doing....but it beats re-booting. > >No it doesn't, it _is_ a kind of rebooting. Also it confuses the hell >out of people who try to answer your question :-) I suppose I should have been more precise as to what I was doing and wanted to do: TERM=cons25 In /etc/rc.conf, I've been experimenting with various fonts. I now understand from a reply to a previous question of mine, that the fonts I use must be "matched" to the correct termcap console. So I've been editting ttys, trying out cons25l1, cons25w, etc etc. Before I got the nerve to try "kill -HUP 1", I simply did "shutdown -r now", to re-initialize the system. When I first tried "kill -HUP 1, I _did not_ expect a "pat on the back" from the system, congradulating me on a successful "kill" ;-) -- rather I was looking for the problem's symptoms to have disappeared, or different symptom's for the same problem. Nothing happened; nothing changed with my consoles, leading me to believe that I had screwed up the command somehow. How I came across kill 1 -l, I can't recall. However, it did exactly what I expected -- re-initialize the system (but w/o the device probing). One of the problems I'm trying to fix is the rendering of the "window" borders in "midc" --- using cons25 with the wrong font, or visa versa, results in a bunch of "garbage" characters for the window border instead of lines. Soooo, I editted the said "ttys" file, hoping to stumble on a configuration that would render correctly. In order to test it out, I of course have to re-init! I was hoping that it would be as simple as doing "source .cshrc" when I'm messing with ~/ .cshrc. So, bottom-line, how do I re-init the system without device probing -- i.e. w/o total reboot? As a side-bar guys, what, in your experience, is the best fonts to use in Unix, to preclude misinterpretation of 1 (one), l (ell) and I (uppercase i). In win95, I now use Verdana, and the distinction is now clear for me in this environment. thanks....duke To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001401bf524b$11231580$6a9dc5d1>