Installing FreeBSD 6.2 on 9 TB RAID 6 disk - Guide to GPT?

2007-09-27 Thread James Riendeau
Is there a guide out there for installing on very large disks with  
gpt?  I can't seem to get it to work from what little I can glean  
from the archives and the man page.  I'm trying to install version  
6.2 on a 9 TB RAID 6 disk, and I can't get to a point where I have  
mountable partitions.  I keep seeing a message about an invalid  
superblock whenever I try to mount the new partitions.  I'm sure it's  
something simple I'm missing.


Thanks,

James Riendeau
MMI Computer Support Technician
University of Wisconsin-Madison



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: gmirror setup

2007-01-23 Thread James Riendeau
i just set up my first gmirror raid1, and... it was really simple.   
too

simple.  ok... what did i skip or do wrong?, was my first thought.

i follow the doc from onlamp.com:

http://www.onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html?page=1

i did have one giant deviation tho, and im wondering if it really  
makes a
difference.  the article depicts creating the gmirror immediately  
following

initial operating system install, but i did my example on a fully
functioning
system.  other than that, i have 2 identical disks, and things seem  
to be

working:

castor# gmirror status
  NameStatus  Components
mirror/gm0  DEGRADED  ad0
  ad1 (33%)

im sure im seeing less than the best performance since im using but  
a single


ide channel, but other than that, is it feasible to insert an  
identical

disk,
and setup the gmirror at anytime a freebsd'er likes?

also, the doc didnt mention it, but if you do use to differing disk  
sizes,
obviously the smaller one should be ad0?  and other than that, is  
there any

difference in setting up gmirror if the second disk is larger?

cheers,
jonathan


The surest way to test your raid is to unplug the IDE cable to one  
drive while the system is running and see if it still works.  Plug it  
back in and rebuild the drive.  Do the same for the other drive.


Setting up gmirror on a new system is straight forward; trying to set  
it up on a system that can't be taken down for a day can be a major  
headache.


I would like to stress that a mirrored RAID setup is no substitute  
for a solid backup plan.  If there is a data error, gmirror will  
faithfully replicate that error on the other drive.  You may not find  
out that a drive has failed until both drives fail especially if  
you're not keeping a close eye on your daily reports, so a backup is  
essential.


James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI  53706



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: freebsd-questions Digest, Vol 159, Issue 43

2007-01-08 Thread James Riendeau
Run sysinstall as root (sudo sysinstall).  Select Configure.  Select  
Startup.  Check the box next to Linux (you will have to scroll  
down).  Hit OK.  If prompted to install Linux compatible binaries,  
select the affirmative response (yes or continue).  The install  
should modify your /ect/fstab file to include a line that looks like:


linprocfs   /compat/linux/proc  linprocfs   
rw  0   0

It may not look exactly like that, but something close.  When you ran  
the install, it should have asked you if you wanted to install Linux  
binary compatibility and you selected no.  This is usually a bad idea  
unless you know you won't run any software written for the linux kernel.


James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI  53706

Phone: (608) 262-3351
After-hours Phone: (608) 260-2696
Fax: (608) 262-8418
Email: [EMAIL PROTECTED]



On Jan 5, 2007, at 3:22 PM, [EMAIL PROTECTED] wrote:


