[Bug 245627] jail rc script stops jails not defined in jail.conf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245627 Dan Langille changed: What|Removed |Added CC||d...@freebsd.org --- Comment #4 from Dan Langille --- The mention of poudriere reminded me of how /usr/local/etc/periodic/security/410.pkg-audit attempts to audit poudriere jails: * https://github.com/freebsd/pkg/issues/1748 * https://github.com/freebsd/pkg/pull/1749 FYI: $ pkg which /usr/local/etc/periodic/security/410.pkg-audit /usr/local/etc/periodic/security/410.pkg-audit was installed by package pkg-1.13.2 How is this related? They are all hard problems to solve. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 245627] jail rc script stops jails not defined in jail.conf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245627 Jamie Gritton changed: What|Removed |Added CC||ja...@freebsd.org --- Comment #3 from Jamie Gritton --- While it would make sense for something like poudriere to work with the existing jail.conf setup, that's non-trivial and not urgent. It seems reasonable to add an rc knob for rc.d/jail to not remove all jails, and keep the default behavior as is. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 245627] jail rc script stops jails not defined in jail.conf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245627 --- Comment #2 from Kyle Evans --- I think it's a bit odd to rule that it should be closed with absolutely no action (perhaps documentation at a minimum) to be taken. Having jails while also using tools like poudriere that create transient jails seems like it should be perfectly fine without this rc script stomping on the latter. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 245627] jail rc script stops jails not defined in jail.conf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245627 jo...@a1poweruser.com changed: What|Removed |Added CC||jo...@a1poweruser.com --- Comment #1 from jo...@a1poweruser.com --- Jail definition statements can still be placed in rc.conf which is the pre release 6.0 method or in the jail.conf file which is the new way since release 6.0. The code in rcd/jail needs to be cleaned up removing the processing of the old rc.conf jail definition method. ezjail uses the rc.conf method and gets a warning message telling the user to change his jail definition method to use jail.conf. The ezjail maintainer has been told to update ezjail many times over the past 6 releases of FreeBSD but has not done so. qjail is an updated version of ezjail that uses jail.conf and only starts/stops/restarts jails under it control. It does not use the default jail.conf file so native jails and other jail tools do not step on qjail jails. When it comes to jails with manual defined definitions in the default jail.conf file with other jail tools also putting their jail definitions in the default jail.conf file the rc.conf jail start statement will start all of them at boot time by default as designed. Adding the rc.conf jail names statement containing the jail names to use is only way to control which jails are started at boot time by default. It is the users responsibility that native jail and jail tools that use the default jail.conf file DO NOT exist on the same host at the same time because of the possibility of them stepping on each other during host boot or stop/restart time. To summarize: This is not a bug or short coming in rcd/jail. But a design flaw in some jail tools making them incapable of playing nice with native jails defined in the default jail.conf file. This bug report should be closed because it's not a bug. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 242437] Jail rc script does not return non-0 exit code on problems
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242437 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|j...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
Fwd: conf/142973: [jail] [patch] Strange counter init value in jail rc
Hi Matteo, Ruslan You both put the code in for jail_poststart and jail_afterstart in rc.d/jail [1,2], and I have a couple of questions about it. I can see that the first function written was jail_afterstart, and that started counting from 1, and I can see that subsequently jail_poststart was added that started counting from zero. I've replied to the PR below with a patch to start jail_afterstart counting from 0 yet still working with a warning for those who have started counting from 1. Is there a difference between poststart/afterstart? Only afterstart is documented (incorrectly). Chris [1] http://svnweb.FreeBSD.org/base/head/etc/rc.d/jail?r1=191619r2=191620 [2] http://svnweb.FreeBSD.org/base/head/etc/rc.d/jail?r1=159071r2=159072; -- Forwarded message -- From: cr...@freebsd.org Date: 3 November 2012 12:21 Subject: Re: conf/142973: [jail] [patch] Strange counter init value in jail rc To: da...@nfrance.com, cr...@freebsd.org, freebsd...@freebsd.org Synopsis: [jail] [patch] Strange counter init value in jail rc State-Changed-From-To: open-analyzed State-Changed-By: crees State-Changed-When: Sat Nov 3 12:21:57 UTC 2012 State-Changed-Why: This is a pickle indeed. Moany people will have used it starting from 1, since the original code was intended to count from 1; see r159072. However, the prestart code added in r191620 counts from 0. The patch at http://www.bayofrum.net/~crees/patches/142973.diff makes it count from 0, but still work with a warning if the user has started at 1. I will talk to the developers concerned. http://www.freebsd.org/cgi/query-pr.cgi?pr=142973 ___ freebsd-jail@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to freebsd-jail-unsubscr...@freebsd.org
Re: jail rc
Use sh /bin/rc -- Michael Scheidell CTO SECNAP Network Security 561-948-2259tel:5619482259 -Original message- From: Mickey Harvey mh.u...@gmail.com To: freebsd-jail@freebsd.org freebsd-jail@freebsd.org Sent: Thu, Apr 21, 2011 18:30:17 GMT+00:00 Subject: jail rc This might be more of a question about how rc works instead of being entirely jail specific but here goes: I am trying to start a jail using the jail command such that it appears on the command line as jail /path/to/jail hostname 192.168.1.1 /bin/rc. I am expecting it to just start the jail and run the rc scripts but I must be doing something wrong because it returns the error jail: execvp: /bin/rc: Permission denied. ___ freebsd-jail@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to freebsd-jail-unsubscr...@freebsd.org ___ freebsd-jail@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to freebsd-jail-unsubscr...@freebsd.org
