Slackware :: Change The Option To Have Samba Start During The Boot Process?
May 17, 2010
Where do I change the option to have samba start during the boot process? I've googled and I've found old posts that say it's a line in /etc/rc.d/rc.inet2 but in my semi-current box, I don't see the part about starting stopping the samba server.
I switched today to slackware-current on one of my desktops to play with it and ran directly into a problem.
Since ages my lilo.conf has two entries for slackware. One for runlevel 3 and one for runlevel 4.
Since the upgrade this is no more possible because I get a kernel panic as soon as udevadm trigger is called. The stack says something about an unknown boot option. Because that i removed the append lines from my lilo.conf and i was able to boot the system. The crash happens when udev is called from within the ramdisk and afterwards. I tried both.
My question is now. Is this a bug in udev or expected? I have this setup since at least 5 years and had never problems with that. What do I have to do to be able to select the runlevel at boot time?
I have installed centos 5.4 with samba 3.0.33-3.15. Now this server is PDC for a domain with 20 xp client. I want to set the "password must change" option in the samba user detail.Now I have this configurationmaximum password age = 68256000maximum password age = 0with pdbedit -Lv pippo
this is not specifically a slackware related question, but since done on 2 slackware boxes... the situation is, i have one box for browsing and other desktop activities and another box acting as router/local server. what i want to achieve is that the router box would look on a nfs mounted folder for new *.torrent files (which i put there from the desktop box) and if there is a new file, it would start downloading it automatically. also a good thing would be if it would notify me when finished.so how would you go about itwhat torrent client would you use and so on? maybe someone has already done something like this?
I loaded the dvd (one that came with Linux Format Magazine No. 139), changed BIOS to boot from dvd, and then:
I get the welcome screen with the options to boot Ubuntu, KUbuntu, XUbuntu or Boot from First Hard Disk. As I have an older laptop I was going to try XUbuntu. However, the arrow keys did not change the boot option. In fact nothing worked, Tab did not bring up a menu and Enter did not initiate boot.
I tried reloading the dvd, switching off the laptop (no way to shutdown) and restarting but always come up with the same problem.
My DVD drive works fine and the dvd appears not to be faulty since all the info is readable when it is loaded with windows running.
My system details are:
HP compaqnx9000 Mobile Intel Pentium(R) 4-m CPU 2.20 GHz 219GHz 704MB RAM Optiarc DVD RW AD-7580A Radeon 1GP 340M
Up until a couple days ago, samba server worked perfectly. I don't remember doing anything with it except adding another share or two. I can still run SWAT, even from remote computers, but I still have the problem of starting the samba server itself.
#./rc.samba start Starting Samba: /usr/sbin/smbd -D /usr/sbin/nmbd -D #./rc.samba restart smbd: no process killed
After issuing the "start" option, I go into SWAT and the status page says samba's not running.
I have installed "open-SUSE 11.4" on a "500GB Free Agent External Hard Drive". I didn't have any problem in booting since last week that I booted it from my laptop. Also I did it before several times from then when I try to boot it e.g. from an "Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz" PC the time between loading INITRD and starting boot sequence messages lasts nearly 30 minutes!(i didn't actually measure it but it take a long time in the same order). after starting boot sequence which is showed on monitor everything looks normal. e.g copy of files would be done by speeds between 2MB/s to 30 MB/s depending on the targets.I used to use the external hard derive to boot from different laptops and PC's from start but I didn't have such a problem anytime.
have just installed Ubuntu alongside Windows 7. I just went along with the manual set-up all through the install. I was expecting to see an obvious option on starting up my computer as to whether to run Ubuntu or Windows but it just goes right ahead and runs windows exactly as it did before the install.
I was installed linux mint in windows 7 using option "Install inside windows"... I got trouble with windows7 so i reinstalled it... but now there is no option to select OS at the start up... But i have the drive where i installed mint and all other files.. Is there any way to get it back.. Because i dont have time to reinstall mint...
I am attempting to share a folder from an existing drive that has been formatted in NTFS. I simply right click on the folder, goto share, and I can see the option to share to UNIX and that works with no problems. My question is; why is the SAMBA sharing dialog grayed out?
I'm currently having a problem trying to remove the black screen that appears at Start-Up that asks me which operating system I want to run...I've already deleted wubi but this screen keeps appearing every time my computer starts up...How do I remove or disable this feature?
Running Ubuntu Server 10.04 32 bit. Sometimes when I reboot it does not start up, It seems to be going through the boot process but then just hangs. I have had a look at the log files and can't see anything, but I'm not really sure what I am looking for.
On my Ubuntu 10.04 LTS Server, mysql does not start at boot. I tried this but does not work. Code: root@dev:~# chkconfig mysql ON
The script you are attempting to invoke has been converted to an Upstart job, but lsb-header is not supported for Upstart jobs. insserv: warning: script 'K02mysql' missing LSB tags and overrides insserv: warning: script 'S10vzquota' missing LSB tags and overrides The script you are attempting to invoke has been converted to an Upstart job, but lsb-header is not supported for Upstart jobs .....
How to make sure mysql process comes up automatically after every reboot
I just got to finish installing ubuntu lastest version on my new netbook, im really exited about how powerful it can get. The thing is, I'm still keeping my old Windows 7 partition and data, and I want to access it faster, editing the grub options, to change the timer on it, and the default booting option.
I've installed Windows 7 Ultimate on a notebook which previously ran Vista. No problems there.I've now installed Ubuntu (now updated to 10.04)so that it can boot to either OS.
It all works fine and when I first power up, I get a screen which invites me to select the OS I want to use. There are however two problems:
1) it defaults to Ubuntu (whereas I would prefer it to default to Windows 7 (it's a work laptop and most of the applications are Windows-specific),
2) the list of choices is getting increasingly complex with an expanding list of choices (with each major update of Ubuntu adding more); it even seems to include an option to go back to Vista!As long as I move down the list and make the right selection quite speedily, I get to where I want to be (though, as I say, I would like to change the default option).Is there any way I can edit/shorten this list without damaging the functionality and how can I change that default?
Got it on a CD and was using it as "Try Ubuntu" instead of installing it for good (I still wanted to see if there were memory issues or HDD issues with my desktop, before I installed it for good).Anyway, I would shut down the pc after about 2 or 3 days and redo the CD install (try ubuntu option) again and add all the plugins etc.Kids used this for playing some games on friv or nickjr.The real issue - of late, when I try to start the PC and boot from the CD, I am getting a LOGIN screen instead of the regular option to install from CD or Try the Ubuntu.
I upgraded to current, and x won't start... I suspect it's probably an issue with the Nvidia drivers (I forgot to swith my xorg to the nv drivers; I knew I'd be getting a new kernel). Anyway, it leaves me with an unusable computer. Is there anyway I can get into a console before x tries to start. BTW, the ctrl-alt-f1 hotkey isn't working.
and hangs for another 120 seconds. In X11 I have no sound at all even after running alsaconf with no errors. My sound works perfectly in Ubuntu, so it's not a hardware problem. Are the two problems related or are they two separate things? Any help here would be hot.
I'm loging my slackware as a simple user After each reboot I need to start cupsd for my printer nfsd and mountd to export my shared directories I use init 4 for my desktop I would like these services to start always without the konsol and the command lines.
I installed Slackware 13.1 a little bit ago, played around with it, performed an upgrade with Slackpkg, messed around with some settings, and chose a new theme. I had set the runlevel to 4 and when I rebooted after choosing a new login theme the screen just went black at the point where the login prompt should have appeared. I couldn't even get into the CLI. Using a LiveCD, I set the run level to 3 again and was able to log in, but when I try to start X the screen goes black and freezes again, so I believe my new login theme is the culprit. Is there a way to change to the default login theme from the CLI?
I'm trying to find how to schedule a process to start at a specific time (not on start up). How would I schedule a process/application to start at a specific time (if it matters, it will be a background process). For instance, have process abc start every weekday at 5am. I've done this for windows many times though have only been using linux regularly for a few months and haven't figured out the best way of doing this.
So far the best solution I have is to create a program that will start on boot and have it check the time and sleep until the required time and then start the required process(es) at the required time(s). But this seems more of a hack since I'd expect there to be a proper way of doing this.
2nd and 3rd might be linux kernel problems but may help someone else so I included here.1st -- run level 4, /etc/rc.d/rc.4 and xdm -nodaemonJust installed 13.1 on an odd system, including building a new kernel.One thing I do is have the system boot to a command prompt and then run /etc/rc.d/rc.4 to start XBut I found that the rc.4 uses xdm -nodaemon flag and it was causing problems so I removed and all is pretty good. I still see some odd behavior with the virtual ttys sometimes.2nd -- when building a new kernel, I found I need the device-mapper butcouldn't tell if that was a linux kernel issue or something to do with lilo, I didn't want and don't need multiple disk devices like for LVM or MD so I didn't plan to have this enabled.3rd -- CONFIG_EXT4_USE_FOR_EXT23 When that kernel config option was selected and I have only an EXT4 filesystem, the filesystem was mounted as an EXT2, even though the kernel had no EXT2 feature. /etc/fstab specified EXT4 but the mount command showed EXT2. A silent problem that could leave an unpleasant surprise since EXT2 hos no journaling.4th -- I had to run lilo -C by hand in a virtual tty before finishing the install. This was what I had to do when installing 13.0 on different hardware. It seems that the lilo part of the install needs some sorting out.
I have to rename a group of machines in my little samba domain (tbd backend) but there is an ugly bug that makes this impossible. have set 'rename user script' variable corectly, also checked all configurations.When i change computer name in my windows box, it shows an error saying something like "Error calling remote procedure"Looking on server side, username for the machine gets correctly changed in /usr/passwd, and also in samba database.But samba log says:
=============================================================== [2009/10/08 11:10:32, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 11052 (3.0.33-3.7.el5_3.1)
I have tried different methods to auto start wpa_supplicant at boot on Ubuntu Lucid server on a laptop which can't be connected to Ethernet.
The only thing that worked is adding the wpa_supplicant command before exit0 in rc.local. It solve my problem of wpa_supplicant auto start and annoyance on not be able to ssh before local login. But the screen stuck at Ubuntu Logo. How can i get pass Ubuntu logo screen to regular tty or xbmc in future?
I installed a fresh copy of Slackware 13.1 (stable) on one of my media servers and I am experiencing something strange.... When I power up the machine, I see the kernel booting, no errors, until it gets to the point where it says:
And then randomly freeze there.... Well the machine is not totally frozen because the cursor still blinks. But it will never continue... Like I said, this happens on a random basis... After a reset, it might go through or simply stall at the same spot.
I remember after installing Slack 13.1, I rebooted the machine but forgot to remove the DVD from the player, so the install routine started up, and froze at the same point when it was loading the kernel for the setup programs...
My mobo is a MSI k9N platinum.
I never had this problem before.... (well I never used 13.1 before). Since I got this machine, I used slack 12.2 and slack 13-current with success.
This problem makes the machine extremely unreliable because I intent to use it as a backup and media server, so chances I will WOL the machine and use it remotely... if that happens.
I just moved my / from sda1 to an ide drive, hde1. i dont see how this could have caused any of these issues, but it did.
First my network card failed to start. i added a line in my rc.local file (where i put all of my additional programs, etc i want to start):/etc/rc.d/rc.inet1
The above now starts my network card with my static ip configured. dhcpcd also worked but i wanted this static.
Now samba will not start. i have the following line in my rc.local: /etc/rc.d/init.d/samba start
This used to work just fine. at first i thought that samba may be trying to start before my network card gets an ip, but the line is *after* the network startup line. just to make sure, i made an additional script called startsamba which contained a sleep 60 followed by samba start, to delay the startup of samba even further.
The message samba reports is very vague, something like failed - core dumped. most of the core dump log is garbage characters, but here is the beginning which seems like it might contain some info:
ERROR: Can't log to stdout (-S) unless daemon is in foreground (-F) or interactive (-i) after the system starts, i can drop to a console and type "/etc/rc.d/init.d/samba start" and the service starts just fine. i've also tried starting samba manually with "smbd -d" which also produces the core dump when started from rc.local, but not when started from a console after startup.