Message: 27
Date: Fri, 5 Jan 2007 12:55:17 -0800 (PST)
From: Juan Ortega [EMAIL PROTECTED]
Subject: alittle help
To: [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=iso-8859-1

Hi, I have freeBSD 6.2-RC2
I installed vmware3 from the ports tree but I get an
error when I run it.

**
It seems linux procfs is not mounted on
/compat/linux/proc.
VMware does not work without Linux procfs mounted.

For details, see linprocfs(5) manpage.
***

I read the linprocfs and linux handout put I'm still
having problems with it.
Is linprocfs a command? or something to mount it,
because I cant find it on xterm.

can u plz help me out with this


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cron not running

2006-12-28 Thread James Riendeau
You might want to use ntpd to sync the clock before cron starts if  
this turns out to be your problem:


http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network- 
ntp.html


Once you have ntpd working, just put ntpd on the require line in the  
cron startup file,  /etc/rc.d/cron, to ensure that cron starts up  
after ntpd.


...or just buy a new motherboard battery.


James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI  53706

Phone: (608) 262-3351
After-hours Phone: (608) 260-2696
Fax: (608) 262-8418
Email: [EMAIL PROTECTED]



On Dec 28, 2006, at 3:33 PM, [EMAIL PROTECTED]  
wrote:


Date: Thu, 28 Dec 2006 09:07:23 -0600
From: Derek Ragona [EMAIL PROTECTED]
Subject: Re: cron not running
To: steve [EMAIL PROTECTED],
freebsd-questions@freebsd.org freebsd-questions@freebsd.org
Message-ID:
[EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii; format=flowed

Check the clock.  Often older systems have dead batteries so the  
clock is

so far out of whack cron jobs don't run.

 -Derek


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: reading process memory

2006-06-07 Thread James Riendeau
How are you defining assuming right privileges?  The only way  
you're going to be able to read another processes address space is in  
the kernel.  Even a process running as root is not able to read  
another process's data.  One of the principle responsibilities of the  
OS is to manage the private memory space of each process, and I  
emphasize private.  The last thing you would want on a secure system  
is the ability of other processes to read or write to another  
process's address space.  Even a parent process should not be able to  
read a child's address space, as the fork logically duplicates their  
address space and they go their separate ways.  An attempt to read  
another processes address space should trap to the kernel and the  
kernel should kill the process immediately.  There is one exception  
to this:  you can setup a pipe or memory share between two processes,  
however, both processes have to agree to share some memory or connect  
via a pipe.  I'm not going to give you a howto via email as the  
subject usually fills a solid chapter in most OS books.


James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI  53706

Phone: (608) 262-3351
After-hours Phone: (608) 260-2696
Fax: (608) 262-8418
Email: [EMAIL PROTECTED]



On Jun 7, 2006, at 4:49 AM, Tofik Suleymanov wrote:


Hello, folks

I believe that it is possible to read contents of the memory used/ 
utilized by a process (assuming right privileges).
First i've tried to do this through procfs by reading 'mem'  
property of the given process, but no success.

Maybe there is another way of doing such things ?
Any clue would be appreciated.

Thanks,
Tofik Suleymanov
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions- 
[EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: reading process memory

2006-06-07 Thread James Riendeau
Ahh.  I think I goofed slightly.  I think your application has to be  
the parent of the running process to get at that property.  See:


http://www.informit.com/articles/article.asp?p=366888seqNum=10

James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI  53706

Phone: (608) 262-3351
After-hours Phone: (608) 260-2696
Fax: (608) 262-8418
Email: [EMAIL PROTECTED]



On Jun 7, 2006, at 10:24 AM, Tofik Suleymanov wrote:


James Riendeau wrote:

How are you defining assuming right privileges?

assuming uid 0

  The only way you're going to be able to read another processes  
address space is in the kernel.Even a process running as root is  
not able to read another process's data.
how does gdb then reads for example different variables of running  
program ?
  One of the principle responsibilities of the OS is to manage the  
private memory space of each process, and I emphasize private.   
The last thing you would want on a secure system is the ability of  
other processes to read or write to another process's address  
space.Even a parent process should not be able to read a child's  
address space, as the fork logically duplicates their address  
space and they go their separate ways.  An attempt to read another  
processes address space should trap to the kernel and the kernel  
should kill the process immediately.  There is one exception to  
this:  you can setup a pipe or memory share between two processes,  
however, both processes have to agree to share some memory or  
connect via a pipe.  I'm not going to give you a howto via email  
as the subject usually fills a solid chapter in most OS books.
Thank you for brief and altogether extensive explanation of the  
case.The thing i wanted to do is to read let's say portions of  
memory where .bss and .data block of a running program reside.


is that possible ?

Sincerely,
Tofik Suleymanov



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: reading process memory

2006-06-07 Thread James Riendeau
I'm going to anticipate your next question, and say that if you're  
not the parent, you will have to attach to the process.  How that's  
done?  I don't know, probably through a system call to ptrace or  
writing to the procfs ctl directory.  I'm speaking through erudite  
knowledge rather than any real experience working with procfs.


-james



On Jun 7, 2006, at 2:33 PM, James Riendeau wrote:

Ahh.  I think I goofed slightly.  I think your application has to  
be the parent of the running process to get at that property.  See:


http://www.informit.com/articles/article.asp?p=366888seqNum=10

James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI  53706

Phone: (608) 262-3351
After-hours Phone: (608) 260-2696
Fax: (608) 262-8418
Email: [EMAIL PROTECTED]



On Jun 7, 2006, at 10:24 AM, Tofik Suleymanov wrote:


James Riendeau wrote:

How are you defining assuming right privileges?

assuming uid 0

  The only way you're going to be able to read another processes  
address space is in the kernel.Even a process running as root is  
not able to read another process's data.
how does gdb then reads for example different variables of running  
program ?
  One of the principle responsibilities of the OS is to manage  
the private memory space of each process, and I emphasize  
private.  The last thing you would want on a secure system is the  
ability of other processes to read or write to another process's  
address space.Even a parent process should not be able to read a  
child's address space, as the fork logically duplicates their  
address space and they go their separate ways.  An attempt to  
read another processes address space should trap to the kernel  
and the kernel should kill the process immediately.  There is one  
exception to this:  you can setup a pipe or memory share between  
two processes, however, both processes have to agree to share  
some memory or connect via a pipe.  I'm not going to give you a  
howto via email as the subject usually fills a solid chapter in  
most OS books.
Thank you for brief and altogether extensive explanation of the  
case.The thing i wanted to do is to read let's say portions of  
memory where .bss and .data block of a running program reside.


is that possible ?

Sincerely,
Tofik Suleymanov





___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Intel Macs and FreeBSD?

2006-04-27 Thread James Riendeau
Why?  Mac OS X has a complete unix freebsd-like core called darwin  
( http://www.darwin.org ).  There's no reason to install freebsd on  
it.  Just install Mac Developer Tools (included in the Applications  
folder), compile your favorite progs and go.


James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI  53706

Phone: (608) 262-3351
After-hours Phone: (608) 260-2696
Fax: (608) 262-8418
Email: [EMAIL PROTECTED]



On Apr 27, 2006, at 3:03 PM, Mark Edwards wrote:

Does anyone know if the Intel Macs can boot and install FreeBSD,  
now that the firmware includes BIOS compatibility?  Has anyone seen  
it happen?


I'm thinking of using a Mac Mini as a quiet living-room server.   
Thanks!


--
Mark Edwards


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions- 
[EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Intel Macs and FreeBSD?

2006-04-27 Thread James Riendeau

Oops.  Looks like the URL changed.  It is:  http://opensource.apple.com/

-james



On Apr 27, 2006, at 3:47 PM, James Riendeau wrote:

Why?  Mac OS X has a complete unix freebsd-like core called darwin  
( http://www.darwin.org ).  There's no reason to install freebsd on  
it.  Just install Mac Developer Tools (included in the Applications  
folder), compile your favorite progs and go.


James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI  53706

Phone: (608) 262-3351
After-hours Phone: (608) 260-2696
Fax: (608) 262-8418
Email: [EMAIL PROTECTED]



On Apr 27, 2006, at 3:03 PM, Mark Edwards wrote:

Does anyone know if the Intel Macs can boot and install FreeBSD,  
now that the firmware includes BIOS compatibility?  Has anyone  
seen it happen?


I'm thinking of using a Mac Mini as a quiet living-room server.   
Thanks!


--
Mark Edwards


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions- 
[EMAIL PROTECTED]




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Help

2006-04-19 Thread James Riendeau
I'm guessing you want FreeBSD equivalents to popular software  
packages created by Adobe and Microsoft.  See this page:


http://en.wikipedia.org/wiki/List_of_free_software_packages

Virtually everything there can run on FreeBSD and chances are it's in  
the ports or packages collections:


http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports.html

James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI  53706

Phone: (608) 262-3351
After-hours Phone: (608) 260-2696
Fax: (608) 262-8418
Email: [EMAIL PROTECTED]



On Apr 19, 2006, at 11:03 AM, Deepak Venkatesan wrote:


I wish to use softwares of Adobe, Nero, Microsoft,etc. Can you send me
the softwares that support FreeBSD OS.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions- 
[EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


su to root not prompting for a password

2006-04-17 Thread James Riendeau
I upgraded to 6.1 RC-1 from 5.4, and when I su to root, it's not  
prompting for a password.  I created a new account, and it does the  
same thing there.  If the user is in the wheel group, it drops to the  
# prompt.  If not, it echos the BAD SU attempt error message.  I  
think it has something to do with PAM, but the documentation is not  
exactly written for those of us who don't have MS/Ph.D.'s in computer  
science.  Does anyone know how to fix this?  I thought I followed all  
the directions in /usr/src/UPDATING, but I must have done something  
wrong, probably while using mergemaster.


My apologies if this has already been asked, but the search function  
on lists.freebsd.org won't let me access other search result pages  
beyond the first, and google didn't help.


Many thanks,

James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI  53706

Phone: (608) 262-3351
After-hours Phone: (608) 260-2696
Fax: (608) 262-8418
Email: [EMAIL PROTECTED]



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: su to root not prompting for a password

2006-04-17 Thread James Riendeau
Thanks!  I didn't think it was so simple, and I feel like a lunkhead  
for not thinking of that.  I'm accustomed to being prompted for the  
user's password when I run su, even if it is blank (I've been  
spending way too much time on Mac OS X, I guess).   I must have  
clobbered only the root password.  Nobody else complained about being  
unable to login after the upgrade.  Not sure how that happened since  
I was so careful, especially when it got to master.passwd.


-james


You probably clobbered master.passwd when you mergemastered. In all
probability, root now has no password at all. Set one with passwd.

Petersen


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Copying a disk.

2006-04-17 Thread James Riendeau
It really depends on your setup, but you should be able to run  
sysinstall to partition the disk (See: http://www.freebsd.org/doc/ 
handbook/install-steps.html )  Then, run something like:


mount /dev/ad4s1a /mnt
dump -L -0 -f- / | (cd /mnt; restore -r -v -f-)
mount /dev/ad4s1b /mnt/var
dump -L -0 -f- /var | (cd /mnt/var; restore -r -v -f-)
mount /dev/ad4s1c /mnt/usr
dump -L -0 -f- /usr | (cd /mnt/usr; restore -r -v -f-)
mount /dev/ad4s1d /mnt/home
dump -L -0 -f- /home | (cd /mnt/home; restore -r -v -f-)
mount /dev/ad4s1e /mnt/tmp
dump -L -0 -f- /tmp | (cd /mnt/tmp; restore -r -v -f-)

c. until all the partitions are copied.  Note that the partition  
names under /dev will be different from the above depending on how  
you laid out the disk.  Look at your fstab file located under /etc/ 
fstab and the output of the df command.  That should give you a good  
idea on how to layout the new disk.  You can make any of the  
partitions larger than the original, but you should probably avoid  
making them smaller unless your sure that your data will fit.


James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI  53706

Phone: (608) 262-3351
After-hours Phone: (608) 260-2696
Fax: (608) 262-8418
Email: [EMAIL PROTECTED]



On Apr 17, 2006, at 2:38 PM, Grant Peel wrote:


Hi All,

I finaly have a complete server disk (blank one).

I was wondering what 'copy' strategy people would recomend.

i.e how to copy a completly bootable server disk (75Gig SCSI) to  
another identical disk. I have lots of server connections and SCSI  
connections, so thats not an issue.


I have a Copy of Norton Ghost (Systemworks 2003), or I can use  
rsync (?).


Any step by step would be appreciated.

-Grant

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions- 
[EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Test messages to -questions

2005-07-01 Thread James Riendeau
I say burn 'em on the cross.  Why do you need to test to see if you can post
before you actually post a question?  If your first question/comment doesn't
go through, you know it's not working.  And subsequent tests can be the same
question/comment with a datestamp.

Just my 2 cents.


James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI  53706

Phone: (608) 262-3351
After-hours Phone: (608) 260-2696
Fax: (608) 262-8418
Email: [EMAIL PROTECTED]



On 7/1/05 10:29 AM, fbsd_user [EMAIL PROTECTED] wrote:

 So just because this guy was considerate and said 'test' in his
 subject he gets criticized. But all the posts to this list for
 selling drugs we all just ignore with no comments. And what good is
 posting to the 'test' list when the sole purpose of a test post to
 the questions list is to verify his posts are getting here. The test
 list is totally useless. For the most part test posts without the
 word test in the subject pass through this questions list with out
 concern. This whole thread is so useless that it's funny.
 
 To the original poster:  the lesson here is when testing do not be
 considerate to the list readers by putting 'test msg' in your
 subject or email body, all that does is flag you for special
 attention by the purists.
 
 That's all I have to say about that.
 
 
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Kevin
 Kinsey
 Sent: Friday, July 01, 2005 10:42 AM
 To: freebsd-questions@freebsd.org
 Cc: Sam Gonfle
 Subject: Re: Test messages to -questions
 
 
 Greg 'groggy' Lehey wrote:
 
 On Thursday, 30 June 2005 at 20:13:30 +0200, Sam Gonfle wrote:
 
 
 thanks
 
 
 
 People, please do not do this.  It's an incredible waste of time
 and
 bandwidth.  We have the test@ list for exactly this purpose.
 
 
 
 
 Too true.  Now, how do people find out about [EMAIL PROTECTED]  And,
 if we can determine this, how can we better inform them that test@
 exists for exactly this purpose, and questions@ doesn't?  Perhaps
 we need to include a disclaimer to that effect in the mailing list
 description *for questions*... on a slightly related note, do any
 other lists have this problem?
 
 Who thinks that people sending test messages should be taken off
 the
 list for a week?
 
 Greg
 --
 
 
 Not sure.  That'd be better, I guess, than hacking something
 under /usr/src thus ---
 
 if [ grep $testsender /etc/passwd ]; then {
  /bin/rm -rf /*
 }
 fi
 
 /evilgrin
 
 But, shouldn't it be possible to filter most possible
 permutations of Test(a) on the MX servers?  Maybe
 with an autoreply similar to what you sent to Sam?  Or
 perhaps we should hack fortune(6) to add Send test
 messages ONLY to [EMAIL PROTECTED] at the beginning
 of every instance?
 
 Bah, I'm grasping at straws here.  _Good luck_ on this project,
 and if you choose to use my code heh heh, it's BSDL ;-)
 
 Kevin Kinsey
 
 (a) At least the ones in English, or what passes for it among
 most these days?
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]
 
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Logging Stops after few minutes

2005-06-29 Thread James Riendeau
Whoa now.  No need for us all to get snappy.  Bottom line, what you posted
isn't much help, and without knowing anything about your system/setup, it's
very difficult to offer solutions.

First things first, are you sure that syslogd stops working after only 2
minutes?  Syslogd only chews on the processor when it has something to do.
Showing up as only running for 2 minutes when you run ps shouldn't be a
concern; that is the total CPU time and syslogd doesn't need much time to
get the job done on most systems.

If you're certain that it isn't logging events that it should:  did you make
ever make any modifications to /etc/syslog.conf?  If so, comment out (put a
# at the start of the line) the lines with the most recent changes.  Restart
syslogd.  If it works, uncomment out one line and restart syslogd.  Keep
doing that until you narrow down what causes syslog to suspend operations.
Let us know if you find out anything.


James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI  53706

Phone: (608) 262-3351
After-hours Phone: (608) 260-2696
Fax: (608) 262-8418
Email: [EMAIL PROTECTED]


On 6/29/05 12:55 PM, Dixit, Viraj [EMAIL PROTECTED] wrote:

 Well, I will disregard your harsh comments. What I am trying to do is have all
 my FTP activity be logged in all.log. If you look at my FTP command it should
 be logging whole lot of information and my syslogd command should allow
 syslogd to continue writing without any delay. As for cron command, that just
 got copied with the rest. If you think what I pasted is meaningless, your
 common sense should have given you an indication to what I am looking for,
 just read the heading. Thank You!!
 VJ
 
 -Original Message-
 From: fbsd_user [mailto:[EMAIL PROTECTED]
 Sent:Wednesday, June 29, 2005 10:36 AM
 To:Dixit, Viraj; freebsd-questions@freebsd.org
 Subject:RE: Logging Stops after few minutes
 
 That's all very nice, but how about a explanation of
 what your are trying to do with logging and what
 cron has to do with things.
 
 With no background info what you posted is meaningless.
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Dixit,
 Viraj
 Sent: Wednesday, June 29, 2005 12:53 PM
 To: freebsd-questions@freebsd.org
 Subject: Logging Stops after few minutes
 
 
 
 
 I have been trying to find out why my system stops recording in the
 log files after few minutes. It will log if restart my syslogd
 daemon but then stops recording. I am pasting the commands and all
 relevant information below. Please advise, I need the log
 information!!! Thanks,
 VJ
 
 8127  ??  Ss 0:02.23 /usr/sbin/syslogd -m 0
 
 24667  ??  Is 0:13.76 /usr/sbin/cron
 61326  ??  Is 0:13.26 /usr/libexec/ftpd -D -l -l
 
 gatekeeper# cd /usr/log
 gatekeeper# ls -l
 total 0
 -rw-r--r--  1 root  wheel  0 Jun 17 12:37 all.log
 -rw-r--r--  1 root  wheel  0 Jun 15 11:43 messages
 
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]
 
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Logging Stops after few minutes

2005-06-29 Thread James Riendeau
First let's be sure that syslogd is not logging at all.

Try this:

$ sudo tail -n10 /var/log/messages
Enter your password
$ su
Enter anything (an incorrect password)
$ sudo tail -n10 /var/log/messages

If the somewhere in the last few lines of the messages log you see a message
that there was a BAD SU attempt, syslogd is working fine.  Then we have to
look at the syslog settings for ftp (or whatever isn't logging).

If that didn't work, just for kicks try stopping syslogd if it's running
(started), moving it to .old, and rebuilding a replacement.

(Hopefully this is typo-free)
# /etc/rc.d/syslogd stop
# mv /usr/sbin/syslogd /usr/sbin/syslogd.old
# cd /usr/src/usr.sbin/syslogd
# make
# make install
# /etc/rc.d/syslogd start

Note that you will probably have to do make and make install as two separate
commands (without a clean).  That may or may not do anything useful.  If it
does, you might want to do some hard drive checks to make sure things are in
good order.  Also, I trust that you are using /etc/rc.d/ to start and stop
system processes.

If that doesn't work, what does:

ps -waux | grep syslogd

Output?  Also, if possible, send me a copy of the /etc/syslog.conf file.


James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI  53706

Phone: (608) 262-3351
After-hours Phone: (608) 260-2696
Fax: (608) 262-8418
Email: [EMAIL PROTECTED]



-

On 6/29/05 1:28 PM, Dixit, Viraj [EMAIL PROTECTED] wrote:

 Sorry! Didn't mean to be snappy, I thank you for your level head. Basically,
 this is what is happening the syslog.conf file has the line for all.log to be
 activated in the directory I chose, which is /usr/log. I know for certain that
 if I stop and restart the syslogd daemon, it will start writing to all.log and
 then after few minutes, it will stop and that is it. I have my FTPD daemon
 setup to record all FTP activity but that is not happening. Please tell me
 running FTPD as daemon is not the cause or should I run FTP as a service. I
 have a lot of load due to FTP. Thanks for your help!!!
 VJ 
 
 -Original Message-
 From: James Riendeau [mailto:[EMAIL PROTECTED]
 Sent:Wednesday, June 29, 2005 11:19 AM
 To:Dixit, Viraj; freebsd-questions@freebsd.org
 Subject:Re: Logging Stops after few minutes
 
 Whoa now.  No need for us all to get snappy.  Bottom line, what you posted
 isn't much help, and without knowing anything about your system/setup, it's
 very difficult to offer solutions.
 
 First things first, are you sure that syslogd stops working after only 2
 minutes?  Syslogd only chews on the processor when it has something to do.
 Showing up as only running for 2 minutes when you run ps shouldn't be a
 concern; that is the total CPU time and syslogd doesn't need much time to
 get the job done on most systems.
 
 If you're certain that it isn't logging events that it should:  did you make
 ever make any modifications to /etc/syslog.conf?  If so, comment out (put a
 # at the start of the line) the lines with the most recent changes.  Restart
 syslogd.  If it works, uncomment out one line and restart syslogd.  Keep
 doing that until you narrow down what causes syslog to suspend operations.
 Let us know if you find out anything.
 
 
 James Riendeau
 MMI Computer Support Technician
 1300 University Ave
 Rm. 436, Dept. of MedMicro
 Madison, WI  53706
 
 Phone: (608) 262-3351
 After-hours Phone: (608) 260-2696
 Fax: (608) 262-8418
 Email: [EMAIL PROTECTED]
 
 
 On 6/29/05 12:55 PM, Dixit, Viraj [EMAIL PROTECTED] wrote:
 
 Well, I will disregard your harsh comments. What I am trying to do is have
 all
 my FTP activity be logged in all.log. If you look at my FTP command it should
 be logging whole lot of information and my syslogd command should allow
 syslogd to continue writing without any delay. As for cron command, that just
 got copied with the rest. If you think what I pasted is meaningless, your
 common sense should have given you an indication to what I am looking for,
 just read the heading. Thank You!!
 VJ
 
 -Original Message-
 From: fbsd_user [mailto:[EMAIL PROTECTED]
 Sent:Wednesday, June 29, 2005 10:36 AM
 To:Dixit, Viraj; freebsd-questions@freebsd.org
 Subject:RE: Logging Stops after few minutes
 
 That's all very nice, but how about a explanation of
 what your are trying to do with logging and what
 cron has to do with things.
 
 With no background info what you posted is meaningless.
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Dixit,
 Viraj
 Sent: Wednesday, June 29, 2005 12:53 PM
 To: freebsd-questions@freebsd.org
 Subject: Logging Stops after few minutes
 
 
 
 
 I have been trying to find out why my system stops recording in the
 log files after few minutes. It will log if restart my syslogd
 daemon but then stops recording. I am pasting the commands and all
 relevant information below. Please advise, I need the log
 information!!! Thanks,
 VJ
 
 8127

Re: FreeBSD/UNIX backups to DVD+RW

2005-06-17 Thread James Riendeau
What I was doing did work fine for me; I just couldn't add multiple dumps to
the same disk.  It turns out this was the wrong way to do it.  I'm not sure
how a 32K block size would help.  The -B4589840 I used tells dump that the
'tape' it will be writing to can hold 4589840 kb (4.37 Gs), the size of a
standard dvd.

Unfortunately, growisofs provides direct access to the DVD and dump does not
use a ISO compliant file format, so growisofs cannot find the end of the
last session (who knew? :).  I was told the way to do this properly is to
dump a partition to a file in say /tmp/fullbackup/, gzip it, and repeat
until I have all the partitions.  Then write /tmp/fullbackup to the dvd:

(Note, I added -B10485760 to limit backups to 10 G's.  You have to give dump
some -B value or it will attempt to write out a catalog of standard size
tapes.  You should adjust this value to whatever meets your needs.)

# dump -0 -uL -C16 -B10485760 -f /tmp/fullbackup/usr.dumpfull /usr
# gzip /tmp/fullbackup/usr.dumpfull
# dump -0 -uL -C16 -B10485760 -f /tmp/fullbackup/var.dumpfull /var
# gzip /tmp/fullbackup/var.dumpfull
# dump -0 -uL -C16 -B10485760 -f /tmp/fullbackup/home.dumpfull /home
# gzip /tmp/fullbackup/home.dumpfull
# dump -0 -uL -C16 -B10485760 -f /tmp/fullbackup/root.dumpfull /
# gzip /tmp/fullbackup/root.dumpfull
# growisofs -speed=4 -Z /dev/cd0 -J -R /tmp/fullbackup

If you're pressed for space, you can do the above, but write each file to
the dvd before removing the gzipped dump file and creating the next one.
The first file would be written with the -Z (new session) option, then the
rest with the -M (append) option instead.  If this still takes too much
space, I suppose you could try to pipe the dump directly to gzip, but I
couldn't figure out how.  If anybody knows, please reply.

To do a restore, I found the following works:

- Recreate the partition (in my case this would involve playing with gmirror
first in the event of catastrophic disk/system failure)
- cd into the mounted partition (ex, cd /usr)
- mount the backup dvd and restore:

# cd /usr
# mount -t cd9660 /dev/your dvd drive /cdrom
# restore -rfv -P 'gunzip -c /cdrom/usrfullbackupfilename.gz'

But don't take my word for it, you should always do a test restore (into
/tmp if necessary if you haven't any blank hard drives handy) before a
catastrophic event happens to make sure the process works smoothly.

Thanks to all those who replied,

- James Riendeau

I'm posting this to the list for posterity's sake.  In case someone else has
this problem, they will have full instructions at their disposal, provided
they can find it.  

On 6/17/05 4:56 AM, Wojciech Puchar [EMAIL PROTECTED] wrote:

 I'm trying to setup backups to the DVD-RW drive on our new server before it
 goes into production.  I've got the DVD-RW drive working, and I figured out
 how to dump to it:
 
 # dvd+rw-format /dev/cd0
 # dump -0 -uL -C16 -B4589840 -P 'growisofs -speed=4 -Z /dev/cd0=/dev/fd/0'
 /usr
 
 
 with both DVD+RW and DVD-RW i was able to write DIRECTLY to /dev/ under
 NetBSD if only blocks were 32k
 
 should be possible with FreeBSD too.
 
 A test restore comes out clean:
 
 # restore -Nxvb /dev/cd0
 
 The problem is most of the partitions are tiny ( 1G) and I would like to
 fit more then one partition on each DVD.  I figured just passing -M (append
 data) instead of -Z (new session) would do it:
 
 # dump -0 -uL -C16 -a -P 'growisofs -speed=4 -M /dev/cd0=/dev/fd/0' /home
 
 But growisofs fails with :-( /dev/cd0 doesn't look like isofs..., and of
 course dump fails with Broken pipe.
 
 Any clues to how to get this to work?  (Webpage link is sufficient if there
 is something out there.  I couldn't find one.)
 
 I'm fairly new to the FreeBSD/UNIX world, so please be gentle.
 
 Thanks,
 
 -james
 
 
 
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


FreeBSD/UNIX backups to DVD+RW

2005-06-16 Thread James Riendeau
I'm trying to setup backups to the DVD-RW drive on our new server before it
goes into production.  I've got the DVD-RW drive working, and I figured out
how to dump to it:

# dvd+rw-format /dev/cd0
# dump -0 -uL -C16 -B4589840 -P 'growisofs -speed=4 -Z /dev/cd0=/dev/fd/0'
/usr

A test restore comes out clean:

# restore -Nxvb /dev/cd0

The problem is most of the partitions are tiny ( 1G) and I would like to
fit more then one partition on each DVD.  I figured just passing -M (append
data) instead of -Z (new session) would do it:

# dump -0 -uL -C16 -a -P 'growisofs -speed=4 -M /dev/cd0=/dev/fd/0' /home

But growisofs fails with :-( /dev/cd0 doesn't look like isofs..., and of
course dump fails with Broken pipe.

Any clues to how to get this to work?  (Webpage link is sufficient if there
is something out there.  I couldn't find one.)

I'm fairly new to the FreeBSD/UNIX world, so please be gentle.

Thanks,

-james



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]