[Sid] csync2 startup scripts
I think there is something wrong with scync2 startup scripts: # systemctl status csync2.service ○ csync2.service - LSB: Cluster file synchronization daemon Loaded: loaded (/etc/init.d/csync2; generated) Active: inactive (dead) since Tue 2021-10-19 15:44:16 CEST; 7min ago Docs: man:systemd-sysv-generator(8) Process: 1220 ExecStart=/etc/init.d/csync2 start (code=exited, status=0/SUCCESS) Process: 1859 ExecStop=/etc/init.d/csync2 stop (code=exited, status=0/SUCCESS) CPU: 28ms Oct 19 15:08:42 Artemis systemd[1]: Starting LSB: Cluster file synchronization daemon... Oct 19 15:08:42 Artemis csync2[1220]: Starting Cluster file synchronization daemon: csync2 Oct 19 15:08:42 Artemis systemd[1]: Started LSB: Cluster file synchronization daemon. Oct 19 15:44:16 Artemis systemd[1]: Stopping LSB: Cluster file synchronization daemon... Oct 19 15:44:16 Artemis csync2[1864]: start-stop-daemon: --remove-pidfile requires --pidfile Oct 19 15:44:16 Artemis csync2[1864]: Try 'start-stop-daemon --help' for more information. Oct 19 15:44:16 Artemis systemd[1]: csync2.service: Deactivated successfully. Oct 19 15:44:16 Artemis systemd[1]: Stopped LSB: Cluster file synchronization daemon.
Re: Startup scripts of Debian Lenny don't perform file system check while on battery power
On Tue, Jan 13, 2009 at 05:20:53AM -0600, Ron Johnson wrote: On 01/13/09 04:40, elektra wrote: [snip] The startup scripts issue a warning of the kind Warning! Skipping file system check because the system is running on battery power - I don't know the exact wording - so the sysadmin has to perform the check manually after boot-up to avoid data loss... It's been like that for ages, since a full fsck takes a long time, which would drain the batteries. Ouch. Shouldn't it give a prompt asking what it should do? i.e. ask to skip the fsck and force the mount; or run the fsck anyway (and suggest plugging in the computer for the duration). Doug. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Startup scripts of Debian Lenny don't perform file system check while on battery power
On Thu, 2009-01-15 at 20:58 -0500, Douglas A. Tutty wrote: On Tue, Jan 13, 2009 at 05:20:53AM -0600, Ron Johnson wrote: On 01/13/09 04:40, elektra wrote: [snip] The startup scripts issue a warning of the kind Warning! Skipping file system check because the system is running on battery power - I don't know the exact wording - so the sysadmin has to perform the check manually after boot-up to avoid data loss... It's been like that for ages, since a full fsck takes a long time, which would drain the batteries. Ouch. Shouldn't it give a prompt asking what it should do? i.e. ask to skip the fsck and force the mount; or run the fsck anyway (and suggest plugging in the computer for the duration). I'd quite like to have an option to opt-out of a fsck anyway; it's really annoying when I'm just turning it on for a few minutes to check my mail before I rush out the door. Richard -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Startup scripts of Debian Lenny don't perform file system check while on battery power
On Fri, 16 Jan 2009 15:30:45 +1300 Richard Hector rich...@walnut.gen.nz wrote: ... I'd quite like to have an option to opt-out of a fsck anyway; it's really annoying when I'm just turning it on for a few minutes to check my mail before I rush out the door. Richard There was a thread about this several months ago; I don't remember much about it, but the initial posts seem to contain a fair amount of useful information: http://lists.debian.org/debian-user/2008/06/msg00833.html Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Startup scripts of Debian Lenny don't perform file system check while on battery power
On Thu, 2009-01-15 at 22:18 -0500, Celejar wrote: On Fri, 16 Jan 2009 15:30:45 +1300 Richard Hector rich...@walnut.gen.nz wrote: ... I'd quite like to have an option to opt-out of a fsck anyway; it's really annoying when I'm just turning it on for a few minutes to check my mail before I rush out the door. Richard There was a thread about this several months ago; I don't remember much about it, but the initial posts seem to contain a fair amount of useful information: http://lists.debian.org/debian-user/2008/06/msg00833.html Thanks - looks like no 'proper' solutions, but possibly some useful hacks there. Richard -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Startup scripts of Debian Lenny don't perform file system check while on battery power
Hi - sorry I can't use reportbug because I am not using Debian anymore. Using the bug-report search engine I couldn't find a report related to my experience. I don't know the name of the Debian package which contains the feature that I assume has messed up the data in my ext3 file system. Here is the story: After an apt-get update apt-get upgrade my system crashed three times while on battery power (supend to RAM which perfectly worked before wasn't properly waking up anymore) Subsequently my ext3 file system was corrupted in such a way that fsck.ext3 couldn't repair it anymore - system gone, some work lost that I couldn't recover from the disc. I think the reason is that the startup scripts of the Lenny version I was running (installed with the netinstall cd in June or July on a Asus EEE PC 901 and frequently updated until it broke on Dezember 23rd 2008) omits the file system check if it detects a mobile system running on battery. The startup scripts issue a warning of the kind Warning! Skipping file system check because the system is running on battery power - I don't know the exact wording - so the sysadmin has to perform the check manually after boot-up to avoid data loss... Given that my system and some of my data went to digital nirvana I don't think adding such a feature was a smart move - especially if there is no mechanism included which avoids mounting a corrupted file system over and over again without a file system check! Checking a interrupted ext3 mount is a matter of seconds so where is the point in skipping the check? This is the second time in my Debian user experience where I see kooky things going on in the bootup phase - I remember Woody attempting to mount already mounted file systems several times. At least this didn't hurt much. I like Debian and I'm surely going to use it again somewhere some day. And I'm sorry that I didn't write this email earlier - but I was busy and I was pissed. I'm running Slackware 12.2 now on the 901. It is not comfortable but it doesn't break because of an update and I can trust the people writing the startup scripts. Cheers, elektra -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Startup scripts of Debian Lenny don't perform file system check while on battery power
elektra wrote: Hi - sorry I can't use reportbug because I am not using Debian anymore. Using the bug-report search engine I couldn't find a report related to my experience. I don't know the name of the Debian package which contains the feature that I assume has messed up the data in my ext3 file system. Here is the story: After an apt-get update apt-get upgrade my system crashed three times while on battery power (supend to RAM which perfectly worked before wasn't properly waking up anymore) Subsequently my ext3 file system was corrupted in such a way that fsck.ext3 couldn't repair it anymore - system gone, some work lost that I couldn't recover from the disc. [snip] I think posting this to debian-user in quite pointless. Please forward all above to the people that really can judge: Debian sysvinit maintainers pkg-sysvinit-devel AT lists.alioth.debian.org. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com Ukrainian C++ developer, Debian Maintainer, APT contributor signature.asc Description: OpenPGP digital signature
Re: Startup scripts of Debian Lenny don't perform file system check while on battery power
On 01/13/09 04:40, elektra wrote: [snip] I think the reason is that the startup scripts of the Lenny version I was running (installed with the netinstall cd in June or July on a Asus EEE PC 901 and frequently updated until it broke on Dezember 23rd 2008) omits the file system check if it detects a mobile system running on battery. The startup scripts issue a warning of the kind Warning! Skipping file system check because the system is running on battery power - I don't know the exact wording - so the sysadmin has to perform the check manually after boot-up to avoid data loss... It's been like that for ages, since a full fsck takes a long time, which would drain the batteries. over again without a file system check! Checking a interrupted ext3 mount is a matter of seconds so where is the point in skipping the check? That's just a load of garbage. e2fsck can take a *long* time. [snip] I like Debian and I'm surely going to use it again somewhere some day. And I'm sorry that I didn't write this email earlier - but I was busy and I was pissed. I'm running Slackware 12.2 now on the 901. It is not comfortable but it doesn't break because of an update and I can trust the people writing the startup scripts. Blah blah blah. -- Ron Johnson, Jr. Jefferson LA USA I am not surprised, for we live long and are celebrated poopers. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
what startup scripts attempt to update sendmail config?
Debian Sarge.. On boot, apparently right after the networking init script, and quite some time before the actual sendmail init script, something appears to be attempting to update various sendmail db's in /etc/mail. What's doing this? -- Ron Peterson Network Systems Manager Mount Holyoke College http://www.mtholyoke.edu/~rpeterso -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Warum: normal Debian startup scripts execute ssh-agent?
Salve! mir ist aufgefallen, das beim Atart von fluxbox (via XDM) zwei ssh-agent gestartet werden. (Knoppix hddinst mit mehreren updates/upgrades) http://www.debian.org/doc/manuals/reference/ch-tune.en.html sagt: For the X server, normal Debian startup scripts execute ssh-agent as parent process. So you only need to execute ssh-add once. For more, read ssh-agent(1)and ssh-add(1). -Aber wieso wird dieser ssh-agent gestartet? -Was startet diese ssh-agents? -Wie kann man ssh-agents überwachen? -Wo gibt es ssh logs? -Wie kann man ohne X ethereal nutzen? Gruß rob
Re: Warum: normal Debian startup scripts execute ssh-agent?
Hallo Robert, Robert Michel, 28.07.2005 (d.m.y): -Wo gibt es ssh logs? /var/log/auth* -Wie kann man ohne X ethereal nutzen? Indem man es als tethereal aufruft. Gruss, Christian Schmidt -- Der Rhein ist ein Jungbrunnen: ein Schluck, und Du wirst nicht alt. signature.asc Description: Digital signature
Re: Warum: normal Debian startup scripts execute ssh-agent?
On Thu, Jul 28, 2005 at 04:52:09PM +0200, Robert Michel wrote: Salve! mir ist aufgefallen, das beim Atart von fluxbox (via XDM) zwei ssh-agent gestartet werden. (Knoppix hddinst mit mehreren updates/upgrades) $hier (richtiges Debian, stable) wird nur einer gestartet. For more, read ssh-agent(1)and ssh-add(1). Beherzigt? -Aber wieso wird dieser ssh-agent gestartet? Damit du ihn benutzen kannst. -Was startet diese ssh-agents? Der X-Server. Ansonsten kannst du mit ps -ef die PID des Parent herausfinden. -Wie kann man ssh-agents überwachen? ssh-add -l hast du gefunden? cu ulf -- Ulf Volmer [EMAIL PROTECTED] www.u-v.de -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Warum: normal Debian startup scripts execute ssh-agent?
Salve Ulf! Ulf Volmer schrieb am Donnerstag, den 28. Juli 2005 um 18:20h: -Aber wieso wird dieser ssh-agent gestartet? Damit du ihn benutzen kannst. -Was startet diese ssh-agents? Der X-Server. man ssh-agent The idea is that ssh-agent is started in the begin- ning of an X-session or a login session, and all other windows or programs are started as clients to the ssh-agent program. Ok aber wieso wird ssh-agent nicht on demand gestartet? Ansonsten kannst du mit ps -ef die PID des Parent herausfinden. Ok /usr/bin/fluxbox startet ssh-agent zweimal. (vielleicht weil beim Start ein XDM oder GDM abbricht und ich XDM manuell starte.) Zuerst hatte ich bei diesen zwei Prozessen an Besuch gedacht - jetzt kann ich mal in Ruhe nachgehen warum es zwei Prozesse sind. Danke, auch an Christian, für Eure Tipps/Hinweise. Bei Ethereal hätte ich eine Option -t (Text) erwartet und nicht ein seperaters tool - aber eigendlich logisch, so braucht man die GUI nicht mitinstallieren. Gruß rob
Re: Warum: normal Debian startup scripts execute ssh-agent?
On 2005-07-28 21:46:33 +0200, Robert Michel wrote: man ssh-agent The idea is that ssh-agent is started in the begin- ning of an X-session or a login session, and all other windows or programs are started as clients to the ssh-agent program. Ok aber wieso wird ssh-agent nicht on demand gestartet? ssh-add und ssh erfahren über eine Umgebungsvariable, wie sie den ssh-agent erreichen. Dafür muss aber diese Umgebungsvariable recht früh gesetzt sein, damit sie jedes Programm in deiner X-Session nutzen kann. Ansonsten kannst du mit ps -ef die PID des Parent herausfinden. Ok /usr/bin/fluxbox startet ssh-agent zweimal. (vielleicht weil beim Start ein XDM oder GDM abbricht und ich XDM manuell starte.) Zuerst hatte ich bei diesen zwei Prozessen an Besuch gedacht - jetzt kann ich mal in Ruhe nachgehen warum es zwei Prozesse sind. Ich hatte das Problem mit den zwei ssh-agents auch. Es lag bei mir daran, dass ich in /etc/X11/Xsession.d zwei Dateien hatte, die den ssh-agent gestartet haben. Vielleicht hilft dir das weiter. Michael -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Warum: normal Debian startup scripts execute ssh-agent?
Robert Michel [EMAIL PROTECTED] wrote: Salve Ulf! Ulf Volmer schrieb am Donnerstag, den 28. Juli 2005 um 18:20h: -Aber wieso wird dieser ssh-agent gestartet? Damit du ihn benutzen kannst. -Was startet diese ssh-agents? Der X-Server. man ssh-agent The idea is that ssh-agent is started in the begin- ning of an X-session or a login session, and all other windows or programs are started as clients to the ssh-agent program. Ok aber wieso wird ssh-agent nicht on demand gestartet? Es wird doch auf deinen Wunsch hin gestartet: $ grep ssh /etc/X11/Xsession.options use-ssh-agent Bei Ethereal hätte ich eine Option -t (Text) erwartet und nicht ein seperaters tool - aber eigendlich logisch, so braucht man die GUI nicht mitinstallieren. Genau. Ein Programm, dass mit -t eine Consolenausgabe liefert, muss denoch gegen die Grafikbibliotheken gelinkt sein und damit müsstest du auf einem Server den X-Core installieren. Schöne Nacht allerseits, Jörg. -- NetBSD ist für Frauen: es läuft auf Waschmaschinen -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
bash startup scripts - what is an interactive login ??
Can anyone clarify for me when the ~/.bash_rc and /etc/bash.bashrc scripts get sourced? I read from the man and googling that it is only when an interactive login shell is created, but what does that mean? If I create a new xterm do these scripts get sourced or is it only if I do an rlogin, ssh, login ,etc? Thanks, Mark
Re: bash startup scripts - what is an interactive login ??
On 2005-07-12, Mark D. Hansen wrote: Can anyone clarify for me when the ~/.bash_rc and /etc/bash.bashrc scripts get sourced? ~/.bash_rc is not a standard file; do you mean ~/.bashrc? /etc/bash.bashrc is usually sourced in /etc/profile. Both files can be sourced any time you want them to be. I read from the man and googling that it is only when an interactive login shell is created, but what does that mean? man bash: A login shell is one whose first character of argument zero is a -, or one started with the --login option. An interactive shell is one started without non-option arguments and without the -c option whose standard input and error are both connected to terminals (as determined by isatty(3)), or one started with the -i option. PS1 is set and $- includes i if bash is interactive, allowing a shell script or a startup file to test this state. If I create a new xterm do these scripts get sourced or is it only if I do an rlogin, ssh, login ,etc? If you call xterm with the -ls option, it opens a login shell, i.e., one which sources /etc/profile and ~/.bash_profile. If the shell is interactive, but not a login shell (e.g., xterm without -ls), it sources ~/.bashrc. -- Chris F.A. Johnson http://cfaj.freeshell.org == Shell Scripting Recipes: A Problem-Solution Approach, 2005, Apress http://www.torfree.net/~chris/books/cfaj/ssr.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bash startup scripts - what is an interactive login ??
Can anyone clarify for me when the ~/.bash_rc and /etc/bash.bashrc scripts get sourced? I read from the man and googling that it is only when an interactive login shell is created, but what does that mean? If I create a new xterm do these scripts get sourced or is it only if I do an rlogin, ssh, login ,etc? All of your questions are answered in the man page, under INVOCATION. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bash startup scripts - what is an interactive login ??
Chris F.A. Johnson wrote: Mark D. Hansen wrote: Can anyone clarify for me when the ~/.bash_rc and /etc/bash.bashrc scripts get sourced? ~/.bash_rc is not a standard file; do you mean ~/.bashrc? I am sure that is the case. /etc/bash.bashrc is usually sourced in /etc/profile. Not on Debian. I think you must be thinking of a different system. :-) If I create a new xterm do these scripts get sourced or is it only if I do an rlogin, ssh, login ,etc? If you call xterm with the -ls option, it opens a login shell, i.e., one which sources /etc/profile and ~/.bash_profile. If the shell is interactive, but not a login shell (e.g., xterm without -ls), it sources ~/.bashrc. You are probably confused by the fact that Debian's xdm, kdm, gdm login does not start the user shell as a login shell and so the ~/.bash_profile is not sourced at login the same as a text console login. Create a ~/.xsession as a login shell as already described several times this week on this list and it will source your ~/.bash_profile at login. Bob signature.asc Description: Digital signature
Environment vars and startup scripts
Title: Environment vars and startup scripts Hi, I'm playing about with java and tomcat4, on Woody bf2.4. I grabbed J2SDK1.4.2 and JakataTomcat 1.4.30 and installed them to /usr/local/bin/2jsdk1.4.2_04 /usr/local/bin/jakata-tomcat-4.1.30 Then I ran ln -s /usr/local/bin/j2sdk1.4.1_01/bin* /usr/bin and then export JAVA_HOME=/usr/local/bin/2jsdk1.4.2_04 export CATALINA_HOME=/usr/local/bin/jakata-tomcat-4.1.30 I start tomcat $CATALINA_HOME/bin/startup.sh And I can access http://mydebianbox:8080, I get the Jakata page telling me tomcat is working. Most satifiying. My questions are; Have I installed these technologies in accordance with The Debian Way ? How do I get the environment vars and the startup script to run automatically on boot ? How come Tomcat4 is not available in Stable ? (I thought it was dependant on stuff in unstable, but it's working so?) Thanks Matt Joyce Children's Cancer Institute Australia http://www.ccia.org.au
Re: startup scripts
On Tue, May 27, 2003 at 02:45:52PM +0200, [EMAIL PROTECTED] wrote: i have a script which i want to run just aftert the system has booted up and before the login prompt is shown to the user...where do put this script ? i am running debian woody. I think you can put it in /etc/rc.boot/ kicsi:~# man rc.boot Reformatting rc.boot(5), please wait... RC.BOOT(5) Debian GNU/Linux Manual RC.BOOT(5) NAME /etc/rc.boot - directory for local or per-package boot scripts. DESCRIPTION The /etc/rc.boot directory is obsolete. It has been super- seded by the /etc/rcS.d directory. At boot time, first the /etc/rcS.d directory is scanned and then, for backwards compatibility, the /etc/rc.boot directory. fyi rgds, charlie -- Vgh Kroly - System Engineer - UTA - TIS.SAS.BSS Cynics say that Hungarians created America's Hollywood before other Hungarians less destructively created America's A-bomb. http://www.mek.iif.hu/kiallit/tudtor/tudos1/martians.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startup scripts
man update-rc.d On Tuesday, May 27, 2003, at 06:51 AM, Sharninder Singh-662 wrote: hi i have a script which i want to run just aftert the system has booted up and before the login prompt is shown to the user...where do put this script ? i am running debian woody. regards sharninder -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Debian startup scripts...
Hello Tony, Please excuse the intrusion, but I came across your name while skimming through a Debian listserv.. I am in the process of setting a up a Debian 2.2 (Potato) on a PIA box. I was able to successfully ping the outside world via my firewall, and was also able to use a text browser (lynx) to navigate the web. However, I can't seem to be able to browse using Netscape. So as a remedy, I manually inserted some pertinent info in /etc/init.d/network. I also setup /etc/modules to include an alias for my NIC driver(dmfe.o). The idea is to have the kernel load the correct module for the NIC. After restarting 'inetd' and recognizing that I still couldn't see the outside world using Netscape, I decided to reboot. Unfortunately, the kernel can't find any of the modules listed in /etc/modules. Hence, the system won't complete the start up sequence.. Additonally, the machine doesn't have a floppy drive. Is there anyway that I can boot into single user mode and fix the problem? Are there some hot-keys that I can employ? I have an old Debian 2.0 CD that I could use as a boot kernel. I suspect that one of the start up scripts has bogus info in it. Thanks in advance... -- Alfred
Re: Startup-scripts
I hammered out this reply, and then I realized it would be somewhat irrelevant because I use slink and I've been told that Debian is switching from /etc/rc.boot to rc.S, or something, because it's more widely used. So if the following doesn't apply to potato, then please disregard it: Try putting the scripts into /etc/rc.boot Make sure they are prefaced with #!/bin/sh or #!/bin/bash or #!/bin/perl, or whichever program you want to run the script. This is something that I never needed to do before because my scripts were always executed from within bash (and I was only using bash scripts) and my perl scripts were executed with the perl program in the command line. But you probably knew this part already =) The way the /etc/rc.XX directories work is that whatever is in the directory is executed when the system enters runlevel XX. I can't remember which numbers mean what, but rc.boot isn't referred to numerically so it's easy to remember what it does. Everybody feel free to correct me if I've said anything stupid in this post. Heck, the letters might not even be rc. I've been away from civilization (read:Debian--or BSD, or anthing similar) for so long (read: three weeks) that I'm starting to lose it. *please CC all replies to me, as I am not subscribed to this list. thanks* Yeah, if you want to correct me, CC it to him. [EMAIL PROTECTED] I am using Debian GNU/Linux potato i386. I have written a ipchains firewall script that I would like to be executed automatically during startup. Where would I put this (shell) script? I know that Debian has rules Where would I put this (shell) script? I know that Debian has rules about the proper way to do certain system config things - what is the proper way to do this? = Jolan Tru, Fish of Borg Visit me on the web! http://www.geocities.com/TimesSquare/Frontier/4784/stccg.html ///Archaeologists near mount Sinai have discovered what appears to be a missing page from the Bible. The page is currently being carbon dated in Bonn. If genuine it belongs at the beginning of the Bible and is believed to read To my Darling Candy. All Characters portrayed within this book are fictitious and any resemblance to persons living or dead is entirely coincidental.///Red Dwarf __ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one place. Yahoo! Shopping: http://shopping.yahoo.com
Re: Startup-scripts
*- On 21 Dec, [EMAIL PROTECTED] wrote about Startup-scripts *please CC all replies to me, as I am not subscribed to this list. thanks* Hello all, I am using Debian GNU/Linux potato i386. I have written a ipchains firewall script that I would like to be executed automatically during startup. Where would I put this (shell) script? I know that Debian has rules Where would I put this (shell) script? I know that Debian has rules about the proper way to do certain system config things - what is the proper way to do this? Put your script in /etc/init.d. Try and make it accept 'start' and 'stop' arguments if appropriate. See /etc/init.d/README and /etc/init.d/skeleton for an example and pointers to more documentation. Then run the command: update-rc.d ipmasq start 41 S . This will place the appropriate links in the /etc/rcS.d and other directories, you need to at least start it after the network is setup(S40). If you want, install the ipmasq package and look at its startup script for an example that is probably more in line with what you want(it does not use the start-stop-daemon program). Brian Servis -- Mechanical Engineering | Never criticize anybody until you Purdue University | have walked a mile in thei shoes, [EMAIL PROTECTED] | because by that time you will be a http://www.ecn.purdue.edu/~servis | mile away and have their shoes.
Re: Startup scripts
best way is to make a script slap the script in /etc/init.d put a link to it in /etc/rc?.d where ? = runlevel (runlevel 2 is defailt for debian so /etc/rc2.d ) make sure to chmod +x the script name the link according to how you want it to start as it reads the files in order. if you don't care when it loads then it doesnt matter what you name it. nate [mailto:[EMAIL PROTECTED] ]-- Linux System Administrator http://www.firetrail.com/ Firetrail Internet Services Limited http://www.aphroland.org/ Everett, WA 425-348-7336http://www.linuxpowered.net/ Powered By:http://comedy.aphroland.org/ Debian 2.1 Linux 2.0.36 SMPhttp://yahoo.aphroland.org/ -[mailto:[EMAIL PROTECTED] ]-- On Sun, 10 Oct 1999, Salman Ahmed wrote: Here is another simple question that I cannot figure out. I want a program to be started up at boot time alongwith all the other daemons. Which startup file should I modify for this ? I want this program (which is a daemon) to be started up regardless of whether X is running or not. Thanks. -- Salman Ahmed ssahmed AT interlog DOT com -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Startup scripts
-BEGIN PGP SIGNED MESSAGE- On Sun, 10 Oct 1999, Salman Ahmed wrote: Here is another simple question that I cannot figure out. I want a program to be started up at boot time alongwith all the other daemons. Which startup file should I modify for this ? You should create a startup script in /etc/init.d, either named after your daemon or named after the service it provides. In either case, it might be wise to prefix or suffix local to help prevent any Debian packages from overwriting it. /etc/init.d/skeleton can serve as a good template. You'd then use the update-rc.d command it insert symlinks in the proper runlevels. Since you seem to want it running in any runlevel, update-rc.d init.d_filename defaults should do it (where init.d_filename is the filename from the paragraph above). See the manpage for more info. - -- finger for PGP public key. -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: noconv iQCVAwUBOAFZrb7M/9WKZLW5AQGmgAQAltQ9fDjHpubOlhLwxLx7hiO7qM/hDOFg iLSe5cgotYaBO8ETK07Ffhi3lQFKYdZelXOfqeJpuyA3ZihiLn9aNtaM3DBL++W4 TgAtFIFTYJUMzg3HJipg2Rhkwcv+qPPW/jpvtkb+e8Vxe/5OZOrISyJ+GHHrXKTL 2DcO/T4K1+s= =hDth -END PGP SIGNATURE-
What is the correct way to modify startup scripts?
My debian system is starting various processes which I don't need. I presume I could prevent this by deleting the links in /etc/rc0.d but is this the correct way to do it? Anthony -- Anthony Campbell - running Linux Debian 2.0 [EMAIL PROTECTED] http://www.achc.demon.co.uk
Re: What is the correct way to modify startup scripts?
Hello Anthony: There is a file in /usr/sbin call update-rc.d. It permitts the addition and removal of startup files from the respective run-level directories. Peter -Original Message- From: Anthony Campbell [EMAIL PROTECTED] To: debian-user@lists.debian.org debian-user@lists.debian.org Date: Wednesday, October 07, 1998 5:30 AM Subject: What is the correct way to modify startup scripts? My debian system is starting various processes which I don't need. I presume I could prevent this by deleting the links in /etc/rc0.d but is this the correct way to do it? Anthony -- Anthony Campbell - running Linux Debian 2.0 [EMAIL PROTECTED] http://www.achc.demon.co.uk -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null BEGIN:VCARD VERSION:2.1 N:Iannarelli;Peter FN:Peter Iannarelli ORG:GenX Internet Laboratories TITLE:Engineer TEL;WORK;VOICE:1+ 416-929-1885 TEL;WORK;FAX:1+416-929-1056 ADR;WORK:;Madison;20 Madison Ave.;Toronto;Ontario;;Canada LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Madison=0D=0A20 Madison Ave.=0D=0AToronto, Ontario=0D=0ACanada URL: URL:http://www.genxl.com EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:19981007T094035Z END:VCARD
Re: What is the correct way to modify startup scripts?
Peter Iannarelli wrote: Hello Anthony: There is a file in /usr/sbin call update-rc.d. It permitts the addition and removal of startup files from the respective run-level directories. My debian system is starting various processes which I don't need. I presume I could prevent this by deleting the links in /etc/rc0.d but is this the correct way to do it? Anthony Hello, I don't quite follow and I also have a few things that run at startup from my first install that I included as modules (ppp,scsi,vfat) that still are trying to load even tho I have made my own kernel with them complied in. So I don't need or want to see them trying to load modules that it first used to get my system going that arn't there anymore. How would I clean up the boot process of these old first install modules..that arnt needed anymore and my present kernel handles fine ? Steven Udell [EMAIL PROTECTED]
Re: What is the correct way to modify startup scripts?
In article [EMAIL PROTECTED], Steven Udell [EMAIL PROTECTED] wrote: How would I clean up the boot process of these old first install modules..that arnt needed anymore and my present kernel handles fine ? edit /etc/modules Mike. -- Did I ever tell you about the illusion of free will? -- Sheriff Lucas Buck, ultimate BOFH.
Re: debian startup scripts dedicated ppp
You should propagate the PPP startup script before the NFS
mounts occur. This is a site specific configuration that
probably isn't that common. Never the less, I think Debian
1.2 will probably deal with this better (I think). In the
I hope so. I didn't have much trouble getting the nfs stuff working, but
I didn't like what I had to do and I felt it should work better out of the
box without requiring editing of the rc scripts.
system in front of me right now (mine's floating in the
Pacific at the moment :-)), so this is the best I can do.
This should get your ppp up prior to going to the mount
phase.
Are you the guy who's doing data collection with a underwater linux
system? I think that'd make a great Linux Journal article :-)
This seems to be a very popular problem. Debian, RedHat,
Slackware, SunOS, Solaris, Irix all kill all processes prior
to unmounting filesystems. The theory behind this is that
if a filehandle is open on a filesystem, it can't be
unmounted. The problem is when the process killed is ypbind
or pppd and you can't resolve the hostname of the NFS
server.
I did like redhat's solution; it worked for me, but I can think of
situations where it wouldn't..
I think Solaris 2.5+ has a functional fuser command
that could be used to kill all processes (close all open
filehandles) on a mount point. The shutdown procedure could
then kill processes on NFS mounted filesystems first,
unmount NFS filesystems, then do its normal routine of
killing all processes and umounting all filesystems.
Anybody know if Debian's fuser command supports this?
Anybody got any other ideas here?
It looks like fuser will support this, it has a -k flag that will kill all
processes accessing a file. fuser -m -k /home should kill every process
using the /home partition.
I see that red hat uses a nfsfs script that's responsible for
starting/stopping nfs services at the appropriate time. Unless I'm just
totally missing something with my problems as I described them above, I
propose that a similar script be added to debian.
How does this script handle the open filehandles issue on
It doesn't handle them at all. The key thing is, it's a standard sysv init
script, so the sysadmin can change the order it's executed in my changing
the symlink, and so can ensure that anything else that's using the nfs
mounts gets killed before the script is executed. (In theory, anyway.)
Do you have a copy of the script?
Here's a copy of the script:
#!/bin/sh
#
# nfsfs Mount NFS filesystems.
#
# Version: @(#) /etc/init.d/skeleton 1.01 26-Oct-1993
#
# Author: Miquel van Smoorenburg, [EMAIL PROTECTED]
#
# Source networking configuration.
. /etc/sysconfig/network
# Check that networking is up.
[ ${NETWORKING} = no ] exit 0
# See how we were called.
case $1 in
start)
echo -n Mounting remote filesystems.
mount -a -t nfs
touch /var/lock/subsys/nfsfs
echo
;;
stop)
echo -n Unmounting remote filesystems.
umount -a -t nfs
rm -f /var/lock/subsys/nfsfs
echo
;;
*)
echo Usage: nfsfs {start|stop}
exit 1
esac
exit 0
--
#!/usr/bin/perl -lisubstr($_,39+38*sin++$y/9,2)=$s # [EMAIL PROTECTED]
for($s=' '||McQ;$_='JOEY HESS 'x8;print){eval$^I} # Joey Hess
He. He. He. - - Herman Toothrot
Re: debian startup scripts dedicated ppp
On Tue, 24 Sep 1996, Joey Hess wrote: You should propagate the PPP startup script before the NFS mounts occur. This is a site specific configuration that probably isn't that common. Never the less, I think Debian 1.2 will probably deal with this better (I think). In the I hope so. I didn't have much trouble getting the nfs stuff working, but I didn't like what I had to do and I felt it should work better out of the box without requiring editing of the rc scripts. Well, I don't know about that. I can't get ppp working under Solaris without editing the asppp scripts and creating a startup script, etc. Of course, Debian is better than Solaris :-) I know that Bruce plans on including some kind of ppp configuration utility in 1.2 that would produce a chat or diald script. It shouldn't be too difficult to add the functionality of choosing where to place it in the startup. Most people don't have a full time ppp connection AFAIK. I believe the average ppp user only connects when she/he needs to and works offline the rest of the time. I could be wrong though. Slackware has a section of its installation that sets up NFS mounts. Maybe Debian should look into including something like this too? Maybe it has it and I forgot? system in front of me right now (mine's floating in the Pacific at the moment :-)), so this is the best I can do. This should get your ppp up prior to going to the mount phase. Are you the guy who's doing data collection with a underwater linux system? I think that'd make a great Linux Journal article :-) No, I'm the guy who just moved overseas and doesn't have any of his stuff because its being shipped via ocean liner. My wife and I both pulled a smooth move and packed up all of our shoes (except the ones we were wearing when the movers came). As much as I miss my Debian system, we can't wait to get our shoes! (It should be noted here that my wife does _not_ miss my Debian system ;-)) I think Solaris 2.5+ has a functional fuser command that could be used to kill all processes (close all open filehandles) on a mount point. The shutdown procedure could then kill processes on NFS mounted filesystems first, unmount NFS filesystems, then do its normal routine of killing all processes and umounting all filesystems. Anybody know if Debian's fuser command supports this? Anybody got any other ideas here? It looks like fuser will support this, it has a -k flag that will kill all processes accessing a file. fuser -m -k /home should kill every process using the /home partition. Well, I'd have to have a Debian system running to do some testing, and we'd have to have a way of dealing with automounted filesystems (addressing the correct mount point), but it looks like we should be able to implement a shutdown procedure that takes care of NFS mounts prior killing all processes. If you're interested in pursuing this, please e-mail me privately. I'd be glad to try to implement something and submit it for inclusion in later Debian releases (unless someone already has :-)). Thanks. Richard G. Roberto [EMAIL PROTECTED] 011-81-3-3437-7810 - Tokyo, Japan -- *** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. ***
debian startup scripts dedicated ppp
I have a dedicated ppp script, and it doesn't seem that debian's startup scripts make any provisions for this. I've modified the init.d/ppp script to start up ppp, and made it be run on boot and shutdown. There's a filesystem I always nfs mount over ppp (it's in fstab), and when I'm booting up, init.d/boot mounts all the nfs filesystems after it's run init.d/network, but before my ppp gets started. So I have to wait there until the mount times out, and manually mount the filesystem after the system is done booting. I have a similar problem on shutdown, my ppp is killed when the scripts in /etc/rc6.d are run, but the nfs filesystem is still mounted. Then init.d/reboot comes along and tries to unmount filesystems, anf gets hung up on the nfs filesystem, and I have to wait for that to time out before my system reboots. So is there a better way to set up a dedicated ppp link than what I'm using? And is there any provision to unmount filesystems before the network is brought down? I see that red hat uses a nfsfs script that's responsible for starting/stopping nfs services at the appropriate time. Unless I'm just totally missing something with my problems as I described them above, I propose that a similar script be added to debian. -- true - do nothing, successfully - - true (1)
Re: debian startup scripts dedicated ppp
The simple solution to your problem is to put the 'noauto' option on your nfs directory entry in /etc/fstab, and then put an explicit mount command (and corresponding umount command) in the init.d/ppp script. You could also setup amd, but that could be overkill for your situation. -- Scott Barker Linux Consultant [EMAIL PROTECTED] http://www.cuug.ab.ca:8001/~barkers/ (under construction) [ I try to reply to all e-mail within 3 days. If you don't ] [ get a response by then, I probably didn't get your e-mail. ] [ Unsolicited commercial and junk e-mail will be proof-read for US$100 ] There is a coherent plan in the universe, though I don't know what it's a plan for. - Fred Hoyle
Re: debian startup scripts dedicated ppp
On Mon, 23 Sep 1996, Joey Hess wrote: I have a dedicated ppp script, and it doesn't seem that debian's startup scripts make any provisions for this. I've modified the init.d/ppp script to start up ppp, and made it be run on boot and shutdown. There's a filesystem I always nfs mount over ppp (it's in fstab), and when I'm booting up, init.d/boot mounts all the nfs filesystems after it's run init.d/network, but before my ppp gets started. So I have to wait there until the mount times out, and manually mount the filesystem after the system is done booting. You should propagate the PPP startup script before the NFS mounts occur. This is a site specific configuration that probably isn't that common. Never the less, I think Debian 1.2 will probably deal with this better (I think). In the mean time, you can customize the init.d/network script to call your ppp startup script instead of running it out of rcX.d (where X is the run level). I don't have a Debian system in front of me right now (mine's floating in the Pacific at the moment :-)), so this is the best I can do. This should get your ppp up prior to going to the mount phase. A better solution may be to use the noauto option for NFS mounts and include a separate NFS mount script in init.d and link it to something later than the PPP script in the rc directory. That would save you from modifying init.d/network. It would also enable you to configure runlevels that do not use ppp, or NFS mounts, etc. Again I don't have a Debian system in from of me right now, so I don't know how this is handled in 1.1 out of the box for sure. I have a similar problem on shutdown, my ppp is killed when the scripts in /etc/rc6.d are run, but the nfs filesystem is still mounted. Then init.d/reboot comes along and tries to unmount filesystems, anf gets hung up on the nfs filesystem, and I have to wait for that to time out before my system reboots. This seems to be a very popular problem. Debian, RedHat, Slackware, SunOS, Solaris, Irix all kill all processes prior to unmounting filesystems. The theory behind this is that if a filehandle is open on a filesystem, it can't be unmounted. The problem is when the process killed is ypbind or pppd and you can't resolve the hostname of the NFS server. I think Solaris 2.5+ has a functional fuser command that could be used to kill all processes (close all open filehandles) on a mount point. The shutdown procedure could then kill processes on NFS mounted filesystems first, unmount NFS filesystems, then do its normal routine of killing all processes and umounting all filesystems. Anybody know if Debian's fuser command supports this? Anybody got any other ideas here? So is there a better way to set up a dedicated ppp link than what I'm using? And is there any provision to unmount filesystems before the network is brought down? I see that red hat uses a nfsfs script that's responsible for starting/stopping nfs services at the appropriate time. Unless I'm just totally missing something with my problems as I described them above, I propose that a similar script be added to debian. How does this script handle the open filehandles issue on NFS mounts? Do you have a copy of the script? Thanks Richard G. Roberto [EMAIL PROTECTED] 011-81-3-3437-7810 - Tokyo, Japan -- *** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. ***
