Jump to content

Scythe

Members
  • Content Count

    155
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Scythe

  • Rank
    Slowly Learning

Contact Methods

  • Website URL
    http://myweb.msoe.edu/~frazeeg/
  • ICQ
    0

Profile Information

  • Gender
    Male
  • Location
    /universe/milkyway/sol/earth

Extra Info

  • Your CPU
    Intel Q9300
  • Your Graphics Card
    GeForce 8800GT
  • Your RAM
    G.SKILL 2x2GB DDR2
  • Your Operating System
    XP
  • Your Monitor
    Acer 22" Widescreen, X2gen 17"
  1. One vacation later and a couple hours tinkering and the problem is solved. I'm not sure if it was the mobo, RAM, or CPU, but I replace those three at once (that CPU socket is out of production for all I can find) and now it works. As you said scarecrow, it was a hardware problem. Thanks.
  2. [i though about that too but BIOS showed normal range of temps (~46 C). Also, I'm pretty sure the mobo would sound one of those alarms if the CPU was overheating, at least that's what my main desktop mobo does. Thanks for the suggestion though. Ordered a new mobo and CPU this afternoon, hopefully this solves the problem.
  3. Ok...it has gotten worse. I took the heatsink off, cleaned it and the CPU, and reapplied Arctic Silver 5 and now it shuts off after about 3 seconds. Definitely hardware related. At this point I'm thinking CPU but I would appreciate the thoughts of those more experienced than I. And, crap, they don't make CPUs for socket 754 anymore. Hmmm....
  4. Ok, so it's not technically a server in the traditional enterprise sense. It runs KDE and could double as a desktop in a pinch but it hosts all my files and is on 24/7. Close enough :)
  5. I have a Kubuntu 8.04 server that keeps randomly shutting down on me. As far as I can tell it doesn't happen during any specific event (meaning it will shut off when the OS is still loading and other times when it's been up for a few hours). I just installed a new 500W Rosewill power supply that is more than adequate for the hardware in it so I'm fairly certain that isn't the reason. The hardware: AMD Sempron 3000+ (stock HS) 512 MB RAM (1) 40GB IDE drive (OS drive) (2) 320GB SATA drives \ (2) 500GB SATA drives | (storage drives) (2) 1TB SATA drives / (2) case fans, 80mm I think SATA controller The next thing I will check is overheating and OS hard drive integrity but right now I'm a little too frustrated to do anything else. It's frustrating to not have the majority of my media files and documents unavailable, let me tell you. Thanks for the help.
  6. I found a different method. The page you posted helped a little in giving me the idea: I made a new folder called "private" and put hardlinks to the folders I wanted within the private folder and set that to restricted access. Not exactly what I was looking for but itll work fine for my purposes. #cd /media/storage1 #mkdir private #cd private #ln -s /media/storage1/Music Music
  7. Hello all, Ive got my Samba server set up with multiple users and of course multiple permissions. My question now is how do I make it so that certain users cant see folders they cant access. For example: I have a folder named "320" that I want only myself to be able to see when the server is accessed. As it is other users can see the folder even if they cant access it. How would I make it so that the folder is not visible to the others but still visible when I log on?
  8. Hey....solved my own problem :-) I just had to run this code: scythe@gfunk:/media$ sudo chown -hR scythe storage1 scythe@gfunk:/media$ sudo chown -hR scythe storage1b Oddly enough I found this out while trying to find out why I couldn't get write access through Samba...but whatever it works now.
  9. I have a Kubuntu server that for some reason I can't write to my storage drives while logged in. Here's my fstab: # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 # /dev/hda1 UUID=825f5093-d527-4dc7-8da2-0f4e60212898 / ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1 # /dev/hda5 UUID=a84677a7-55d8-4373-8590-a8f40cde18f0 none swap sw 0 0 /dev/hdc /media/cdrom0 auto user,atime,noauto,rw,dev,exec,suid 0 0 /dev/fd0 /media/floppy0 auto user,atime,noauto,rw,dev,exec,suid 0 0 /dev/sda1 /media/storage1 auto user,exec,rw 0 0 /dev/sdb1 /media/storage1b auto user,exec,rw 0 0 # /dev/hdc /media/cdrom0 udf,iso9660 user,atime,noauto,rw,dev,exec,suid 0 0 Everything I've found on Google has told me that I have the entries for /dev/sda1 and /dev/sdb1 all set correctly, but for some reason I still can't write to them. I'm kinda wishing I had stuck with Fedora 7, but if this can also work I'll stay with Kubuntu. Permissions with Fedora were much easier.
  10. You might try keytouch. I don't remember if it gives you an option to change how much it changes your volume by, but you'll definitely be able to set up your other shortcut keys.
  11. I'm actually doing this is Fedora 7, which has its own Samba configuring GUI (I forget what it's called). I'll try uninstalling it and see what happens. *edit* The Fedora tool is system-config-samba
  12. I did that when I set the permissions in the first place :-/
  13. I've got my server running Samba to share files with my other computers. The only problem is that Samba takes it unto itself to rewrite samba.conf and put some semi-colons where they don't belong. For example: [Music] path = /media/storage1/Music ; writeable = no ; browseable = yes valid users = owner, Music write list = owner In front of the writeable and browseable tags. This means that I have to continually keep going back in to edit that back to the way I had it. Quite annoying. Does anyone know a way to keep this from happening? I tried to make the file read-only, but that didn't work (probably because root is the owner). [moved from Software by spinynorman]
  14. I thought I tried that and it didn't work...obviously not. I just tried it and it worked great. The option is under "Advanced Options." Thanks everyone for the help. Case closed.
  15. So if I do a "Link to Application...", set the work path to where I saved the script, and set the command as "sh script.sh" it should run the script? Will it open up a terminal to do this? I like the verbose mode when backing my stuff up. It's nice to know what's going on ;-)
×
×
  • Create New...